Qt Jambi (Qt java binding) is basically stopped by Nokia. And Qt guys are heading to QML.
Although Android Java UI part is "thin", I am not sure if it is worth the effort to port it to use Qt. Another important thing is Android just employs JAVA programming language NOT java runtime, i.e., it has different runtime and infrastructure. (fyi. I can see problems with many Android technical decisions on its VM, API and infrastructure, not mentioning its closed dev model ) (Here is one reference I like http://www.osgi.org/blog/2007/11/android-and-osgi.html) I'd recommend that if we really need Java on MeeGo, we should stick to standard java (OpenJDK, J2ME, even SWT or swing etc.) though I will stay away from JAVA for UI after spending many years on it :-) Regards, JD On Tue, Mar 2, 2010 at 6:54 AM, Thiago Macieira <thi...@kde.org> wrote: > Em Terça-feira 02 Março 2010, às 14:47:35, Jose Manrique Lopez de la Fuente > escreveu: > > I promise that the android layer is really thin... It is used for the > > UI, and the service underneath has been already tested in java (from > > command line). > > If you say so, I'll have to believe you, because I'll have to assume you > have > already done some initial work in order to estimate. > > I'm basing mine in slideware coming out of Google & Android partners and > looking at the API. > > -- > 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 > > _______________________________________________ > MeeGo-dev mailing list > MeeGo-dev@meego.com > http://lists.meego.com/listinfo/meego-dev > >
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
