Re: Is the NetBeans Platform the best choice for a JavaFX only desktop application?

I would not recommend Griffon for large applications that need to be 
modular, pluggable, extensible, etc.

You can keep writing back about the NetBeans team needing to replace 
Swing with JavaFX, as long as you want -- however it's not going to 
happen. We have many feature requests and other priorities to work on. 
We don't believe the amount of work that will be needed to do this is 
worth the effort. Anyone out there is welcome to create alternative 
implementations on top of the NetBeans Platform, like Sven has already 
done, and you're welcome to join that project and extend it further.

Gj

On 28-6-2016 15:30, Marcelo Ruiz wrote:
> Thanks for the answers!
> Some of the characteristics of the app (not in order of importance) are:
>
> - Look should be consistent and easily customizable from the user side
> - Heavy use of data stored in a database, with part of that data represented visually through charts and images
> - Easy to update
>
> The app would definitely benefit from the NetBeans module system and windowing system (with heavy use of the docking modes). The hybrid approach will be a big problem from the customization point of view. I completed the Simpson's app example from JavaFX Client Programming for the NetBeans Platform but, IMHO, it does not look good and consistent from a visual point of view.
> Please feel free to share your thoughts. I don't mind if your are biased.
> I got a suggestion to look at the Griffon framework to create a pure JavaFX applicaiton, but if I can avoid recreating the window system it would be great... I believe Geertjan was involved with that project at some point so he might be able to share his thoughts about it.
> I wish the NetBeans team could refactor the code somehow so swing could be replaced by JavaFx. I know it might be impossible at this point... but I can't help dreaming!
> Again, thanks for your thoughts, they're really appreciated.
>
>
>
>