FXML Patterns / best practices (original) (raw)

Werner Lehmann lehmann at media-interactive.de
Fri Feb 24 02:07:19 PST 2012

Dan,

I second that. Currently I don't see that value in the FXML controller in the general case. I can only imagine that a big scene graph with lots of controls and handlers might justify a separate controller to split code in smaller peaces. But if it only passes things around...

Rgds Werner

On 24.02.2012 05:58, Daniel Zwolenski wrote:

Looking at this proposed implementation, we've now got FXML in there for building up our Scene Graph, which is fantastic but the need for this extra FXMLController is a new cost. It is an extra file (which I have no problem withso long as it adds value), and also means we still have Java files within the designer's domain (i.e. the plumbing of our View).

More information about the openjfx-dev mailing list