Re: Android Qt maturity?

48 views
Skip to first unread message

Willy Gardiol

unread,
Jun 21, 2011, 10:42:34 AM6/21/11
to andro...@googlegroups.com

Hi!
i can answer from my point of view and my experience.

I have a working app for Symbian published on OVI and i am working on
porting in on Android.

The first feeling: its not mature yet (afterall its still ALPHA).
The second feeling: it WORKS and its amazing!

Now to facts.

Good Facts:
Take your Qt app, compile it into Necessitas with very little (if none)
effort IT WORKS on Android. And if you use QtMobility, a lot of stuff is
already Qt native interfacing with the mobile world.

Bad facts:
- Virtual Keyboard works very unreliably (on some phones simply DOES
NOT WORK and no way around it so far i found)
- Themes are unsupported (default white Qt theme, very ugly on Android)
so you have to roll your own stlye, which could be fine.
- Something sometimes crashes and why i dont know (overall 99% stable
tough)
- debugger works ONLY on Android 2.3.1 or newer, narrowing you choices
as debug devices
- screen rotation is awkward to manage (yes you can fix it, but
dinamycally manage it cannot be done)
- No way to go fullscreen (yet)
- no way to map to default Android buttons (like menu)

So on the overall, publishing an app on the Market at the moment i dont
think its feasible without some heavy work (on themes) and still
expecting quite some bad feeback from users... because look&feel will be
different and on some phones things might not work as expected at the
moment.

About necessitas itself, its an amazing and great effort, very
promising (man, besides some quirks, i got my app running in no time)
but still no production ready. After all its called aplha 0.2, you know.

I hope BogDan and all the others working on it will keep the great work
and fix the most oustanding open issues, and i hope they do it fast too.
I am also ready to give some money to the project if possible...

I cannot help in developing necessitas, no time not even for my app,
but i would if i could.

On Tue, 21 Jun 2011 08:43:08 -0500, Samir Faci wrote:
> Hello all,
>
> I was thinking about developing an app using android-qt rather
> then
> the standard android SDK, and I was hoping
> the list could give me some feedback as to their views on how stable/
> mature this project is.
>
>
> One of the appeals of Qt is the portability of the application,
> ability to run it on windows, Linux, mac, meego, and now it seems
> even
> qt.
>
> Has anyone written and published an app written in qt on the market?
>
> I was also wondering on the state of NFC support on qt+android.

--
Willy Gardiol
wi...@gardiol.org
www.gardiol.org
www.trackaway.org -> Track YOUR way the way you want!

Samir Faci

unread,
Jun 21, 2011, 9:43:08 AM6/21/11
to andro...@googlegroups.com
Hello all,

I was thinking about developing an app using android-qt rather then
the standard android SDK, and I was hoping
the list could give me some feedback as to their views on how stable/
mature this project is.


One of the appeals of Qt is the portability of the application,
ability to run it on windows, Linux, mac, meego, and now it seems even
qt.

Has anyone written and published an app written in qt on the market?

I was also wondering on the state of NFC support on qt+android.


--
Samir Faci
*insert title*
fortune | cowsay -f /usr/share/cows/tux.cow

Sent from my non-iphone laptop.

Josh

unread,
Jun 21, 2011, 4:48:18 PM6/21/11
to android-qt
On Jun 21, 2:43 pm, Samir Faci <sa...@esamir.com> wrote:
> Has anyone written and published an app written in qt on the market?

I have. It's still beta but usable I think.

With some tweaking I managed to get a bit of touch-friendlieness in.
It *is* possible.

I never bothered about mimicking Android style; if the application is
O.K. and there are some controls that you can use in a similar way as
in the native OS ("Back"/"Menu" key, list flicking), the design should
be of lower importance.

See "Cumulus for Eclair/Froyo/Gingerbread". Mind that it's for large
screens only (800x400 and up).

Shantanu Tushar Jha

unread,
Jun 22, 2011, 12:01:21 AM6/22/11
to andro...@googlegroups.com
Hi,


On Wed, Jun 22, 2011 at 2:18 AM, Josh <alcesa...@googlemail.com> wrote:
On Jun 21, 2:43 pm, Samir Faci <sa...@esamir.com> wrote:
> Has anyone written and published an app written in qt on the market?

I have. It's still beta but usable I think.

IIRC, BogDan had requested that we don't put necessitas powered apps on the market as of now. Or was that very long time ago and is not the case now?

BogDan Vatra

unread,
Jun 22, 2011, 1:58:11 AM6/22/11
to andro...@googlegroups.com
Hello,

Please accept my apologize for the slow replay.

Pushing QT apps to Android market is very risky now, because we are
not very happy with current QAtomic implementation, so, if we'll
change it, all your apps will stop working.
There are not too many thing to do before we release a beta version,
which will guarantee that *any* app which will use it will run on any
newer version, we had a session last week and a lot of people are now
working to make it happen very soon here [1] you can find a wiki page
with more information.
We are investigating a way to "replace" also some pieces of your app
java part using Minsitro, this way we can update your java part
seamlessly, without forcing you to update your application on Android
Market.

Cheers,
BogDan.

[1] http://community.kde.org/Necessitas/Meetings/QtCS2011

2011/6/22 Shantanu Tushar Jha <jhah...@gmail.com>:

Gerhard Gappmeier

unread,
Jun 22, 2011, 3:39:21 AM6/22/11
to andro...@googlegroups.com
Hi BogDan,

I was just wondering when I read, that there are problems with QAtomic.
Can you explain that further?
I thought also normal Desktop Qt would support ARM already.

If not, there are plenty of resources which show how to implement atomic operations on ARM.
E.g. this:
http://www.hpl.hp.com/research/linux/atomic_ops/
and the linux kernel of course ;-)

regards,
Gerhard.
--
mit freundlichen Grüßen / best regards

Gerhard Gappmeier
ascolab GmbH - automation systems communication laboratory
Tel.: +49 9131 691 123
Fax: +49 9131 691 128
Web: http://www.ascolab.com
GPG-KeyId: 5AAC50C4
GPG-Fingerprint: 967A 15F1 2788 164D CCA3 6C46 07CD 6F82 5AAC 50C4

--
ascolab GmbH
Geschäftsführer: Gerhard Gappmeier, Matthias Damm, Uwe Steinkrauß
Sitz der Gesellschaft: Am Weichselgarten 7 • 91058 Erlangen • Germany
Registernummer: HRB 9360
Registergericht: Amtsgericht Fürth

BogDan Vatra

unread,
Jun 22, 2011, 4:12:02 AM6/22/11
to andro...@googlegroups.com
Hi Gerhard,

Here [1] I tried to explain what was "wrong" with current Qt ARM v5
implementation.
Currently this issue is "assign" to Bernhard, so if you want to help
on this topic I
recommend you to join Necessitas devel mailing list [2] and begin a
discussion there,
We created another mailing list special for this kind of topics.

Thank you.

Cheers,
BogDan.

[1] http://community.kde.org/Necessitas/TODO#QAtomic_implementation
[2] https://mail.kde.org/mailman/listinfo/necessitas-devel

2011/6/22 Gerhard Gappmeier <gerhard....@ascolab.com>:

Josua Dietze

unread,
Jun 23, 2011, 1:13:50 PM6/23/11
to andro...@googlegroups.com
Am 22.06.2011 05:01, schrieb Shantanu Tushar Jha:
> IIRC, BogDan had requested that we don't put necessitas powered apps on the
> market as of now. Or was that very long time ago and is not the case now?

I'm not using Necessitas. I'm delivering bundled local libs and have disabled
the Ministro stuff, so users will not be surprised by any automatic library updates.

I will change this as soon as QScroller is part of Qt and the remaining
obstacles for deployment are removed.

Josh

Reply all
Reply to author
Forward
0 new messages