A more modern style API for the Java Swing UI framework, focused on ease of use.
Let's be honest, coding for Swing is not easy. And JTable is probably the epiphany; you have to understand TableModel, manually add sorting, filtering, the events that trigger updates, etc. What if the Swing API would be revisited and made modern, so that using that JTable becomes simple. What if creating a table with sorting, filtering, automatic updates of cells when values change only took a few lines of code?
var sTable = new STable<City>()
.columns(City.class, "name", "distance", "roundtrip")
.items(cities); // cities is a List<City>, and City is a Java Bean with PropertyChangeEventsOr creating a strongly typed text field that is bound to the property of a Java bean would be as simple as:
var sTextField = STextField.ofString().value$().bindTo(city.name$());
// Or a bit compact; value is STextField's default bind property
var sTextField = STextField.ofString().bindTo(city.name$());
// Or even more compact
var sTextField = STextField.ofBindTo(city.name$());Well, you've come to the right place. Take a look at the examples here, and the JavaDoc present in org.tbee.sway, and see if they are easy enough to use. A UI library probably is never truly finished, but Sway is stable and used in production, but also probably not bug free.
// A label can have its text and icon property bound
var sLabel = new Slabel();
sLabel.text$().bindTo(city.name$());
// SCheckBox can be bound to a boolean property
var sCheckBox = SCheckBox.of("Growing").bindTo(city.growing$());
// SCheckBox3 can be bound to a Boolean property, supporting 3 states: TRUE, FALSE, NULL
var sCheckBox = SCheckBox3.of("Cityrights").bindTo(city.cityrights$());
// Add a list
var sList = new SList<City>()
.render(new CityFormat())
.selectionMode(SList.SelectionMode.MULTIPLE)
.items(cities); // cities is a List<City>
// Bind the selection of the list to that of the table created above
sList.selection$().bindTo(sTable.selection$());
// A tree is nothing more than a root and a way to get the children of a node.
var sTree = STree.of(amsterdam)
.render(new CityFormat())
.childrenOf(City::getPartnerCities);
// A tree often shows different classes as nodes, so several children mappings are needed.
// The Formats registered in the FormatRegistry are used for rendering automatically.
var sTree = STree.of(cities) // a list as root is automatically handled
.childrenOf(City.class, City::getStreets)
.childrenOf(Street.class, Street::getBuildings);
// SButtonGroup revolves around the associated value, not the button
var sButtonGroup = SButtonGroup.<Integer>of()
.add(1, new SToggleButton("winner"))
.add(2, new SToggleButton("2nd"))
.add(3, new SToggleButton("3rd"))
.bindTo(race.position$());
var sPanel = SFlowPanel.of(sButtonGroup.getButtons());
// SButtonGroup has some practical convenience methods
var sButtonGroupCities = SButtonGroup.ofRadioButtons(amsterdam, berlin, rome);
var sPanelCities = SFlowPanel.of(sButtonGroupCities.getButtons());
// STabbedPane supports loading-on-demand, synchronous and asynchronous, when the visible tab changes.
// STabbedPane can be bound, so when a tab needs loading, it gets this value to start from.
// For example: an STabbedPane bound to a city can load the details or crime numbers when the corresponding tab becomes visible.
STabbedPane<City> sTabbedPane = STabbedPane.of()
.bindTo(data.city$())
.tab("details", STextField.ofString() // synchronous: only value-to-component function provided
, (city, sTextField) -> sTextField.setValue(city.name()))
.tab("crime", new CrimeNumbersPanel() // asynchronous: value-to-value2 function, on-success value2-to-component function, and on-failure provided
, city -> crimeApi.fetchNumbersFor(city.code()) // In a worker thread derived data is fetched
, (crimeNumbers, crimeNumbersPanel) -> crimeNumbersPanel.setNumbers(crimeNumbers) // The derrived data is displayed
, (throwable, crimeNumbersPanel) -> ... // Or something went wrong
);
// Explicit panels for layouts, with corresponding methods.
var sBorderPanel = SBorderPanel.of(new STable())
.west(new SomeNavigationMenu())
.east(new SomeContextLinks());
// Any component can have an overlay of any component, but there are a few practical ones
sBorderPanel.overlayWith(new SLoadingOverlay());
// MigLayout is used by Sway internally anyhow, so the user can use this great layout as well.
var migPanel = MigPanel.of().fill();
migPanel.addLabelAndField(someLabel, someField).growX();
migPanel.wrap();
// Construct menus without those pesky in-between variables
SMenuBar.of(jFrame)
.add(SMenu.of("menu1")
.add(SMenuItem.of("menuitem 1a", this::menu1aHandler))
.add(SMenuItem.of("menuitem 1b", this::menu1bHandler))
)
.add(SMenu.of("menu2")
.add(SMenuItem.of("menuitem 2a", this::menu2aHandler))
.add(SMenuItem.of("menuitem 2b", this::menu2bHandler))
.add(SMenuItem.of("menuitem 2c", this::menu2cHandler))
); In order to not have to repeat the same formatting over and over again, Sway has a FormatRegistry.
A simple example:
// Only two methods need to be implemented, the rest are optional
public class LongFormat implements Format<Long> {
@Override
public String toString(Long value) {
return value == null ? "" : value.toString();
}
@Override
public Long toValue(String string) {
return string.isBlank() ? null : Long.parseLong(string);
}
}
// Register the format once to use it in many components
FormatRegistry.register(Long.class, new LongFormat()); // Formats must be stateless and thread safe. The FormatRegistry is used by all components, STextField, STable, STree, SButtonGroup, ..., so it is only necessary to register a format once. This also is true for domain entities, like for example a "City" or "Employee".
Format also allows to define things like horizontal alignment and icon.
Actions can be registered and will be shown in the (right mouse button) context menu. These can be simple actions, like the default available "copy", "cut" and "paste", but also business model related actions.
ActionRegistry.register(new ShowOnMapForCityTextFields());
SContextMenu.install();
public class ShowOnMapForCityTextFields implements Action {
@Override
public String label() {
return "Show on map";
}
@Override
public boolean isApplicableFor(Component component, Map<String, Object> context) {
return component instanceof STextField sTextField
&& sTextField.getFormat() instanceof CityFormat;
}
@Override
public void apply(Component component, Map<String, Object> context) {
STextField<City> sTextField = (STextField<City>)component;
City city = sTextField.getValue();
... // show city on map
}
}Sway includes a bean generator. This means you can have a class with only data (instance variables) and using some annotations all the methods are generated.
// This will generate a class "City extends CityData"
// With a "name" property (setName, getName, name$(), etc).
// And a "sisterCities" property (addSisterCity, removeSisterCity, sisterCities$(), etc).
@Bean(stripSuffix = "Data")
abstract public class CityData extends AbstractBean<City> {
@Property
String name;
@Property(nameSingular="sisterCity", isList = true)
List<City> sisterCities;
}The data class needs to extend AbstractBean in order to provide the expected property change methods. Or you will need to add them manually.
Things become interesting when custom logic needs to be added. It is very likely the custom code needs to call a setter in order to send the appropriated events for binding. For this the bean generator supports a dual and triple stack approach.
The triple stack is the most straight forward approach, with three classes, where the middle one contains the generated code.
// Contains the data
@Bean(stripSuffix = "Data", appendSuffixToBean = "Bean")
abstract public class TripleStackData extends AbstractBean<TripleStack> {
@Property
String name;
}
// Contains the generated code
public class TripleStackBean extends TripleStackData {
public String getName() {...}
public void setName(String name) {...}
public TripleStack name(String v) {...}
}
// Contains the custom code
public class TripleStack extends TripleStackBean {
public void custom() {
setName("custom");
}
}The triple stack approach spreads the maintained code over two classes, ideally one would want to have data and custom code in one class. This is where the double stack comes in. It uses a small trick to be able to access the generated methods from the data class, using a "self" variable.
// Contains both data and custom code
@Bean(stripSuffix = "Data")
abstract public class DoubleStackData extends AbstractBean<DoubleStack> {
@Property
String name;
private final DoubleStack self = (DoubleStack)this;
public void custom() {
self.setName("custom");
}
public DoubleStackData() {
// Sway's AbstractBean has a convenient type safe listener method
this.<String>addVetoableChangeListener("name", (oldValue, newValue) -> {
if ("notAllowed".equals(newValue)) {
throw new IllegalArgumentException("Name is not allowed");
}
});
}
}
// Contains the generated code
public class DoubleStack extends DoubleStackData {
public String getName() {...}
public void setName(String name) {...}
public DoubleStack name(String v) {...}
}The double stack does not allow for, for example, a setter be overwritten to validate the input value. You have to use the vetoable change property logic to do validation instead. Decide what you prefer.
The bean generator uses compiler annotations, so it will automatically be picked up by a build tool like Maven. IDEs usually need to have compiler annotations activated.
Sway includes what is considered the most popular Look-and-Feels for Java, which at the moment is FlatLAF.
SLookAndFeel.installDefault();These popular LAFs are known to change over time, so in the future FlatLAF may become deprecated and be replaced.
Sway uses the standard Swing components, only with an opinionated API, so they should blend-in nicely in existing applications.
But Sway is highly opinionated, trying to make standard stuff as easy as possible. Sway assumes some kind of domain model, which is implemented according to the Java Bean specification, including PropertyChangeEvents if you want to do binding. And as long as you stick to these assumptions, things should go smoothly. If you want to do things differently than Sway envisions, it's better use the Swing components; they are much more flexible (and because of that more difficult to use).
As long as you stick to Sway's API, upgrading should not be too much of a hassle. If you start poking around, you're on your own ;-)
There is no formal support for Sway: this library is an open source hobby project and no claims can be made. Asking for help is always an option. But so is participating, creating pull requests, and other ways of contributing.
Just include a dependency in your project. For the latest version see Maven central
<dependency>
<groupId>org.tbee.sway</groupId>
<artifactId>sway</artifactId>
<version>1.3.0</version>
</dependency>- Binding uses Karsten Lentzsch's JGoodies underneath (https://www.jgoodies.com/freeware/libraries/binding/).
- STable's filter header is provided by Coderazzi (https://coderazzi.net/tablefilter/).
- STable's navigation bar is based on CoMedia's implementation (project is no longer available online).
- Mikael Grev's excellent MigLayout is used for several layouts (https://www.miglayout.com/).
- FlatLAF is a modern high quality Look and Feel (https://www.formdev.com/flatlaf/).
- Ikonli (https://kordamp.org/ikonli/) to use the standard included Material (https://kordamp.org/ikonli/cheat-sheet-material2.html) and Material Design 2 icon set (https://kordamp.org/ikonli/cheat-sheet-materialdesign2.html)