Javafx Gridpane Builder Benefits

Update - collectors are deprecated

Regarding builders in general, the JavaFX project manager writes :

Deprecated in 8 and removed from JavaDoc, departed in 9 (will be available as a separately downloadable Jar so you can continue to use them, but they will not be updated). We remove them from samples.

Your best bet is to turn off Builders.

Builder classes in JavaFX provide a fluent interface to functionality. Such an API is often easier to read than the required code.

Fluent APIs are declarative in nature, and it is often easier to write declarative code without errors than stateful imperative code .

A Builder instance can be created as a template and the same instance reused over and over again, as well demonstrated in The JavaFX Builders Benefits .

JavaFX Builders also define attributes that can be used in an FXML document. For more information on this usage, see the Builders section of Introduction to FXML .

In some areas where Builders might not be enough in JavaFX 2.2 versus the imperative API, follow these steps.

• Builders don't make it easy to bind properties.
• The Builder APIs may be incomplete for all features.
• Builders can use generics that are difficult to understand.
• Builders do not allow static constraints on objects.
• For simple ads, builders are more verbose than their peers.

Example point 4 is that the Builder does not have a method equivalent like GridPane.setVgrow (precedence) .

As for the GridPaneBuilder , specifically using the GridPane - it has the same advantages and disadvantages as other developer mappings rather than mandatory API mappings, however the GridPaneBuilder is a little more dejected than some other developers as it only provides a subset of the interface functionality The GridPane is primarily because the GridPane relies heavily on static methods to specify layout constraints and the equivalent functionality does not appear in the Builder.