A modern programming language that makes developers happier.

kotlinlang

<@U6VG0BB54> I have mixed feelings about FXML.  On the one hand, I saw graphic designers produce usable JavaFX code (still in use after 4 years) and perform a clean handoff to developers.  Also, Scene Builder is great for prototyping.  Just drag a few components on the screen and press Control+P.  Works with complex nested screens too.   The XML has been highly compatible through the years.

However, the most recent versions of Scene Builder I worked with had a bunch of bugs: problems opening more than one instance, not being able to resize the window after launching, not being able to drag-and-drop from the hierarchy after a while.  I sometimes use an older Oracle version.

With TornadoFX, you'll hit a wall with FXML support that IMHO will make it unsuitable (TornadoFX + FXML, that is) for larger projects which is nesting.  See <https://github.com/edvin/tornadofx/issues/243>.  Any rich UI app is going to need nesting as a way to break apart its complex view code.

So, I would stick to the app design of Views and Fragments and the Builder Pattern.  There is something called the Layout Debugger which is handy when prototyping.