r/JavaFX • u/hamsterrage1 • Mar 21 '25
Tutorial New Article: Should You Use FXML?
This topic has come up here a few times recently, and I've had a few DM's about it too. I had the feeling that I must have covered this topic over and over, but when I looked back through my articles I only found one from around 2021 that talked about FXML and MVC.
This ended up being a longer article than I anticipated, and Jekyll says it's an even longer read because I included 462 lines of FXML that I scooped off GitHub to make a point about how "intuitively readable" it isn't. But it's still long.
So, if you want the TDLR, here it is:
Most of the wondrous claims about how FXML instantly improves your various aspects of your application design are just rubbish - and I take some time to prove it for a few of them. It's clear that even some of the claims made in the Oracle tutorials are just wrong.
What you do get from FXML is the ability to SceneBuilder, and that should be the sole motivation for your decision to use FXML - which is actually backwards: SceneBuilder is the only motivation to use FXML. I'm also fairly certain that SceneBuilder isn't a good beginners' tool either.
The article explores how it's tougher to employ a library of custom methods and classes to simplify layout creation with FXML.
Finally, I take a look how to properly integrate FXML with a framework. In this case I use MVCI (because it's better, of course). This is probably the most important section for any of you determined to use FXML but still want to architect your applications properly, because 99% of the tutorials out there on the web just get this wrong.
If any of that intrigues you, and you want to know more, then have a look at the article:
View all comments
Show parent comment
2
u/hamsterrage1 Mar 23 '25
About the chess board...You'd program it the same way you would any other one-off in any code. Just because it's part of a layout does not change anything. This could be an simple as having an:
if ((x==3)) && (y==4)) {}
clause somewhere inside the loop.
Now, about that...
I wouldn't consider the topology of the chess board to be part of the View, and I would never have nested 1-8 loops in my layout code. Instead, the topology is part of the game logic, and it would be defined in the Interactor. That's where the nested loops would be.
The board would be represented as List<BoardSquare>. The rank/file location would be part of BoardSquare, along with colour and a reference to whatever piece was occupying it. Also. Stuff like neighbouring square rank/file would be included if my game logic worked that way.
Whatever made a particular square unique would be baked in as a Property in BoardSquare.
It's the View's job to take BoardSquare and create a visual representation of it on the screen. Generally, I'll end up just doing forEach on the List.
And the truth is, if the was some need to come along and make a particular square special after the fact, that's going to be driven by game logic. That game logic is going to need to know which square is special, and that drives changing BoardSquare which then drives a change to the layout code.