The moral of the story is that Griffon and JavaFX are not competing technologies, as a matter of fact they can work together, there is no need to be asking yourself "should I go with Griffon or JavaFX for my next application?", go with both! (if that meets your application's requirements). I'd like to show you that integrating JavaFX into a Griffon application via FxBuilder is not that hard a task.
1. First you need a binary distribution of FxBuilder, which is not yet officially available. However you can download a copy of the sources [http://svn.codehaus.org/griffon/builders/fxbuilder/trunk/] and build one yourself.
2. Create a new Griffon application with griffon create-app, I went with fx as the applicaiton's name.
3. Copy FxBuilder's jar along with all JavaFX jars into fx/lib.
4. Edit griffon-app/conf/Builder.config, add a definition for FxBuilder, your file should look like this
5. Edit griffon-app/views/FxView.groovy, replace its contents with the following script
6. Run the application by typing griffon run-app, you should see a screen similar to this one

Once you click on a button it's text will be changed, this is achieved by wiring a Groovy closure, not a JavaFX function, as you can observe on the button definitions. Here is another look at the application once the buttons have been activated a few times

There you have it, there are however some caveats to using FxBuilder in its current state
- FxBuilder relies on JavaFX SDK 1.0, work needs to be done to upgrade it to JavaFX SDK 1.2
- FxBuilder is capable of wrapping any swing component and embed it into a JavaFx Scene but only on standalone mode, this won't work with Griffon's composite builder (yet).
- FxBuilder does no support the full range of shape nodes nor effects found on JavaFX SDK 1.0.
There is chemistry between Griffon and JavaFX, sadly I cannot devote to this builder as much time as I'd like, if anyone is willing to help getting this puppy up to date with the latest JavaFX SDK please drop me a line, much appreciated

Keep on Groovying!