🚧 Work in progress 🚧 Please view the Wiki here
What's new? Release notes
- 1.5.0 10/30/2024 - New support to get view model from a JFXNode record, new ways to monitor change and invoke validators on change.
- 1.4.0 10/18/2024 - New support to get properties as common JavaFX properties. Avoids down casting.
- 1.3.0 09/04/2024 - Enums for property name lookups. Added SLF4J, JUnit5, began unit tests.
- 1.2.0 08/05/2024 - Validators support multiple validation messages.
- 1.1.0 06/28/2024 -
PropertyIdentifiertype objects to reference properties. - 1.0.0 05/30/2024 - Initial Release.
FXMLMvvmLoader,SimpleViewModel,ValidationViewModel,Validator(s).
A lightweight JavaFX (21+) forms framework based on the MVVM UI architecture pattern.
View Model(s) maintain the state of a view (Form) and, in principle, should contain a controller's presentation logic. MVVM allows the developer to test the presentation logic without having to wire up a JavaFX controller during runtime.
To use Cognitive in your project, download and install Java 21+ JDK. The library depends on JavaFX 21+ To see the demo's code see Form demo
Gradle:
implementation 'org.carlfx:cognitive:1.5.0'Maven:
<dependency>
<groupId>org.carlfx</groupId>
<artifactId>cognitive</artifactId>
<version>1.5.0</version>
</dependency>A project using Java Modules (JPMS) will want to do the following in the consuming module:
requires org.carlfx.cognitive;
// open for FXML loaders
opens com.mycompany.myproject.controller to javafx.fxml, org.carlfx.cognitive;As you can see, the opens allow FXML and Controller code to inject view models and UI controls using reflection.
Software developers creating form based applications will inevitably stumble across the single most important UI architectural design pattern Model View Controller or MVC in short. This concept has paved the way for many frameworks which provide a good (acceptable) separation of concerns.
However, there are drawbacks to the MVC pattern (especially in JavaFX). One main drawback is that the controller layer can be difficult (if not impossible) to test. It is especially concerning when you are JavaFX developer who has worked with FXML and controller classes.
The pattern helps avoid coupling UI components, models (data) and presentation logic within a controller class. Because UI components are available during runtime it is difficult to test interactions (presentation logic) between the model and UI layers.
So, what is a solution?
You guessed it! The MVVM UI architecture pattern.
MVVM is an architectural pattern that isolates the business logic/back-end data(Presentation Logic) from the view (UI code). Its goal is to simplify user interface development. According to Wikipedia, the MVVM is a variation of Martin Fowler's perspective of the Presentation Model design pattern.
Next, let's see how to apply the MVVM UI pattern to an existing JavaFX Application
Before I show you how to convert a JavaFX MVC structure, let's compare the differences between MVC and the MVVM UI architecture patterns.
Typically MVC is used in Java Swing or JavaFX UI form type apps.
JavaFX is MVC-based, where developers often follow the Supervising Controller Pattern. An excerpt describing the controller's ability to manipulate the view with more complex view logic:
"Supervising Controller uses a controller both to handle input response but also to manipulate the view to handle more complex view logic. It leaves simple view behavior to the declarative system, intervening only when effects are needed that are beyond what can be achieved declaratively."
In the case of JavaFX, the declarative part would be FXML & CSS (XML representing the View).
JavaFX can also bind (Properties API) UI controls and listeners to synchronize the model data. While it is convenient to do this inside a controller(Presenter) class, the code is tightly coupled regarding presentation logic, (complex) view logic, and (possibly) business logic, making code difficult to maintain, debug, and test.
It is difficult to test especially when many UI controls are realized (dependency injected) during runtime, such as @FXML annotated UI controls inside controller classes.
Now, let's look at the MVVM pattern and how it differs.
The MVVM UI pattern is a variation of the Presentation Model Pattern. Both MVVM and Presentation Model pattern both achieve the separation of the View and the Model. An excerpt from Martin Fowler's section on When to use it?
"Presentation Model allows you to write logic completely independent of the views used for display. You also do not need to rely on the view to store state."
What's important is that the ViewModel manages the state. Later, we'll look at how to bind data between the View and ViewModel to synchronize model data.
The following is how MVVM is normally depected:
As you will notice, the model does not update the view layer, which he main difference between MVVM and MVC.
The main advantage is testing presentation logic separately from the UI form and its associated JavaFX Controller class.
Now that you've seen the pros and cons between MVC and MVVM how do we conceptually convert a JavaFX MVC UI form into the MVVM pattern?
Hint: Refactor (pull out) presentation logic and business logic away from JavaFX controllers into ViewModels or Model (services).
Below is a conceptual way to think of JavaFX using the MVVM UI pattern.
Cognitive is an un-opinionated library that let's you to refactor things at your own pace. As you get comfortable, you'll notice that JavaFX controller classes contain less code where presentation logic is move off to the ViewModels.
As shown above, you can treat the JavaFX FXML & Controller class as the View, and the Model will remain the same. The only difference is that the ViewModels will contain much of the state of the UI form and presentation logic. The objective is to make the view very stupid.
Now that you know conceptually, let's look at a code example of an MVC-style controller with a save operation.
Below is an example of how a UI form is about to save data.
/**
* User clicks on save button to save contact information.
* @param ae event
*/
@FXML
private void saveAction(ActionEvent ae) {
// copy user's input
String firstName = firstNameTextField.getText();
String lastName = lastNameTextField.getText();
// validate user's input
// if valid write to database and reset ui.
// db.write(new Person(firstName, lastName));
}Now, let's look at how to use a view model in a controller class.
Using view models, you can have presentation logic or business logic. When testing presentation logic, you can populate a view model with the correct values without modifying the UI. Remember, a view model does not contain any UI controls. Shown below is an example of using a view model.
@FXML
private void initialize() {
firstNameTextField.textProperty().bidirectionalBind(personViewModel.getProperty(FIRST_NAME));
lastNameTextField.textProperty().bidirectionalBind(personViewModel.getProperty(LAST_NAME));
}
@FXML
private void saveAction(ActionEvent ae) {
personViewModel.save(); // validates
if (personViewModel.hasErrorMsgs()) {
// apply messages to badges or decorate control for fields or global messages.
} else {
// view model get model values and has logic to persist data.
String firstName = personViewModel.getValue(FIRST_NAME);
String lastName = personViewModel.getValue(LAST_NAME);
// personViewModel.writePerson(new Person(firstName, lastName));
}
}Above you can see there are 4 steps to using View Models:
- Binding - Bind JavaFX controls and their properties to the view model's properties (property value layer).
- Validation - Upon
saveAction()method perform a view model'ssave()method (which calls thevalidate()method) - Error Messages - Check if there are any error messages if so, these can be applied to controls for user feedback.
- Model Values - Once you have valid values (model value layer) the code calls to view model's
.getValue()method to return raw values. NOTE: Think of a view model with two layers a Property Values and Model Values. ValidationViewModel`'s save Now that you see, much of the work uses view models instead of methods or UI code inside the controller class. The developer aims to remove state and presentation logic from the controller class.
Let's look at the two main implementations of the ViewModel interface SimpleViewModel and ValidationViewModel.
Let's start by creating a SimpleViewModel with one property with a String such as a first name. The objective is
To create a JavaFX text field and bind the value with a view model's property.
To bind properties do the following:
final String FIRST_NAME = "firstName";
// A text field
var firstNameTextField = new TextField();
// Create a
var personVm = new SimpleViewModel()
.addProperty(FIRST_NAME, "");
// Bidirectional bind of the first name property and text field's text property.
firstNameTextField.textProperty().bidirectional(personVm.getProperty(FIRST_NAME));
// Set view model property value.
personVm.setPropertyValue(FIRST_NAME, "Fred");
// Output Text field's text property
System.out.println("First name = " + firstNameTextField.getText());Output:
First name = Fred
As you can see whenever a user enters text into the text field (TextField) the view model's property (first name) gets populated and visa-versa.
Usually if you have a UI Form that has read-only or no validation needed a SimpleViewModel can be used. A form controls bound to properties on a view model you can call the reset() method to copy initial model values back into the property values, thus clearing the screen. The save() method
will copy the property values into the model values layer. For simple UIs you can validate fields manually.
Next, let's look at ValidationViewModel(s). These allow the developer to add validation to properties. The following example shows you how to create properties and add validators. These use cases are typically when a user is about to save information. Here they would need to validate before obtaining model values. New in version 1.3.0 are Enums as property names!
public enum PersonField {
FIRST_NAME("First Name"),
LAST_NAME("Last Name"),
AGE("Age"),
PHONE("Phone"),
HEIGHT("Height"),
COLORS("Colors"),
FOODS("Foods"),
THING("thing"),
MPG("Mpg"),
CUSTOM_PROP("Custom Prop");
public final String name;
PersonField(String name){
this.name = name;
}
}
var personVm = new ValidationViewModel()
.addProperty(FIRST_NAME, "")
.addValidator(FIRST_NAME, FIRST_NAME.name(), (ReadOnlyStringProperty prop, ViewModel vm) -> {
if (prop.isEmpty().get()) {
return new ValidationMessage(FIRST_NAME, MessageType.ERROR, "${%s} is required".formatted(FIRST_NAME));
}
return VALID;
})
// Adding multiple validation messages
.addValidator(FIRST_NAME, FIRST_NAME.name(), (ReadOnlyStringProperty prop, ValidationResult validationResult, ViewModel viewModel) -> {
if (prop.isEmpty().get() || prop.isNotEmpty().get() && prop.get().length() < 3) {
validationResult.error("${%s} must be greater than 3 characters.".formatted(FIRST_NAME));
}
String firstChar = String.valueOf(prop.get().charAt(0));
if (firstChar.equals(firstChar.toLowerCase())) {
validationResult.error("${%s} first character must be upper case.".formatted(FIRST_NAME));
}
})
.addProperty(PHONE, "111-1111111")
.addValidator(PHONE, PHONE.name(), (ReadOnlyStringProperty prop, ValidationResult validationResult, ViewModel vm) -> {
String ph = prop.get();
Pattern pattern = Pattern.compile("([0-9]{3}\\-[0-9]{3}\\-[0-9]{4})");
Matcher matcher = pattern.matcher(ph);
if (!matcher.matches()) {
validationResult.error("${%s} must be formatted XXX-XXX-XXXX. Entered as %s".formatted(PHONE, ph);
}
});
// validate view model
personVm.validate();
if (personVm.hasErrors()) {
for (ValidationMessage vMsg : personVm.getValidationMessages()) {
System.out.println("msg Type: %s errorcode: %s, msg: %s".formatted(vMsg.messageType(), vMsg.errorCode(), vMsg.interpolate(personVm)) );
}
}Output:
msg Type: ERROR errorcode: -1, msg: First Name is required
msg Type: ERROR errorcode: -1, msg: First Name must be greater than 3 characters.
msg Type: ERROR errorcode: -1, msg: Phone Number must be formatted XXX-XXX-XXXX. Entered as 111-1111111
Above you'll notice the first name field is required and must be more than 3 characters. The phone number is formatted incorrectly.
As each validation message contains a property of the field in question the code can create decorators or badges affixed on a UI control to allow the user to see the error or warning.
ValidationMessage vMsg = ...;
Label firstNameError = ...;
if (FIRST_NAME.equals(vMsg.propertyName())) {
firstNameError.setText(vMsg.message());
}Now let's fix the validation issues but instead of calling validate() you should call save(). A ValidatationViewModel overrides the SimpleViewModel's save() method.
The save() method essentially copies property values into the model value layer. Since a call to the validate() method happens before the save() method, property values will not be copied when errors occur.
personVm.setPropertyValue(FIRST_NAME, "Fred");
personVm.setPropertyValue(PHONE, "123-867-5309");
personVm.save();The correct thing to do is obtain the view model's model values by calling the following:
if (personVm.hasErrorMsgs()) {
return;
}
// Valid!
// Obtain valid values from the view model.
String validFirstName = personVm.getValue(FIRST_NAME); // You should not use personVm.getPropertyValue(FIRST_NAME);
// Write to database
db.write(...);You can think of the property values of a view model used for the form ui and the model values used on the backend.
When creating JavaFX controller classes you can add view models by using the annotation as follows:
// ... A controllers instance variables
@InjectViewModel
SimpleViewModel personViewModel;When you've created a FXML (view) and a controller you must use the FXMLMvvmLoader.make() facility.
Config config = ...;
JFXNode<Pane, PersonController> personJFXNode = FXMLMvvmLoader.make(config);
Pane personPane = personJFXNode.node();
PersonController personController = personJFXNode.controller();
// perform workHere's a demo UI form without values. As a user types into fields, the validator for populating the form will update the submit button state. If any fields are not populated, the save button will be disabled.
When pressing the submit button the validation behavior occurs afterwards. To see the demo's code see Form demo
Input in error (after save to validate)
When the submit is pressed show the overlay icons for each field with an error.
As you can see the user entered an initial character as an upper case 'F' only one error message alerts user that it must be 3 characters or more. With the new support of multiple error messages when using validator let show multiple messages related to the first name field.
Here are the following requirements or validation rules for First Name:
- Must not be blank
- Must be greater than 3 characters
- First character must be upper case
Let's enter one lowercase character into the First Name field and click on submit to evaluate error messages. Shown below is the new support for multiple validation messages using ConsumerValidators.
Above you will notice the first name field the user entered one lowercase 'f' character getting 2 validation messages.
To see how to add multiple validation messages shown below is a StringConsumerValidator for the first name field.
viewModel.addValidator(FIRST_NAME, "First Name", (ReadOnlyStringProperty prop, ValidationResult validationResult, ViewModel viewModel) -> {
if (prop.isEmpty().get() || prop.isNotEmpty().get() && prop.get().length() < 3) {
validationResult.error(FIRST_NAME, "${%s} must be greater than 3 characters.".formatted(FIRST_NAME));
}
String firstChar = String.valueOf(prop.get().charAt(0));
if (firstChar.equals(firstChar.toLowerCase())) {
validationResult.error(FIRST_NAME, "${%s} first character must be upper case.".formatted(FIRST_NAME));
}
});Now let's add correct data with valid input.
Here are new features to simplify code in certain scenarios.
- Updating the view model after JFXNode object is FXML loaded.
JFXNode'supdateViewModel()method. - Getting the view model after JFXNode object is FXML loaded.
JFXNode'sgetViewModel()method. - Running a code block when a property has changed.
ViewModel's.doOnChange()method. - Validate on change runs validators based on a property change.
ViewModel's - Determine if Form is invalid. The
ValidationViewModel'sonInvalid()method. - Determine if Form is valid.
ValidationViewModel'sonValid()method.
After calling the FXMLMvvmLoader.make() method a JFXNode object is returned representing the JavaFX Node and a Controller. Contained in the JFXNode (record) is a way to update the properties of a view model injected into the controller as shown in the code snippet below:
JFXNode<Pane, AccountCreateController> jfxNode = FXMLMvvmLoader.make(config);
// Modify a view model AFTER UI form was created and loaded.
jfxNode.updateViewModel("accountViewModel", (viewModel) ->
viewModel.setPropertyValue(EMAIL, "test123"));Above your notice the updateViewModel() method takes the variable name inside the controller and a lambda containing the view model to be modified.
After calling the FXMLMvvmLoader.make() method a JFXNode object is returned representing the JavaFX Node and a Controller. Contained in the JFXNode (record) is a way to get a view model previously injected into the controller as shown in the code snippet below:
JFXNode<Pane, AccountCreateController> jfxNode = FXMLMvvmLoader.make(config);
// Another way to modify a view model AFTER UI form was loaded.
Optional<AccountViewModel> accountViewModel = jfxNode.getViewModel("accountViewModel");Above your notice the getViewModel() method takes the variable name and returns an Optional instance.
Did you ever just want to run a code block when a property value has changed? Now you can with the following:
// fields change fire a validation
accountViewModel.doOnChange(()->{
accountViewModel.validate();
}, FIRST_NAME, LAST_NAME, EMAIL);Above you'll notice a lambda (Runnable) to be executed when the properties first name, last name and email property values change.
When a property value has changed its validators get run and any validation messages will be passed to help update the UI. Below is an example of decorating an icon overlay on the first name field to provide user feedback of the error.
// Does not decorate field initially. As user types validation occurs for field.
accountViewModel.validateOnChange(FIRST_NAME, (validationMessages) -> {
// clear decoration UI code.
firstNameTooltip.setText("");
firstNameErrorOverlay.setVisible(!validationMessages.isEmpty());
// process each message owned by Field
validationMessages.forEach(validationMessage -> {
// show overlay and update tooltip
accountViewModel.updateErrors(validationMessage);
String message = validationMessage.interpolate(accountViewModel);
// concatenate. Update UI
firstNameTooltip.setText(firstNameTooltip.getText() + message + "\n");
});
});Above you'll notice it clears the tooltip and error overlay, then it concatenates the error messages to be shown to the user.
The invalid property detects (true) when there are validation messages otherwise it is false. This is often used to validate the whole form and disabling or enabling a save button as shown below.
// button disable property is bound to invalid property.
submitButton.disableProperty().bind(accountViewModel.invalidProperty());Above you'll notice a JavaFX Button's disable property is bound to the invalid property. Also, this gets set based on the following code:
// fields change fire a validation
accountViewModel.doOnChange(()-> {
accountViewModel.validate();
}, FIRST_NAME, LAST_NAME, EMAIL);When validate is run, the error messages are collected (greater than zero) the invalid property gets set to true.
After a validation view model's validate() or save() method is called you can check if there are zero validation messages or not as shown below.
// validate form
accountViewModel.validate();
// is valid
if (accountViewModel.validProperty().get()) {
// success!!!
}The following are links on the topic of UI/UX and Patterns:
- GUI Architectural Patterns by Martin Fowler - Model View Controller, Model-View-Presenter
- Flow Synchronization Pattern - How to synch data between UI form and domain objects.
- Separated Presentation - Separating presentation and business logic code in separate layers.
- JavaFX Forms Framework
