I've been using JavaFX for about 3 or 4 days now and I find that I really like it. I was able to pick it up almost instantly. Perhaps this is because I worked on a project a few years ago that tried to do something similar. (XML to Swing compiler, but this WAY better).
In my opinion it provides a nice clean separation between the model the view and the controller. I think the best part is that you can specify the view UI using FXML which looks a heck of a lot like HTML and even handles CSS & Javascript correctly. In my book this means I can leverage existing web artists and designers by farming UI work out to them, without a major learning curve and without needing to code umpteen million lines of boiler plate glue logic. This leaves me free to work on the application design and the back end logic, which is the part I enjoy the most. As I said before, there doesn't seem to be a need for glue code, and the new Task & Service classes mean I don't have to stress the swing Event Dispatch Thread or deal with the clunky Swing Worker model. In fact I'm really just waiting for the other shoe to drop. I'm considering JavaFX for a much bigger application and possible inclusion in my long term toolkit of things I recommend to clients. Language wars aside, does anyone know of any major gotchas or limitations in JavaFX I may be looking at compared to say Swing, SWT or AWT? Thanks! /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
