PreferencesFX - 轻松创建用于应用程序设置/首选项的UI的框架

网友投稿 835 2022-10-11

PreferencesFX - 轻松创建用于应用程序设置/首选项的UI的框架

PreferencesFX - 轻松创建用于应用程序设置/首选项的UI的框架

PreferencesFX

Preference dialogs for business applications made easy. Creating preference dialogs in java has never been this easy!

Table of Contents

MavenGradleWhat is PreferencesFXAdvantagesMain FeaturesDocumentationStructureDemosDefining a preferences dialogRequired argumentsOptional argumentsSetting types LocalisationValidationTeam

Maven

To use this framework as part of your Maven build simply add the following dependency to your pom.xml file:

Java 8

com.dlsc.preferencesfx preferencesfx-core 8.6.0

Java 11

com.dlsc.preferencesfx preferencesfx-core 11.6.0

Gradle

To use this framework as part of your gradle build simply add the following to your build.gradle file and use the following dependency definition:

Java 8

dependencies { compile group: 'com.dlsc.preferencesfx', name: 'preferencesfx-core', version: '8.6.0'}

Java 11

dependencies { compile group: 'com.dlsc.preferencesfx', name: 'preferencesfx-core', version: '11.6.0'}

What is PreferencesFX?

Creating preference dialogs in JavaFX is a tedious and very error-prone task. PreferencesFX is a framework which solves this problem. It enables the developer to create preference dialogs with ease and creates well-designed and user-friendly preference dialogs by default.

Advantages

Less error-proneLess code neededEasy to learnEasy to understandEasy to use, for developers and users alike

Main Features

Simple and understandable APIThe most important features are noted in the picture and the corresponding table below:

Nr.FeatureDescription
1Search / FilterFilters all categories for a given String. Enables searching for a Setting, Group or Category by name.
2TreeViewShows all categories in a hierarchical structure
3Breadcrumb BarShows the user the previous categories in the hierarchy to the currently displayed category and allows the user to navigate back.
4Undo / Redo ButtonsAllows the user a stepwise undo and redo possibility of his last changes.
5Various pre-defined setting typese.g. Integer, Double, Boolean, String, Lists, Objects
6close/cancel buttonsThe close button just closes the window and leaves the preferences as they are. The cancel button discards all changes which are made during the time the dialog was last opened.

| Instant persistance | Any changes to the application are saved instantly.

Documentation

This project uses the asciidoctor plugin to generate the necessary documentation. Run the following maven task:

process-resources

Afterwards, you will find the documentation in the target/generated-docs/ subdirectory.

Structure

A preferences dialog can contain multiple Categories. Each Category contains one to multiple Groups Each Group contains one to multiple Settings

For better illustration, the basic concept of writing a preferences dialog is shown below:

PreferencesFx preferencesFx = PreferencesFx.of(SaveClass.class, Category.of("Category Title", Group.of("Group Title", Setting.of("Setting Title", new Property()) ) ) );

Notes:

It is also possible to omit the Group and declare all settings in a Category directly. However, in this case all settings will simply be displayed one after another without grouping. If you want more control, use Group.A Group can also be defined without a title. In this case, the individual groups are displayed with more space in between them, to ensure they can be differentiated.A Category can also take a graphic node to be used as an icon as the second argument, e.g. Category.of("Category Title", new ImageView(new Image("file:icon.png")),

Demos

We created several demos to visualize the capabilities of PreferencesFX. Simply launch preferencesfx-demo/src/com/dlsc/preferencesfx/AppStarter.java and look into the different Tabs.

The following demos are available:

ImportDescription
StandardThe standard demo with a few settings and fully working bindings.
InternationalizedShows how to define preference dialogs in multiple languages, using internationalization.
OneCategoryShows the behavior of the API when only one category is used: The Breadcrumb Bar and TreeView will be omitted from the GUI.
ExtendedA demo, populated with lots of categories, groups and settings without any bindings. Designed to show usage in a big project.

Defining a preferences dialog

Creating a preferences dialog is as simple as calling PreferencesFx.of().

StringProperty stringProperty = new SimpleStringProperty("String");BooleanProperty booleanProperty = new SimpleBooleanProperty(true);IntegerProperty integerProperty = new SimpleIntegerProperty(12);DoubleProperty doubleProperty = new SimpleDoubleProperty(6.5);PreferencesFx preferencesFx = PreferencesFx.of(AppStarter.class, // Save class (will be used to reference saved values of Settings to) Category.of("Category title 1", Setting.of("Setting title 1", stringProperty), // creates a group automatically Setting.of("Setting title 2", booleanProperty) // which contains both settings ), Category.of("Category title 2") .expand() // Expand the parent category in the tree-view .subCategories( // adds a subcategory to "Category title 2" Category.of("Category title 3", Group.of("Group title 1", Setting.of("Setting title 3", integerProperty) ), Group.of( // group without title Setting.of("Setting title 3", doubleProperty) ) ) ) );

This code snippet results in the following preferences window, containing three categories:

To create a Setting, you only need to define a title and a Property. PreferencesFX does the rest. You can then integrate this Property in your application. Changes of values in the preferences dialog will be persisted instantly, however it's up to you to decide whether you want to persist them instantly in your application as well.

Required arguments

You have a lot of options to influence the behavior and layout of the preferences dialog. The following parameters are the absolute minimum, needed for the proper functioning of PreferencesFX:

ParameterDescription
AppStarter.classIn the constructor of PreferencesFx a saveClass is required. This class is saved as a key for the saved setting values. Further information is available in the javadoc.
Category descriptionEach Category must have a description. This is required to display its description in the TreeView.
Setting descriptionEach Setting must have a description. It will be displayed on the left of the control, which is used to manipulate the respective Setting.

Note: The value of the each Setting is stored using the Java Preferences API by default. For testing purposes, to clear the saved preferences of the demo, run the method in the class:

preferencesfx-demo/src/test/java/PreferencesStorageReset.java

Optional arguments

The following parameters are optionally available to further configure the dialog created by PreferencesFX:

MethodClassDescription
.subCategoriesCategorySubcategories allow a Category to have additional subcategories as children. Those are also displayed in the tree.
.expandCategoryAllows to specify if the Category should be expanded in the Tree-View by default.
.descriptionGroupIf you decide not to add the description of a group in the constructor, you can still add it after the creation of the group.
.validateSettingAllows to add a Validator to a setting, to set constraints to the values that can be entered.
.persistApplicationStatePreferencesFxDefines if the Preferences API should save the application states. This includes the state persistence of the dialog window, as well as the values of each Setting.
.persistWindowStatePreferencesFxDefines whether the state of the dialog window (position, size, last selected Category) should be persisted or not. Defaults to false.
.saveSettingsPreferencesFxDefines whether the changed settings in the Preferences window should be saved or not. Defaults to true.
.debugHistoryModePreferencesFxMakes it possible to enable or disable the keycombination to open a debug view of the list of all actions in the history (undo / redo). Pressing Ctrl + Shift + H (Windows) or CMD + Shift + H (Mac) opens a dialog with the undo / redo history, shown in a table. Defaults to false.
.buttonsVisibilityPreferencesFxSets the visibility of the cancel and close buttons in the PreferencesFxDialog. Defaults to true.
.instantPersistentPreferencesFxIf set to true, it will instantly apply any changes that are being made in the PreferencesFxDialog. If set to false, it will only apply changes when the Save / Apply / OK button is pressed. Due to a limitation in FormsFX, undo / redo cannot be used with instant persistence switched off! Defaults to true.
.i18nPreferencesFxSets the translation service of the preferences dialog for internationalization.
.dialogTitlePreferencesFxAllows to specify a custom dialog title.
.dialogIconPreferencesFxAllows to specify a custom dialog icon.

Setting types

The following table shows how to create Settings using the predefined controls and how they look like:

Note: By default, PreferencesFX saves the settings under a key which consists of the breadcrumb to the setting, delimited by # signs. If you want to define your own key to be used for saving, use the method setting.customKey("key")

Localisation

All displayed strings can be internationalized. You can use resource bundles to define different locales and use the key instead of the descriptions. Adding i18n support is simply done by calling the method .i18n() at the end when creating the preferences:

private ResourceBundle rbDE = ResourceBundle.getBundle("demo.demo-locale", new Locale("de", "CH"));private ResourceBundle rbEN = ResourceBundle.getBundle("demo.demo-locale", new Locale("en", "UK"));private ResourceBundleService rbs = new ResourceBundleService(rbEN);PreferencesFx.of(…) .i18n(rbs);

Validation

It is possible to optionally add a Validator to settings. PreferencesFX uses the implementation of FormsFX for the validation. FormsFX offers a wide range of pre-defined validators, but also includes support for custom validators using the CustomValidator.forPredicate() method. The following table lists the supported validators:

ValidatorDescription
CustomValidatorDefines a predicate that returns whether the field is valid or not.
DoubleRangeValidatorDefines a number range which is considered valid. This range can be limited in either one direction or in both directions.
IntegerRangeValidatorDefines a number range which is considered valid. This range can be limited in either one direction or in both directions.
RegexValidatorValiates text against a regular expression. This validator offers pre-defined expressions for common use cases, such as email addresses.
SelectionLengthValidatorDefines a length interval which is considered valid. This range can be limited in either one direction or in both directions.
StringLengthValidatorDefines a length interval which is considered valid. This range can be limited in either one direction or in both directions.

Team

Marco Sanfratellomarco.sanfratello@students.fhnw.chSkype: sanfratello.m@gmail.comGitHub: Genron François Martinfrancois.martin@students.fhnw.chSkype: francoisamimartinGitHub: martinfrancois Dirk Lemmermanndlemmermann@gmail.comSkype: dlemmermannGitHub: dlemmermann Dieter Holzdieter.holz@fhnw.chSkype: dieter.holz.canoo.comGitHub: DieterHolz

License

版权声明:本文内容由网络用户投稿,版权归原作者所有,本站不拥有其著作权,亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容,请联系我们jiasou666@gmail.com 处理,核实后本网站将在24小时内删除侵权内容。

上一篇:搭建的vscode 服务使用nginx代理后不能访问
下一篇:odoo7 rpc 使用,openerp7
相关文章

 发表评论

暂时没有评论,来抢沙发吧~