[Development] a bit big change in qtquickcontrols recently

Koehne Kai Kai.Koehne at digia.com
Mon Jun 17 10:34:04 CEST 2013

> -----Original Message-----
> From: development-bounces+kai.koehne=digia.com at qt-project.org
> [mailto:development-bounces+kai.koehne=digia.com at qt-project.org] On
> Behalf Of Alan Alpert
> Sent: Friday, June 14, 2013 7:39 PM
> To: Bache-Wiig Jens
> Cc: development at qt-project.org; Qi Liang; qt-components at qt-project.org
> Subject: Re: [Development] a bit big change in qtquickcontrols recently
> Note that there are a lot of deployment issues for QML applications that we'll
> probably need to discuss at the Contributor Summit. A few things that come to
> mind are:
> Android: I think I heard somewhere that the assets, like QML files, have to go
> into a different folder than the binary so there needs to be a way to find them
> without an #ifdef ANDROID around your QQmlApplicationEngine
> QNX: File accesses are expensive, it would benefit from bundling up
> everything into one file (or QRC'ing everything) for performance

Weren't 'QML Bundles' designed to solve this issue? Are you, or someone else, still working on them?

> iOS: Stereotypically less open, probably want integrated minifier/obfuscator
> for smaller and less reverse-engineerable packages.
> We need to consider all of these issues for QML-based modules as well, at
> least for all platforms where they need to bundle a Qt with the application
> (which apparently includes desktop now). So I'll assume there will be a
> "spontaneous" session about solving this conveniently for cross-platform (for
> 5.2).

Great, I'll be happy to join that one :)


More information about the Development mailing list