Skip to content

Conversation

@tobiasdiez
Copy link

We are discussing internally which frameworks and techniques to use for JavaFX. This PR is a proposal of afterburner.fx and MVVM.

You can ignore it for the moment. But since you guys also have some experience using JavaFX, we would welcome your input and feedback.

Observations so far:

  • afterburner hides almost all the boilerplate code for loading fxml + css + resources
  • almost no doc avaible for it...but as soon as the initial configuration is finished, this is not a big miss
  • Depency injection removes global dependencies quite effectively and makes testing a brezze
  • FXML has its disadvantages (no compile-time check of binding expressions)
  • MVVM works quite effectively with JavaFX binding and is perfect for testing (there is actually no difference anymore between testing GUI code and normal code)

boceckts and others added 6 commits March 14, 2016 20:59
The old dialog and html layout file have been removed. The layout of the
dialog panel is defined in the AboutDialogLayout.fxml located in the
resources with its stylesheet. The AboutDialogController class takes
care of the text initialization of any components in the layout. It also
implements any methodes called from any component of the dialog panel.
@boceckts boceckts force-pushed the AboutDialogFX branch 5 times, most recently from 729c7ca to 9907d3a Compare April 26, 2016 08:54
@tobiasdiez tobiasdiez closed this Apr 29, 2016
boceckts pushed a commit that referenced this pull request Jul 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants