[Qt-interest] Qt for the iPad?

[Jason H]

That is ingenious! 

And you are right, Mobility definitely has that ability. I am wondering how QtMobility would interface with the device HW. If everything is made accessible via Java, then there would need to be a Qt/Java bridge... This is beyond my knowledge at this time. Anyone have an idea how that hardware interacts with the java apps?



----- Original Message ----
From: Thiago Macieira <thiago at kde.org>
To: qt-interest at trolltech.com
Sent: Mon, April 12, 2010 3:45:44 PM
Subject: Re: [Qt-interest] Qt for the iPad?

Em Segunda-feira 12. Abril 2010, às 20.17.38, Jason H escreveu:
> Maybe focus moves to Android now? If I could straddle two platforms (Nokia.
> Google) it would still be worth it to me.

There is also a community port of Qt to Android and they have already managed 
to get applications running. The solution they found was to make the 
application an .so and place it inside the .jar file, alongside a stub loader 
that calls out to your C++ code. Quite an ingenious solution, if you ask me.

The big advantage of Android is that it's Linux, so most of the code in Qt 
simply works out of the box. And with the Lighthouse project, the UI part is 
coming along nicely.

The disadvantage is that it's not like any other Linux. The libc is broken, 
pthread support is lacking, etc.

> However, QtMobility would need
> to be outfitted with a lot of Android dongles, and I don't think Mobility
> is ready for that yet... 

Mobility has been designed from day 1 to have different backends, depending on 
the platform. This would require only writing of such backends for Android.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358