Hi all,
thanks a lot for allowing me to join the QtC Summit this year.
I'm wondering if anyone is interested in my experiences with using the
Qt/Quick technology in a non standard way. I was specifically thinking
of the QSkinny theming system and the implications of doing scene graph
node com
Sad to see, there is no recording... :(
Any materials/slides to share?
Br,
Zoltan
On Thursday, November 7, 2019, Tuukka Turunen wrote:
>
> Hi,
>
> Unfortunately no recording. We had the session in the hack space, not part of
> the technical tracs (that were recorded and will be available lat
On 2019-11-07 10:40 a.m., Cristian Adam wrote:
You can use https://qtlite.com/ to figure out only the parts you need for your
setup.
Cool!
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On 2019-11-07 10:31 a.m., Konstantin Tokarev wrote:
07.11.2019, 18:08, "drwho" :
On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
4) What about the memory footprint?
A couple of megabytes.
I'd love to see a build how t
You can use https://qtlite.com/ to figure out only the parts you need for your
setup.
Cheers,
Cristian.
> -Original Message-
> From: Development On Behalf Of
> drwho
> Sent: Thursday, 7 November 2019 16:07
> To: development@qt-project.org
> Subject: Re: [Development] Porting QT to new O
07.11.2019, 18:08, "drwho" :
> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
>> On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
>>
>>> 4) What about the memory footprint?
>> A couple of megabytes.
>
> I'd love to see a build how too that results in a couple of megabytes.
On Thursday, 7 November 2019 16:06:41 CET drwho wrote:
> On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
> > On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
> >> 4) What about the memory footprint?
> >
> > A couple of megabytes.
>
> I'd love to see a build how too that results
On 2019-11-07 12:42 a.m., Thiago Macieira wrote:
On Wednesday, 6 November 2019 20:41:10 PST martin ribelotta wrote:
4) What about the memory footprint?
A couple of megabytes.
I'd love to see a build how too that results in a couple of megabytes.
The smallest I've ever got Qt with a "cut ev
Hi,
Unfortunately no recording. We had the session in the hack space, not part of
the technical tracs (that were recorded and will be available later).
Yours,
Tuukka
On 07/11/2019, 13.20, "Paul Wicking" wrote:
This sounds great! Was the session recorded, and if so is it viewabl
On 6. Nov 2019, at 13:38, Edward Welbourne wrote:
>>> Simplest would be to have two optional arguments, startYear and
>>> span; in 5.15, startYear must be supplied (to distinguish this
>>> overload from the old method) but span can be optional, defaulting
>>> to 100 (also used if span < 0 or span
This sounds great! Was the session recorded, and if so is it viewable somewhere
online, for people that weren't there?
P.
On 07/11/2019, 07:58, "Development on behalf of Tuukka Turunen"
wrote:
Hi,
Yesterday morning at the Qt World Summit we had a session about
contributi
André Somers (6 November 2019 17:20) wrote
> I came to the conclusion that the sane behavior for interpreting dates
> depends on the semantics of what the date means. For instance, a birth
> date will always be a date in the past,
... except when it's the best-estimate date of birth of an expected
>> Yes, POSIX compliant base including pthreads and filesystem API. What the
>> filesystem API accesses is irrelevant, it just has to exist. Threading
>> support
>> is mandatory in Qt, even though there are #ifndef QT_NO_THREAD around.
>> Those
>> aren't tested and aren't guaranteed to even compi
> On 6. Nov 2019, at 13:38, Edward Welbourne wrote:
>
> Eike Ziller (6 November 2019 09:45)
>> It sounds to me like any automatically chosen base for 2-digit years
>> will be wrong depending on use case.
>
> You (among several others) make a compelling case.
>
>> If you want to make it easier
Hi all,
Final downmerge from '5.12' to '5.12.6' is now done. So all changes targeted to
Qt 5.12.6 release must be done in '5.12.6'.
Target is to release Qt 5.12.6 during next week so please make sure all
blockers are visible in release blocker list
(https://bugreports.qt.io/issues/?filter=2166
15 matches
Mail list logo
