[Android-development] On False Promises ...

Rubi Mazaki rubimazaki at gmail.com
Tue Jan 7 17:25:04 CET 2014


AFAIK https://bugreports.qt-project.org/browse/QTBUG-35529 regards to the
way the examples are shipped, which is less critical in my opinion. The
problem with the Android installation is that it provides examples that
don't work 90% of the time. And that's really bad. As to the android tag, I
must say that the existence of the tags was not something I was much aware
of until now, so I guess that is the experience of a new/desktop Qt user,
trying to start mobile dev.

Regarding the AndroidManifest.xml - I guess it would be great if qt builder
would handle the permission management automatically, but as it seems,
after running a number of samples, non of them installed with any
permissions. So, it seems that Qt just don't handle this, which is
critical. WORSE, to override the AndroidManifest one must go and find the
right line to write in the .pro file, a line that is not documented:

*in QMAKE:*
*ANDROID_DEPLOYMENT_DEPENDENCIES*=<dir_conaining_AndroidManifest.xml_path>

*in QBS (available?)*
MANIFEST command line variable

It was far and hard to get to these commands too. Not too documented
AFAIK...

Consider also, that the AndroidManifest.xml contains many parameters for
the application, including if it would run in portrait/landscape mode
(currently defaulted to landscape... which means the applications will run
like games on the side of the screen - not really the most useful settings
unless it's a tablet)




With Regards,

Rubi Mazaki
Email: rubimazaki at gmail.com


On Tue, Jan 7, 2014 at 4:58 PM, Eskil Abrahamsen Blomfeldt <
eskil.abrahamsen-blomfeldt at digia.com> wrote:

> On 01/07/2014 09:25 AM, Rutledge Shawn wrote:
> > Anyway if you go to the examples on the Creator Welcome screen, some
> examples have an android tag (see the list of tags under each thumbnail).
>  If you click on one of the android tags it will put tag:"android" as a
> search criterion so that you see the examples which have been deemed
> appropriate for android.  So we can consider it a bug if some examples
> which don't work well are tagged that they do work on android, and we can
> talk about whether the filtering should be chosen by default when you
> choose a kit, but at least there is a filter already.
>
> Just note that this list is not 100% correct at the moment. Some of the
> examples that are not tagged "android" work well, and some of the
> examples that are tagged "android" will work, but will not be very
> appropriate for showing how to do mobile development. So the list needs
> to be updated and cleaned, but there hasn't been time to do that yet.
>
> -- Eskil
>
> _______________________________________________
> Android-development mailing list
> Android-development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/android-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/android-development/attachments/20140107/b432d888/attachment.html>


More information about the Android-development mailing list