0.4.0

This release has a focus on the Guice and CDI modules. The goal was to stabilize the API for these extension modules.

New Features

#136 The CDI and Guice modules now have a unified API. In both variants the user now can use the three methods initMvvmfx(), startMvvmfx(Stage stage) and stopMvvmfx() to implement the application bootstrapping and shutdown. The standard methods from javafx.application.Application (init(), start(Stage stage) and stop()) can't be used anymore as they are now final in both modules.

#130 The primary stage can now be injected in Guice/CDI applications out of the box. This can be useful for example when you like to create modal windows and dialogs.

#128 The application parameters that are passed into the main application are now injectable in Guice/CDI applications.

#50 There is now a maven archetype that can be used to setup new mvvmfx-based applications.

API breaking changes

#136 The init, start and stop method signature for the CDI/Guice modules have changed (see above for a detailed explanation).

#142 ViewListCellFactory is now a functional interface and not an abstract class anymore. This way it is possible to use a lambda expression. In most use-cases this change won't break existing code because anonymous inner classes still work. Only when you have extended from the abstract class ViewListCellFactory the code will break. Instead you have to implement the interface now.

#132 In version 0.3.0 the ViewLoader was marked as deprecated. In this version the class was removed. Use the FluentViewLoader instead.

#117 The class ListTransformation is now matching the JavaFX bean conventions.

Minor changes

#127 In guice applications the method initGuiceModules is now optional. Old code using this method is still working. The only difference is that with the new version you aren't forced to override this method if you don't want to define own guice modules.