Its important to recognise that QtQuick and QtWidgets are _different_ systems. Quick is all on the GPU. It awesome for building touch based apps. I'm currently targeting desktop development. I haven't found much else that will use the GPU pipeline in an easy way.
* Javascript. Ew.
* Deployment is a bit of a nightmare. They have windeployqt.exe which helps, but it doesn't automatically copy the MingW DLLs, and all the QML files aren't compiled as resources which is a bit ugly.
* The apps are huge. It's like 50 MB for hello world.
* There isn't very good encapsulation of QML components. All object IDs seem to go in one big namespace.
QtQuick controls on other hand can't be styled using CSS, which is bit of a bummer IMO.
Thanks for the tip.
I put my own QML into resources, but windeployqt.exe pulls in a big chunk of their own QML into the deployment. huh? these should all be resource.
My "hello world" app is 30MB, so yes this too.
Also you can include QML files as resources using qrc and they will compiled into the binary.
1. JavaScript: is there only to facilitate manipulation of Items and elements. Use C++ for any logic
2. Deployment: Yes
3. Size: Yes
4: This sounds like you're doing it wrong. IDs are scoped to their context (usually the item and on down)
This doesn't sound right. Can someone else verify? I'm pretty sure I've written Android applications in QML that are far smaller. Are you sure these are release binaries?