Re: [Development] Examples and Demos in qtdoc

2017-06-14 Thread Tuukka Turunen 

Hi,

Yes, we would like to overall improve the examples. This is related to having a 
new repo for examples, but not fully the same thing. Main goal in example 
improvement being to make them more useful in what they are: examples of how to 
use Qt. Currently there are some examples that implement their own rudimentary 
controls instead of using Qt Quick Controls 2. We also have some examples that 
do not properly leverage our tooling. Some examples might not show the very 
best way to do things, as the new APIs allow even better way than at the time 
of creating the example.  

What comes to WOW, we do need to have great looking demos and at least some 
examples should look good as well. However, that WOW should not be the ultimate 
goal. The purpose of examples is to help users make better use of Qt and 
sometimes making things too shiny can be counterproductive. Another thing is 
that this WOW is a quite subjective matter and different trends come and go. It 
is fine to make an example look great, but that should not be the sole purpose.

Yours,

Tuukka

On 14/06/2017, 18.54, "Development on behalf of Sze Howe Koh" 
 wrote:

On 14 June 2017 at 19:18, Frederik Gladhorn  wrote:
>
> Hi all,
>
> We recently had a discussion in the Qt Company about how we can improve 
the
> first use experience of Qt and one important aspect are the examples and 
demos.

+1


> We have a lot of examples that are limited by the Qt module they live in, 
for
> example not making use of ready made buttons in Qt Quick. To allow 
examples to
> use any Qt module while keeping the build system clean (no cyclic 
dependencies
> between modules), I'd like to propose using the qtdoc module to gather 
fresh
> and beautiful examples.
>
> We currently have a few bigger examples already that would fit this 
category
> and plan to invest more into good looking nice and welcoming examples to 
give
> new Qt users a positive first impression.

Fresh and beautiful is good.

Does this initiative also involve cleaning up existing examples
(including removing them, where appropriate)? For example, the old
rendering at 
http://doc.qt.io/qt-5/qtquick-scenegraph-textureinsgnode-example.html
would detract from the nice and welcoming bits on display.

One reason to avoid a large-scale cleanup, though, is to avoid link rot.


> Of course we could create a new repo, but considering that we have an 
existing
> repo which did contain the demo launcher previously and which is ready to 
be
> used, I'd propse going with it, while the name is not perfect. It's 
already
> part of the infrastructure and qt5.git, so this seems like an easy way to 
go
> forward.

qtdoc.git currently houses a number of non-flashy but nonetheless
important examples and documents (e.g. signals and slots, platform
notes). Would it be better to keep a separate repo for wowing
newcomers (say, "qtshowcase.git")? Especially since there will be many
large files involved, as Sean mentioned.


Regards,
Sze-Howe
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Someone please fix the remaining qrand cases in SSL code

2017-06-14 Thread Thiago Macieira 
On quarta-feira, 14 de junho de 2017 08:25:31 PDT Giuseppe D'Angelo wrote:
> Il 12/06/2017 22:45, Thiago Macieira ha scritto:
> > I can't submit changes to SSL-related code, so can someone apply the
> > equivalent ofhttps://codereview.qt-project.org/191738  to the files listed
> > in that commit's message?
> 
> There are a couple of problems arising from there:
> 
> 1) some place has a "TODO: use a CSPRNG". Given the current
> QRandomGenerator API, is there a way to know if a CSPRNG is actually
> being used or we're falling back to a plain PRNG?

It's not in the API, but in all non-misconfigured systems, it should be CSPRNG. 
You can misconfigure your system by running your Qt application in a chroot 
that doesn't have /dev/random or /dev/urandom.

There's also the issue of the system and CPU entropy pools. This could be an 
issue if the application uses QRandomGenerator in the first few hundred ms 
after boot. That can only affect device manufacturers and they should inspect 
their systems to know if that is happening. 

At least on Linux, once seeded, /dev/urandom does not stop working, so if we 
opened it (no bad chroot) and it has worked (system collected some entropy), 
the fallback should never kick in. Yes, that means the Mersenne Twister 
fallback is actually dead code on Linux. But this means that QRandomGenerator 
is good for unattended CSPRNG uses, such as networking code.

For key generation, I'd use /dev/random and require the user to move the 
mouse.

> 2) a test wants to generate a few MB of random data. Ideally this would
> be a no-brainer -- QRandomGenerator plus an engine from the standard
> library, but we can't use those engines yet (or can we?). So those
> places will need to keep qrand()?

#if QT_CONFIG(cxx11_random), after https://codereview.qt-project.org/196612 
integrates.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Examples and Demos in qtdoc

2017-06-14 Thread Sze Howe Koh 
On 14 June 2017 at 19:18, Frederik Gladhorn  wrote:
>
> Hi all,
>
> We recently had a discussion in the Qt Company about how we can improve the
> first use experience of Qt and one important aspect are the examples and 
> demos.

+1


> We have a lot of examples that are limited by the Qt module they live in, for
> example not making use of ready made buttons in Qt Quick. To allow examples to
> use any Qt module while keeping the build system clean (no cyclic dependencies
> between modules), I'd like to propose using the qtdoc module to gather fresh
> and beautiful examples.
>
> We currently have a few bigger examples already that would fit this category
> and plan to invest more into good looking nice and welcoming examples to give
> new Qt users a positive first impression.

Fresh and beautiful is good.

Does this initiative also involve cleaning up existing examples
(including removing them, where appropriate)? For example, the old
rendering at 
http://doc.qt.io/qt-5/qtquick-scenegraph-textureinsgnode-example.html
would detract from the nice and welcoming bits on display.

One reason to avoid a large-scale cleanup, though, is to avoid link rot.


> Of course we could create a new repo, but considering that we have an existing
> repo which did contain the demo launcher previously and which is ready to be
> used, I'd propse going with it, while the name is not perfect. It's already
> part of the infrastructure and qt5.git, so this seems like an easy way to go
> forward.

qtdoc.git currently houses a number of non-flashy but nonetheless
important examples and documents (e.g. signals and slots, platform
notes). Would it be better to keep a separate repo for wowing
newcomers (say, "qtshowcase.git")? Especially since there will be many
large files involved, as Sean mentioned.


Regards,
Sze-Howe
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] What to do with qrand/qsrand?

2017-06-14 Thread Thiago Macieira 
On quarta-feira, 14 de junho de 2017 08:26:50 PDT Jason H wrote:
> Given the number of softwares that are compromised by bad random number
> generation practices, I'd suggest we invert the normal behavior - random by
> default. If they need predictability then make them seed with a constant
> seed.

That is why I added QRandomGenerator, which has a (reasonably) secure default 
behaviour. But it will degrade if you abuse it.

The question though is what to do with qrand. Code using it is not secure at 
all, so does it matter if we change it?

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] What to do with qrand/qsrand?

2017-06-14 Thread Jason H 
Given the number of softwares that are compromised by bad random number 
generation practices, I'd suggest we invert the normal behavior - random by 
default. If they need predictability then make them seed with a constant seed.

For a more detailed talk on secure random: 
https://www.youtube.com/watch?v=n_xiOYvr6oY




> Sent: Tuesday, June 13, 2017 at 3:52 PM
> From: "Thiago Macieira" 
> To: development@qt-project.org
> Subject: [Development] What to do with qrand/qsrand?
>
> I've changed almost all uses of qrand in Qt sources to QRandomGenerator and 
> eliminated the use of qsrand. That is actually the biggest advantage: not 
> needing to seed the generator. I was quite surprised how much use of qrand we 
> have in our own source code, and not just in examples. (See commits with 
> Change-Id Icd0e0d4b27cb4e5eb892fffd14b5285d43f4afbf).
> 
> Obviously those functions need to remain in Qt 5, but what should we do to 
> them long-term? See
>   https://lxr.kde.org/ident?_i=qrand&_remember=1
> 
> With this many references, I'm not sure we should even add a QT_DEPRECATED 
> warning to it, since that would make trigger-happy "warning--" developers in 
> KDE wholesale moving to something else.
> 
> Options:
>  1) do nothing, leave as-is (in Qt 6, use thread_local)
> 
>  2) deprecate and provide no replacement. That is, tell people to either:
>- use QRandomGenerator if they need true random, non-bulk
>- use  engines if they need bulk
>- use  rand() if they need C library compatibility
> 
>  3) deprecate and provide a thread-safe PRNG, which can be used in bulk
> a) with no seed; or
> b) with an access to seeding
> 
>  4) same as #3, but actually use the qrand/qsrand names
>for (a), qsrand would be empty
> 
> -- 
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
> 
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> 
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Someone please fix the remaining qrand cases in SSL code

2017-06-14 Thread Giuseppe D'Angelo 

Il 12/06/2017 22:45, Thiago Macieira ha scritto:

I can't submit changes to SSL-related code, so can someone apply the
equivalent ofhttps://codereview.qt-project.org/191738  to the files listed in
that commit's message?


There are a couple of problems arising from there:

1) some place has a "TODO: use a CSPRNG". Given the current 
QRandomGenerator API, is there a way to know if a CSPRNG is actually 
being used or we're falling back to a plain PRNG?


2) a test wants to generate a few MB of random data. Ideally this would 
be a no-brainer -- QRandomGenerator plus an engine from the standard 
library, but we can't use those engines yet (or can we?). So those 
places will need to keep qrand()?


Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB Group company | Tel: UK +44-1625-809908
KDAB - Qt, C++ and OpenGL Experts



smime.p7s
Description: Firma crittografica S/MIME
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] New configuration system docs and FBX issues

2017-06-14 Thread Lisandro Damián Nicanor Pérez Meyer 
On martes, 2 de mayo de 2017 08:47:34 -03 Sean Harmer wrote:
> Hi,
> 
> On 01/05/2017 14:16, Thiago Macieira wrote:
> > On Monday, 1 May 2017 03:17:23 -03 Sean Harmer wrote:
> >> Hi,
> >> 
> >> is there any documentation for the new configuration system please?
> >> 
> >> My specific issue is that I need a config test that uses different
> >> library names on each platform and I can't see how to achieve this. On
> >> windows I want the FBX config test in Qt 3D to link against the static
> >> FBX library libfbxsdk-md.lib whereas on linux it would be
> >> libfbxsdk-static.a and on macOS libfbxsdk.a.
> > 
> > Please make sure we're abe to link against the dynamic version of that
> > library on Linux.
> 
> Why the preference for dynamic linking here? It's another file to have
> to distribute? I don't particularly mind either way but is there a
> policy for such things?

Possibly because it makes it easier for distributions to create patches to 
link against the system version.


-- 
20:57  * m4rgin4l patento el proceso de invencion
20:57 < m4rgin4l> de aqui en mas cualquier inventor me tiene que pagar
regalias por inventar algo
20:57  * m4rgin4l tiene la patente pendiente del metodo cientifico

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Problems building qtwebkit in 5.9.1

2017-06-14 Thread Konstantin Tokarev 


14.06.2017, 12:49, "Harald Vistnes" :
> Hi,
>
> Has there been a change in the dependencies for qtwebkit in 5.9.1? I am not 
> able to build it anymore.
>
> I am using these commands:
>
> ...
> perl init-repository 
> --module-subset=all,-ignore,-qtwebkit-examples,-qtwebengine,-qtnetworkauth,-qtspeech,-qtandroidextras,-qtvirtualkeyboard,-qtcanvas3d,-qtdatavis3d,-qtcharts,-qtpurchasing,-qtquickcontrols2,-qtmultimedia,-qtserialport,-qtwayland,-qtdoc
>
> configure -prefix %CD%\qtbase -opensource -shared -confirm-license 
> -debug-and-release -release -opengl desktop -qt-zlib -qt-libpng -no-angle 
> -qt-libjpeg -icu -skip qtconnectivity -skip qtlocation -skip qtsensors -skip 
> qtwayland -skip qtserialbus -skip qtserialport -skip qtvirtualkeyboard -skip 
> qtdatavis3d -skip qtcharts -skip qtpurchasing -skip qtcanvas3d -skip qtspeech 
> -skip qtandroidextras -skip qtnetworkauth -skip qtquickcontrols -skip 
> qtwebengine -platform win32-msvc2015 -nomake tests
>
> cd qtwebkit
>
> ../qtbase/bin/qmake.exe WebKit.pro
>
> In 5.9.1 I get the following output from qmake:
>
> Running configure tests...
>
> Checking for fontconfig... no
> Checking for gccdepends... no
> Checking for glx... no
> Checking for gnuld... no
> Checking for icu... yes
> Checking for leveldb... no
> Checking for libsqlite3... no
> Checking for libwebp... no
> Checking for libXcomposite... no
> Checking for libxml2... no
> Checking for libXrender... no
> Checking for libxslt... no
> Checking for libzlib... no
> Project ERROR: Could not find feature system-jpeg.
>
> I did not get this error in 5.9.0 or in any previous versions.

You should use 5.212 branch of QtWebKit instead of 5.9.1.
Build instruction: 
https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Windows


>
> I am on Windows, but a colleague got the same error on Linux. He also tried 
> to configure with -system-jpeg, but with the same result.
>
> Thanks,
> Harald
>
> ,
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development


-- 
Regards,
Konstantin
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Examples and Demos in qtdoc

2017-06-14 Thread Pasi Keränen 
Hi,

I agree 100% with the need to have a place to store beautiful demos and 
examples. And I agree with Sean’s large file support need as Qt 3D Studio 
examples and demos will also depend on having access to large textures and hdr 
textures to make things look nice. Even 2D examples can require “large” 
resources when you are striving to create beautiful results.

I’m not 100% sure about qtdoc as the repo though. But I can live with it if 
that is what is seen as best option by others.

Cheers,
Pasi

--
Pasi Keränen
Senior Manager

The Qt Company
Elektroniikkatie 13
90590, Oulu, Finland


On 14/06/2017, 15.15, "Development on behalf of Sean Harmer" wrote:

Hi,

On Wednesday 14 June 2017 13:18:35 Frederik Gladhorn wrote:
> Hi all,
> 
> We recently had a discussion in the Qt Company about how we can improve 
the
> first use experience of Qt and one important aspect are the examples and
> demos.
> 
> We have a lot of examples that are limited by the Qt module they live in,
> for example not making use of ready made buttons in Qt Quick. To allow
> examples to use any Qt module while keeping the build system clean (no
> cyclic dependencies between modules), I'd like to propose using the qtdoc
> module to gather fresh and beautiful examples.
> 
> We currently have a few bigger examples already that would fit this 
category
> and plan to invest more into good looking nice and welcoming examples to
> give new Qt users a positive first impression.
> 
> Of course we could create a new repo, but considering that we have an
> existing repo which did contain the demo launcher previously and which is
> ready to be used, I'd propse going with it, while the name is not perfect.
> It's already part of the infrastructure and qt5.git, so this seems like an
> easy way to go forward.

I agree that we need something like this. Ideally we also need support for 
git-lfs or some other mechanism for handling large files. Particularly for 
Qt 
3D, getting "nice looking" results often requires HDR textures for 
environment 
maps and often other texture inputs too.

Cheers,

Sean
-- 
Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
KDAB (UK) Ltd, a KDAB Group company
Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090
Mobile: +44 (0)7545 140604
KDAB - Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Examples and Demos in qtdoc

2017-06-14 Thread Sean Harmer 
Hi,

On Wednesday 14 June 2017 13:18:35 Frederik Gladhorn wrote:
> Hi all,
> 
> We recently had a discussion in the Qt Company about how we can improve the
> first use experience of Qt and one important aspect are the examples and
> demos.
> 
> We have a lot of examples that are limited by the Qt module they live in,
> for example not making use of ready made buttons in Qt Quick. To allow
> examples to use any Qt module while keeping the build system clean (no
> cyclic dependencies between modules), I'd like to propose using the qtdoc
> module to gather fresh and beautiful examples.
> 
> We currently have a few bigger examples already that would fit this category
> and plan to invest more into good looking nice and welcoming examples to
> give new Qt users a positive first impression.
> 
> Of course we could create a new repo, but considering that we have an
> existing repo which did contain the demo launcher previously and which is
> ready to be used, I'd propse going with it, while the name is not perfect.
> It's already part of the infrastructure and qt5.git, so this seems like an
> easy way to go forward.

I agree that we need something like this. Ideally we also need support for 
git-lfs or some other mechanism for handling large files. Particularly for Qt 
3D, getting "nice looking" results often requires HDR textures for environment 
maps and often other texture inputs too.

Cheers,

Sean
-- 
Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
KDAB (UK) Ltd, a KDAB Group company
Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090
Mobile: +44 (0)7545 140604
KDAB - Qt Experts
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Examples and Demos in qtdoc

2017-06-14 Thread Frederik Gladhorn 
Hi all,

We recently had a discussion in the Qt Company about how we can improve the 
first use experience of Qt and one important aspect are the examples and demos.

We have a lot of examples that are limited by the Qt module they live in, for 
example not making use of ready made buttons in Qt Quick. To allow examples to 
use any Qt module while keeping the build system clean (no cyclic dependencies 
between modules), I'd like to propose using the qtdoc module to gather fresh 
and beautiful examples.

We currently have a few bigger examples already that would fit this category 
and plan to invest more into good looking nice and welcoming examples to give 
new Qt users a positive first impression.

Of course we could create a new repo, but considering that we have an existing 
repo which did contain the demo launcher previously and which is ready to be 
used, I'd propse going with it, while the name is not perfect. It's already 
part of the infrastructure and qt5.git, so this seems like an easy way to go 
forward.

Cheers,
Frederik

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Problems building qtwebkit in 5.9.1

2017-06-14 Thread Harald Vistnes 
Hi,

Has there been a change in the dependencies for qtwebkit in 5.9.1? I am not
able to build it anymore.

I am using these commands:

...
perl init-repository
--module-subset=all,-ignore,-qtwebkit-examples,-qtwebengine,-qtnetworkauth,-qtspeech,-qtandroidextras,-qtvirtualkeyboard,-qtcanvas3d,-qtdatavis3d,-qtcharts,-qtpurchasing,-qtquickcontrols2,-qtmultimedia,-qtserialport,-qtwayland,-qtdoc

configure -prefix %CD%\qtbase -opensource -shared -confirm-license
-debug-and-release -release -opengl desktop -qt-zlib -qt-libpng -no-angle
-qt-libjpeg -icu -skip qtconnectivity -skip qtlocation -skip qtsensors
-skip qtwayland -skip qtserialbus -skip qtserialport -skip
qtvirtualkeyboard -skip qtdatavis3d -skip qtcharts -skip qtpurchasing -skip
qtcanvas3d -skip qtspeech -skip qtandroidextras -skip qtnetworkauth -skip
qtquickcontrols -skip qtwebengine -platform win32-msvc2015 -nomake tests

cd qtwebkit

../qtbase/bin/qmake.exe WebKit.pro

In 5.9.1 I get the following output from qmake:

Running configure tests...

Checking for fontconfig... no
Checking for gccdepends... no
Checking for glx... no
Checking for gnuld... no
Checking for icu... yes
Checking for leveldb... no
Checking for libsqlite3... no
Checking for libwebp... no
Checking for libXcomposite... no
Checking for libxml2... no
Checking for libXrender... no
Checking for libxslt... no
Checking for libzlib... no
Project ERROR: Could not find feature system-jpeg.

I did not get this error in 5.9.0 or in any previous versions.

I am on Windows, but a colleague got the same error on Linux. He also tried
to configure with -system-jpeg, but with the same result.

Thanks,
Harald
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] First Qt 5.9.1 snapshot available

2017-06-14 Thread Jani Heikkinen 
Hi all,

We have first Qt 5.9.1 snapshot available via online installer. It is a 
separate 5.9.1 node, not as an update to Qt 5.9.0. Instructions how to install 
it here: https://wiki.qt.io/How_to_get_snapshot_via_online_installer

Content of the snapshot is based on 
https://codereview.qt-project.org/#/c/196614/, delta to Qt 5.9.0 as an 
attachment.

RTA testing is ongoing and snapshot seems to be pretty much OK. So please test 
the snapshot & report your effort via https://wiki.qt.io/Qt59_release_testing

And please note: We will do regular patch releases for 5.9 series and so on we 
won't block the release because of old issues. Qt 5.9.1 is released on June and 
5.9.2 is targeted to be released on August so if there is still bad issues open 
in 5.9.1 there is time to fix those for soon coming Qt 5.9.2 (or even Qt 5.9.3 
which should be out ~September...)

br,
Jani



qt5.git
9b0e908aca19d58a0d6b6eefebeb7e184437ada5 Build examples with MSVC 2015 instead 
of MSVC 2013
eb58b173e1fcd2f77adc86ee97796eef7a233c74 Enforce MinGW developer build
7456e028a701ff31f63a465fb8fadca63c453b97 Enable CI tests for Boot2Qt
ba1a8d62164df4b3e4c5e18f3356fd246ab00334 Provision macOS disable screensaver in 
current session
5be9b3d2be9d5e0fff1e94fd0c8d5fd52886d30a Add missing ForceDebugInfo -flag for 
winRT x86_64 builds
8df3b0c7ea04ee2b3f68911a4b3a4ce374d8 Build Windows 10 MSVC2015 x86 on 
Windows 10 x64 host
60fb73a1ebffda7a77c4e36a5c385a3fbb8a3615 qtremoteobjects has QML plugins
613242b2bfd0da4afae134615c18fef76c5b54ac Add *.pro.user* to .gitignore
5236e08cd4ce66184a20172dc71dea084caf0023 make -skip work with configure -redo
qt3d
842b8fa5ef41135cc58a98e15d56497482dc5619 Remove redundant code in 
AlphaCoverage/SeamlessCubemap render states
93ea4251c7771f11cf93b47651af3d4ede46d1f2 Fix animation inifinite looping
ab0a43e9efba3da95da2ebc7662a1437d5e3a899 Initialize member variable (found by 
GCC 7)
1a636c7a518d235fc95c822316da4fe640ed7df7 Make render states honor the enabled 
flag
ff6518ebf0bcfe982f4b0e21eb5c3c8d6fc7ea07 Fix GCC 7 warning about case 
fallthrough
e0634ef1eea9db438dd158ce10a19c130cb16249 Normalize Q_ARG to avoid temporary 
memory allocations
511de6d565920b31a135eef67c3714e0dd073a0e Support setting texture format on 
QTextureLoader
68c62e3a8e8bc51bf5353aac7b1b9b42ef5e8c59 tst_QGraphicsApiFilter: Use 
application object
4c9303aa377e45681377997586f0985d5c282bbe Add reference count for backend buffers
95d6847cec8a8c0d5c0013fece507d56c4aee7e6 Fix crash when loading fbx file with 
embedded textures
7e3f60b499ecf4eb40ede1da5c4ddf5b8a0b265e Fix context sharing in scene2d
1e5c704bf01780302607500144b475e4018f7bc5 Fix container detachments detected by 
clazy
76c2f63c2c288774e35fd7257ba2d23df6031276 Doc: add doc to undocumented Qt3D 
classes
1d024678ba16dd979a8c7023b35cdc76db357d37 Fix build with QT_STRICT_ITERATORS
757e26894b5b912bd03ce93b7e538e26f88c9b62 Implement PIMPL for Qt3DWindow
1d03c298fa27e2747fd41a9b5378135d57656fd9 Implement PIMPL for Qt3DQuickWindow
8dfcdb186dd15f2948c02054bdef94f7aafeb412 Document version of assimp library
094e697edbc1195105f05f8aef860d5256622a9a Bump version
qtactiveqt
0544c2b41fdb0a7d7efc9db701bac561e0edf1f3 Unset widget window's parent when 
WM_DESTROY is sent to prevent a crash
9be1fd20859e90c379d517eaf6dfeb55604cd2fa Bump version
qtandroidextras
3b8c84442801ca8989ceb3e57f027ae5c76137c5 Bump version
qtbase
237c867a002c8035aac7ff8a870da717eb7b0878 Doc: Update widget style gallery topic
98057fc6c5455c82844a53b374994c33ee1c1a0e Use upstream at-spi 2
3702b3f68b2dccbdb7203f8a4caeec8578556aba Pick up default library paths for clang
da104aa308c7807e62c137a7972e70e9bf2dbfb2 Android: Remove no-op call to 
processEvents()
235b4cac1da881f55c0bf958965d4812ea49c335 Android: Remove unused struct
b684ed6bd7ae459fe9df24c4da23b25bb199bed6 Android: Properly update geometry once 
the platform plugin is ready
147aa291620d9e2533bbea536a748a8f8a7ed14b Fix sending UTC-offset QTimeZones 
through QDataStream
86a948fc0ff124d2ef03956ac507c923cbb262eb Document that QLoggingCategory is 
thread-safe
5441f399af7880f3957751d1601354aaec802666 Fix tst_QDir::emptyDir
8e776d39ff9fbdf74422ab431a94c0aea6b98cfd Fix tst_qresourceengine for platforms 
with embedded test data
0793dd90d674d0523998750d8dff4bc406780b2f QKeySequence: fix size mismatch
df32c9a1127cfec15aab834cc2df363fa49ca5bd Windows QPA: Port to new feature system
e1a073044855c43ca11e9ada6eedded199c02fc8 QPlainTextEdit: not show place holder 
when having preedit string
510d18d7aedc1c7853292395dd0e6b470570cc9d Update for the newest Darwin-family 
operating systems
dd8313d5be4fe4dd0defdf3eb78e2b47f0e2f20e Translate the adjusted 
deviceWindowRect with an adjusted offset
6a6cdccee43288e2abb6a6e16e4e911062911374 tst_QSharedMemory::readOnly: Skip on 
macOS
d254d8c19714af69a9897bdd67c4e9aa3267c3a3 Use the C++ [[nodiscard]] attribute
6ae801875ea3c654f808b7ed519b403807653068 Re-fix the detection of CPU 
architecture on an Apple OS
bc93ee060abcd746cbed906a51f2379e3da6f379