1.411 released
Support hot enabling and disabling of Plugins
Support hot enabling and disabling of Plugins
Support hot enabling and disabling of Plugins
Support hot enabling and disabling of Plugins
Support hot enabling and disabling of Plugins
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names Add the initConfiguration(Prefefences, short) and initConfiguration(Prefefences) as interface method with a default empty implementation in the MDIApplication interface Add the serializeConfiguration() method in the MDIApplication interface with a default implementation Add the serializeConfiguration() method implementation in the AbstractJFXApplication Support hot enabling and disabling of Plugins
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names
Fix the updated Plugins map not using the Plugins names
1.410 released
release 1.4.10
release 1.4.10
Allow to execute the StreamGobbler listener in another thread than the one where the stream is read, avoiding missing discarding inputs if a lot of input are read quickly
Allow to execute the StreamGobbler listener in another thread than the one where the stream is read, avoiding missing discarding inputs if a lot of input are read quickly
Allow to execute the StreamGobbler listener in another thread than the one where the stream is read, avoiding missing discarding inputs if a lot of input are read quickly
Fix some cases where the DefaultMessageArea would emit an exception when adding text Ensure that the adding of text on the DefaultMessageArea is always performed on the swing event thread Add a setTimedMessage(String, int) method on the StatusBar
update libs in samples
1.4.9 released
update wiki
update samples
update wiki
update wiki
Add a capability to have a message area per each tab
Add a capability to have a message area per each tab
Add a framework to manage the localization of the menus
Use docJGenerator 1.6.15 Add a setCloseable method in the FileProperties to specify if the associated tab can be closed Add a new closeOtherTabs(boolean) method which will use the forceClose argument Add a new getDefaultForceCloseTab() method in the TabbdApplication class to specify the default behavior of the close methods Add an option to be able to save the content of the message area as a text file Add a DefaultProgressInterface class to be able to have a status bar without a Splash screen Add...
update wiki
update wiki
Use docJGenerator 1.6.15 Add a setCloseable method in the FileProperties to specify if the associated tab can be closed Add a new closeOtherTabs(boolean) method which will use the forceClose argument Add a new getDefaultForceCloseTab() method in the TabbdApplication class to specify the default behavior of the close methods Add an option to be able to save the content of the message area as a text file Add a DefaultProgressInterface class to be able to have a status bar without a Splash screen Add...
- Define two types of application, allowing to better configure the use of the framework:
update source
update source
update wiki
Put the README and the CHANGES files in markdown
licence
Use docJGenerator 1.6.15
Use docJGenerator 1.6.15
replace readme by markdown
replace readme by markdown
replace readme by markdown
Add a setCloseable method in the FileProperties to specify if the associated tab can be closed
Add a setCloseable method in the FileProperties to specify if the associated tab can be closed
Use docJGenerator 1.6.13
Use docJGenerator 1.6.13 Add a setCloseable method in the FileProperties to specify if the associated tab can be closed
1.4.8 released
Use jDependency 1.4.8 for the Unit Tests
Use jDependency 1.4.8 for the Unit Tests
Use jDependency 1.4.8 for the Unit Tests
Use docJGenerator 1.6.11.1
Use docJGenerator 1.6.11.1
Use docJGenerator 1.6.11.1 Use jDependency 1.4.8 for the Unit Tests Fix a potential NPE in the applyCommandLineArguments() method Make sure that the handlers list in the DefaultMessageArea is never null Fix some cases when the click listeners in the DefaultMessageArea would not be correctly setup, which would lead to the listeners not being fired when a click event would occur
- Make sure that the handlers list in the DefaultMessageArea is never null
- Make sure that the handlers list in the DefaultMessageArea is never null
- Make sure that the handlers list in the DefaultMessageArea is never null
- Make sure that the handlers list in the DefaultMessageArea is never null
Fix a potential NPE in the applyCommandLineArguments() method Make sure that the handlers list in the DefaultMessageArea is never null Fix some cases when the click listeners in the DefaultMessageArea would not be correctly setup, which would lead to the listeners not being fired when a click event would occur
Fix a potential NPE in the applyCommandLineArguments() method
Fix a potential NPE in the applyCommandLineArguments() method
1.4.7 released
1.4.7 update
1.4.7 update
1.4.7 update
Fix the samples project not containing the flatlaf-3.2.1 jar file
Fix the samples project not containing the flatlaf-3.2.1 jar file
- Allow to prevent the opening of the application with specific arguments groups in the command-line framework