Don't you think the qt libs are a little too big?
Morr. Liang
is 5.5M. So if I create an app which takes 3M, well, I have to deploy
10M files to the user's cellphone. I consider that's not acceptable.
Well, you may say that the libs are shared among every Qt Apps. But in
an Android phone, I don't really expect people would have many Qt
Apps. So if a user ever installed 2 Qt Apps, the 7.5M is still a huge
overhead, not to mention the other libs.
In a country with low bandwidth like China, don't think about the user
would install your app if you ask him to download 10MB files before
the installation.
So, do you guys considering cutting down the size of qt by removing as
many things as possible ?
Ross Bencina
>I just checked the release version of the qt libs, QtCore is 2M, QtGui
> is 5.5M. So if I create an app which takes 3M, well, I have to deploy
> 10M files to the user's cellphone. I consider that's not acceptable.
Those lib sizes are smaller that what I get on Windows (2.1M, 8M).
Perhaps they can be put on a diet.. but with Qt you have to accept that the
runtime is not small. That's why we have Ministro
> Well, you may say that the libs are shared among every Qt Apps. But in
> an Android phone, I don't really expect people would have many Qt
> Apps. So if a user ever installed 2 Qt Apps, the 7.5M is still a huge
> overhead, not to mention the other libs.
For me I don't care.. storage on new phones/tablets is bigger and my app
binary (without libs) will probably be 5M (this is a real desktop app ported
for tablets). I think the conclusion for you should be:
If you can use Java for your app, don't use Qt.
> In a country with low bandwidth like China, don't think about the user
> would install your app if you ask him to download 10MB files before
> the installation.
>
> So, do you guys considering cutting down the size of qt by removing as
> many things as possible ?
I'm not sure what can be removed? Perhaps non-Android QStyle subclasses and
resources are still in there?
Ross.
Morr. Liang
Martin Koller
> Code bloat in Qt is really a headache for me.
compile Qt on your own and disable all stuff you do not need:
http://doc.qt.nokia.com/4.7/fine-tuning-features.html
--
Best regards/Schöne Grüße
Martin
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Geschenkideen, Accessoires, Seifen, Kulinarisches: www.bibibest.at
Alessandro Portale
> I'm not sure what can be removed? Perhaps non-Android QStyle subclasses and
> resources are still in there?
the styles occupy a few hundred KB. All icons exist in 16/32/128 pixel
sizes, and there many desktop related icons like CD-ROM. That's why
wince and symbian have a reduced icon set, with less size variants:
http://qt.gitorious.org/~taipan/qt/android-lighthouse/blobs/android-stable/src/gui/styles/styles.pri#line26
Android-qt could imho reuse qstyle_s60.qrc which just includes the 32-
pixel versions of mobile relevant icons:
http://qt.gitorious.org/~taipan/qt/android-lighthouse/blobs/android-stable/src/gui/styles/qstyle_s60.qrc
...on Symbian that shaped away about ~250 KB from QtGui.
Alessandro
Morr. Liang
Alessandro Portale
fallback icons are (only) needed to support the complete Qt API on all
platforms even if the underlying platform does not provide native
icons.
Qt's cross-platform promise: An application that uses icons on
platform A should be able to function on platform B.
Many ports of Qt (even the Symbian port in part) get the native icons
from the system. If the system does not have a specific Icon, the
fallback icon is used.
Now the question is if Android has an API to provide such icons. And
can the QAndroidStyle access that Api? And which icons from this list
http://doc.qt.nokia.com/latest/qstyle.html#StandardPixmap-enum are not
supported by Android and need a fallback? Perhaps, it is possible to
reduce the fallback icons even more than on Symbian and still keep
Qt's cross platform promise.
On 11 Mrz., 11:45, "Morr. Liang" <liangm...@gmail.com> wrote:
> I don't see why we should even keep the 32px icons. Nowadays, UI is becoming
> more and more important and fallback icons just don't make good UIs...
>
> > On 11 Mrz., 05:14, "Ross Bencina" <ro...@audiomulch.com> wrote:
> > > I'm not sure what can be removed? Perhaps non-Android QStyle subclasses
> > and
> > > resources are still in there?
>
> > That's a very good point to start the diet. Just the fallback icons of
> > the styles occupy a few hundred KB. All icons exist in 16/32/128 pixel
> > sizes, and there many desktop related icons like CD-ROM. That's why
> > wince and symbian have a reduced icon set, with less size variants:
>
> > Android-qt could imho reuse qstyle_s60.qrc which just includes the 32-
> > pixel versions of mobile relevant icons:
>
Morr. Liang
Joel Dillon
You might want to investigate qt embedded's qconfig.h which let's you strip out features...but really, Qt is big. It's just how it is if you want to share it between apps.
On Mar 10, 2011 11:14 PM, "Ross Bencina" <ro...@audiomulch.com> wrote:
Morr. Liang wrote:
>
> I just checked the release version of the qt libs, QtCore is 2M, QtGui
> is 5...
Those lib sizes are smaller that what I get on Windows (2.1M, 8M).
Perhaps they can be put on a diet.. but with Qt you have to accept that the runtime is not small. That's why we have Ministro
> Well, you may say that the libs are shared among every Qt Apps. But in
> an Android phone, I do...
For me I don't care.. storage on new phones/tablets is bigger and my app binary (without libs) will probably be 5M (this is a real desktop app ported for tablets). I think the conclusion for you should be:
If you can use Java for your app, don't use Qt.
> In a country with low bandwidth like China, don't think about the user
> would install your app...
Alessandro Portale
> Now the question is if Android has an API to provide such icons. And
> reduce the fallback icons even more than on Symbian and still keep
> Qt's cross platform promise.
needed icons via "Drawables":
http://androiddrawableexplorer.appspot.com/
And there are also the theme bits which can be used by QAndroidStyle
to make QWidgets (or even the "native aware" QML components
http://labs.qt.nokia.com/2011/03/10/qml-components-for-desktop/ ?)
look native.