Plugins allow to add functionalities to a Client, Server, or Editor. For example:
- Allow to save and load runtime Buffers in the Client or the Server
- Allow to execute Scripts in the Editor
- Allow to Edit an UACDS Interface in the Editor
Plugins will depend on the Client, Server, or Editor, but the Client, Server, and Editor do not depend on any Plugin. Note that contrary to Extensions
, Plugins do not allow to extend the ARINC 661
Plugins should be by default in the
application directory (relative to the Client, Server or Editor). Note that (as previously stated), the J661 modules do not depend on any Plugin. The discovery and connection of the available Plugins are performed at runtime when starting the application.
It is possible to specify alternate directories where to find the Plugins by using the
−pluginsDir:<directory 1; directory 2;...>
to force the locations of directories for the Plugins.
Default provided Plugins
The following Plugins are provided by default by the J661 Project:
Developing a Plugin
See also Developing a plugin
Copyright 2016 Dassault Aviation. All Rights Reserved. Documentation and source under the GPL v2 licence