Hello
I'm just curious, is Qt project aiming for be a umbrella of libraries tied
to Qt release or this libraries like QtGamePad on other thread
should be more suitable to something like inqlude.org ( or similar ).
Just to clarify, as a distro packager too.
[]'s
On Tue, Jan 26, 2016 at 8:47 A
Awesome work :)
Simon
From: Development on behalf of Mike Krus
Sent: Monday, January 25, 2016 21:06
To: Qt Development Group
Subject: [Development] tvOS port
Hi
during the xmas break, I took "advantage" of the dreadful weather to
investigate port
And another +1 from me.
Cheers,
Lars
On 26/01/16 08:42, "Development on behalf of Mike Krus"
wrote:
>+1, will be useful for the tvOS remote!
>
>
>Mike
>
>On 25/01/2016 15:37, Agocs Laszlo wrote:
>> Hello,
>>
>> The Qt Gamepad module has been living in a qt-labs repo (*) for some
>> time. I
+1 for making it a TP in 5.7 and another +1 for Erik becoming the maintainer.
Cheers,
Lars
On 25/01/16 19:49, "Development on behalf of Turunen Tuukka"
wrote:
>
>+1
>
>State machine framework has been part of Qt for many years and there was also
>some work earlier for scxml compatibility, w
+1, will be useful for the tvOS remote!
Mike
On 25/01/2016 15:37, Agocs Laszlo wrote:
Hello,
The Qt Gamepad module has been living in a qt-labs repo (*) for some
time. I’d like to propose to upgrade it to an add-on module and include
it as a Tech Preview in Qt 5.7. This would also benefit oth
Hi
during the xmas break, I took "advantage" of the dreadful weather to
investigate porting Qt5 (dev branch) to Apple's tvOS.
Due to tvOS being mostly built upon iOS, the initial work was quite straight
forward, adding a new mkspec, a new configure option, a CONFIG variable (tvos),
enabling an
On Monday, January 25, 2016 02:55:27 PM Blasche Alexander wrote:
> Hi,
>
> As part of the renewed publishing process following the new KDE Free Qt
> foundation agreement, we'd like to publish the source of the new Qt SCXML
> module.
>
> I'd like to propose the module to be accepted as part of th
+1
State machine framework has been part of Qt for many years and there was also
some work earlier for scxml compatibility, which was never completed. SCXML is
an industry standard format, which can be exported from multiple different
tools.
Yours,
Tuukka
> Blasche Alexander kirjoitti 25.1
On 25/01/2016 15:37, Agocs Laszlo wrote:
Hello,
The Qt Gamepad module has been living in a qt-labs repo (*) for some
time. I’d like to propose to upgrade it to an add-on module and
include it as a Tech Preview in Qt 5.7. This would also benefit other
modules, for instance Qt 3D has pending
+1
BogDan.
On Monday 25 January 2016 15:37:45 Agocs Laszlo wrote:
> Hello,
>
> The Qt Gamepad module has been living in a qt-labs repo (*) for some time.
> I'd like to propose to upgrade it to an add-on module and include it as a
> Tech Preview in Qt 5.7. This would also benefit other modules, fo
Hello,
The Qt Gamepad module has been living in a qt-labs repo (*) for some time. I'd
like to propose to upgrade it to an add-on module and include it as a Tech
Preview in Qt 5.7. This would also benefit other modules, for instance Qt 3D
has pending contributions for gamepad support via the Qt
Hi,
As part of the renewed publishing process following the new KDE Free Qt
foundation agreement, we'd like to publish the source of the new Qt SCXML
module.
I'd like to propose the module to be accepted as part of the Qt add-on modules.
The module itself is brand new as well (target is a 5.7
On 25/01/16 14:54, "Development on behalf of Giuseppe D'Angelo"
wrote:
>Il 23/10/2015 22:19, Hausmann Simon ha scritto:
>> +1x2
>
>Howdy,
>
>was this nomination somehow lost in the process?
Looks like it. Sorry for that.
>I guess enough time has
>passed to make Andreas both Approver and
Il 23/10/2015 22:19, Hausmann Simon ha scritto:
+1x2
Howdy,
was this nomination somehow lost in the process? I guess enough time has
passed to make Andreas both Approver and WinCE maintainer!
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Software Engineer
KDAB (UK) Ltd., a KDAB
On Friday 22 of January 2016 08:50:52 Thiago Macieira wrote:
> On Friday 22 January 2016 11:26:55 Bogdan Vatra wrote:
> > AFAIK C++11/14 compilers have zero-cost exception, so, is there any reason
> > why not start using them in Qt 6.0 ?
>
> Yes. There's a couple of man-decades worth of work to m
Jani:
I see the 5.6.0 RC blocker list.
But what about bugs like?
Using 5.6.0 Beta: https://bugreports.qt.io/browse/QTBUG-50374
What is the criterion for entry into the blocker list?
Only core code, not tools?
Thank you,
md
On Mon, Jan 25, 2016 at 5:39 AM, Heikkinen Jani
wrote:
> ‘5.6.0’ b
‘5.6.0’ branch is now available, please start using it for the changes targeted
to Qt5.6.0 release.
We will merge ‘5.6’ branch to ‘5.6.0’ Monday 1st February so there should be
enough time to finalize ongoing changes in ‘5.6’ and start using '5.6.0'. All
new changes for Qt5.6.0 should be done
On 23 Jan 2016, at 19:52, Sean Harmer
mailto:s...@theharmers.co.uk>> wrote:
On 23/01/2016 12:45, Uwe Rathmann wrote:
Hi,
The OpenGL acceleration in Charts module is really impressive ...
Unfortunately part of the truth is, that the performance of the software
renderer does not necessarily be tha
Le samedi 23 janvier 2016 à 12:45 +, Uwe Rathmann a écrit :
> Hi,
>
> > The OpenGL acceleration in Charts module is really impressive ...
>
> Unfortunately part of the truth is, that the performance of the
> software
> renderer does not necessarily be that far behind.
The test I did with QCh
> On Jan 23, 2016, at 1:12 AM, Kevin Kofler wrote:
>
> Ziller Eike wrote:
>>> I would like that trend to continue. The likely next candidates are
>>> threads, futures and locks.
>>
>> +1
>
> I wonder why everyone so far agreed on that. So let me dissent: I think
> having these things in Qt wi
> On Jan 23, 2016, at 1:47 AM, Thiago Macieira
> wrote:
>
> On Saturday 23 January 2016 01:23:30 Kevin Kofler wrote:
>> I feel it's actually TOO rapidly changing. C++11 even threw out C
>> compatibility, not only by not adopting all C99 improvements (e.g. VLAs),
>> but also by subtly interpreti
I suppose the default should be that a class is fully supported on all Qt
platforms, so the qdoc command should be \notsupported with the list of not
supported platforms.
\notsupported
...could appear in a \class or a \fn or in a \qmltype or \qmlmethod.
martin
___
22 matches
Mail list logo
