Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • By default all Plugins that are deployed with this folder are available with the XML Editor. Therefore the Xml2Ini Converter is active by default.
  • Should the sub-folder plugins not be available, e.g. should this folder have been renamed, then you cannot use the conversion feature. 
  • If the Xml2Ini Converter is available then you can use the respective operation from the main menu and from the tab context menu.
    • The XML Editor shows a file dialog and suggests an .ini export file with the same basename as the current .xml configuration file.

Configuring the XML Editor for automated

...

Conversion

The XML Editor comes with the feature to auto-save configuration files in the .ini format when saving to the .xml format, i.e. doing the conversion automatically.

  • To activate this feature adjust the check-box "Autosave ini file" to be checked. We recommend to use this feature if you want to create compatible .xml and .ini configuration files for JADE releases 1.10 and 1.11. 
    • This allows to manage configurations for JADE 1.11 in XML format and to have a parallel .ini file being created for use with JADE 1.10. Keeping both .xml and .ini configuration files in sync will allow a smooth migration to JADE 1.11 - as long as you would not manually modify the .ini file.
    • In autosave mode the .ini file will be overwritten whenever the .xml file is saved.
  • In addition you can enable desktop notifications to be created if a .ini file is being saved.

 

Assigning the JADE XSD Schema

When creating a new XML configuration file then the following dialog appears for schema assignment:

Image Added

For JADE configuration files please assign the XSD Schema that matches your JADE release:

Examples

...