phidias51 at gmail.com
Tue Oct 16 09:44:11 PDT 2012
Thanks for the link Will. The idea behind baking in JSON support is to make
it easy for people with existing "libraries" of RESTful services to be able
to quickly wire up a JavaFX GUI, and make a potential transition from
HTML/HTML5 to JavaFX as easy as possible. It's a powerful when you can
take an HTML UI and quickly put together the JavaFX equivalent and reuse as
much of your existing codebase as possible.
On Tue, Oct 16, 2012 at 9:09 AM, Danno Ferrin <danno.ferrin at shemnon.com>wrote:
> On Mon, Oct 15, 2012 at 4:29 PM, Daniel Zwolenski <zonski at gmail.com>wrote:
>> > Once the basics are sorted out, it would be good to re-examine how
>> > developing JavaFX apps could be made even easier with Maven. For
>> it might be nice to autogenerate these "Observable" POJOs from POJOs that
>> > already exist and are being used on the server. Imagine having the
>> > version of Spring ROO or Grails where the forms and controllers you need
>> > are automatically generated. This would make it easier the prospect of
>> > transitioning to a new toolkit less daunting, and make it possible to
>> > on the infrastructure and services that you already have in place.
>> Some RAD tools would be awesome. I don't think this is Maven's space
>> but definitely within the ROO and Grails space. SceneBuilder is the 'RAD'
>> tool of the JFX platform but it is basically an FXML WYSIWYG editor.
> The JavaFX version of Grails is called Griffon. --
> It is substantially derived from Grails (i.e. the first 0.0 release had
> large poritons cut and pasted, I would know).
> There is nothing that will hold me back. I know who I am....
> I remember wher I came from, and I feel stronger for knowing.
> Zane, Ninja of Ice. Ninjago S01E07
More information about the openjfx-dev