I guess I'm in the minority amongst computer programmers, who seem to love producing over-arching abstractions that span multiple things, but I really prefer stuff that operates in a limited domain and does it well, to code that spans too much stuff and ends up being mediocre.
That being said, I note that the Qt toolkit will run on some mobile devices, but only Windows Mobile and Nokia S60. So it can't be too hard, provided you target the more feature-rich devices. Honestly, I think that Android native UI layer is pretty compelling - it wouldn't be worth it to me as a developer to ignore all of the extra stuff you get from running platform native there - things like device rotation, integration with the home screen, pen input methods, touch recognisation, etc, all stuff that is mobile specific, but very necessary to deploying on a mobile platform. Regards, Noel. Greg Brown wrote: > Hi all, > > Based on what I have seen so far, trying to get Pivot to run on Java ME seems > like it might be an exercise in frustration. It only supports Java 1.4 (maybe > only 1.3), documentation is difficult to find, and device support appears to > be non-existent. > > However, it may be possible to get it to run on Android. Android supports > Java 5, so that simplifies things. It also appears to be very > well-documented, and there are existing devices capable of running it. The > key challenge would be building an AWT adapter layer such that Pivot > components could draw themselves. It looks like someone has already started > down this path, but it is unfortunately licensed under GPL: > > http://code.google.com/p/awt-android-compat/ > > I imagine that we could do something similar. If we coupled this with an > Android-specific skin (which we would probably do, since mobile device UE is > quite different from desktop UE), we could even be very selective about which > AWT features (i.e. Graphics2D methods) we decide to port. > > So, my questions are: > > 1) Has anyone looked into Android in any depth to know how feasible this > might be? > > 2) How valuable do you think such a port might be? The ability to write an > app that can be deployed both as an RIA and to a mobile device seems pretty > compelling to me, but I wanted to see what others thought. > > Thanks, > Greg > > >
