The application didn't really benefit from fullscreen, as it had infinite scrolling before we were all gawping at Twitter doing it. And in 4 directions.
It would have been useless for blind people, as it was deliberately aimed at sighted users. In fact, the way I wrote it ignored Swing's accessibility APIs, so I actually wasn't using the support that you're complaining doesn't exist. Regarding cross-platform UI being a quest for the lowest common denominator, I think that overstates the differences there are between the platforms we actually use. On an unrelated note, I just can't beat you on a particular level of Angry Birds that you probably didn't even know I was trying to beat you on. Grr. :) On Tue, Dec 6, 2011 at 2:04 PM, Casper Bang <[email protected]> wrote: >> To be fair, I had a Swing app running on Macs with no problems 5 years >> before I first used a Mac, so I think it delivered on that front. > > > Java tried, but it failed. And really, how could a unification of UI/UX > across different OS be anything than the never-ending quest for > lowest-common denominator?! > > To continue your Mac example: Try to run your Swing app on OSX Lion and > notice how it's unable to go into fullscreen mode. Or try letting a blind > person, with a screenreader, navigate your (emulated) Swing UI. > > It's a pipe dream and no successful application I can think of, make use of > a cross-OS UI toolkit. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
