Release Notes: Fixes the Synth2 Look and Feel not taking into account the screenDensity graphic property for the fonts set for buttons, comboBox, etc. Addes synth2 to LookModel conversion in the LookModel plugin. Fixes the DataScaling widgets not taking into account a modification of the TargetParameterID property in the Editor. Protects the decoding of buffers received by the Server against cases where some of the blocks have a 0 size. Adds a new property for the UDP protocol, which allows you to define more than one port for the output (meaning that several remote clients/servers will receive the buffers).
Release Notes: This version support both Swing and JavaFX rendering engines, and has a lot of additions compared to the 0.57 previous version.
Release Notes: Supports plugins in the JavaFX graphic framework. Allows you to generate an ARINC 661-kind docx document with a widgets definition in the Widget definition plugin. Improves the performance of MapItem renderer creation by up to a factor of 100 in JavaFX. Validates the widgets XML definition against a Schema rather than a DTD. Fixes many bugs in the JavaFX widgets implementation. Allows you to create gestures libraries (such as custom multitouch gestures) and behavior libraries (such as animations libraries) in JavaFX and Swing.
Release Notes: The additional Plugin Types not correctly handled by the Plugins Manager have been fixed.
Release Notes: This is a maintenance version for the Java 6 branch of the J661 project. It fixes the list of extensions not saved when saving the configuration in the Editor. There are several enhancements to the editor scripting plugin. Fixes the case where the change of a StyleSet for a widget in the server or the editor, which lead to a change of UI implementation for the widget, would not be taken into account.
Release Notes: Fixes the JavaFX implementation for several widgets. Supports ARINC 661 extensions in Swing and JavaFX. Fixes several Editor bugs in JavaFX. Removes the necessity to specify a specific jar file for MapItems implementations; the associated jar file is now considered as a regular extension.