Summary

Conclusions

JavaFX combines a tree of nodes, automatic layout, and events. Code creates behavior, FXML describes structure, and CSS defines styling. Short handlers and separate pure computations simplify testing and prepare the application for MVC.

Self-check questions

1. How does a Stage differ from a Scene?
2. Which actions must not be performed in init?
3. Why is setOnAction better for an ordinary button?
4. How does a VBox determine the placement of its children?
5. Why is runLater not a background thread?
6. When are a controller's @FXML fields already initialized?
7. Why is opens needed for a controller's private fields?
8. Which checks must be repeated for the built image?