Making JavaFX Development Faster

[Mark Fortner]

The article that Will pointed out was interesting.  However, the developer
would still end up having to write code to make their POJOs or POJO
collections observable.  It would be nice if there was a "dynamic proxy"
that automagically made any class you sent it observable.  Not sure how
doable that is -- just thinking off the top of my head.

The one thing that you would need to avoid is making your POJO have any
JavaFX dependencies.

On the issue of RAD tooling, it sounds like the Griffon team is making some
progress with respect to making JavaFX easier.  I'm not sure how well
Griffon's Service and Controller interfaces map to JavaFX's Controller.

Cheers,

Mark




On Thu, Oct 18, 2012 at 11:21 AM, Richard Bair <richard.bair at oracle.com>wrote:

> Another option I would guess is to not use observable objects at all, but
> you can still use binding (the property adapters should work with that).
> Even with a list view, which has an ObservableList, you can add items form
> a normal list and vice versa.
>
> On Oct 18, 2012, at 10:39 AM, Mark Fortner wrote:
>
> > One of the big timewasters when it comes to JavaFX projects taking your
> > server-side POJOs, creating Observable versions of them, and creating
> > forms, and controllers for them.  If you've been doing JEE development in
> > the past 5 years then you're probably already using Spring ROO, Grails,
> or
> > some other RAD tooling that makes this type of work trivial in the web
> > world.  All of these artifacts are usually generated directly from the
> > POJOs.
> >
> > So I'm curious if anyone knows of any tools that make that process easier
> > and faster?
> >
> >
> > Cheers,
> >
> > Mark
>
>