Sounds like a nice dream. The swing API is completely unrealistic for such a thing, though.
Actually, the swing API is unrealistic in general. There's a reason JavaFX exists. On Sep 13, 7:45 pm, Mark Fortner <phidia...@gmail.com> wrote: > Actually, Swing on the phone does make a lot of sense. I've often thought > though that we should have a context-independent graphics toolkit. Imagine > for a moment, if you could create an application complete with a UI and run > the application on a server, on a desktop, or on a phone. The context would > determine how to render the UI that you provide. If you want to run the app > on a server, it might render the UI classes using GWT; if you want to run it > on a phone, it would use whatever native toolkit is provided (same thing > with the desktop). > > This is similar to the approach that AWT took when it made use of native > peers. The only problem for Sun was that they had to appeal to the lowest > common denominator amongst the different UI toolkits. But I'm sure the > current toolkits could provide better peers nowadays. > > Cheers, > > Mark > > card.ly: <http://card.ly/phidias51> -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
