Plugins dependencies

The MDIPluginType manifest property for a Plugin specifies for which kind of application the Plugin is available:

• "common" for a Plugin which can be used for the Client, the Server, or the Editor^[1]
  For example, the Scenario Plugin can be used in the Client, the Server, or the Editor in the context of the Embedded Server
• "server" for a Plugin which can be used only for the Server
• "client" for a Plugin which can be used only for the Client
• "editor" for a Plugin which can be used only for the Editor^[2]
  For example, the UACDS Plugin or the EditorScript Plugin can be used only for the Editor

Furthermore, Plugins can have inter-plugins dependencies^[3]

For example, the UACDS Plugin depends on the EditorScript Plugin

. The following diagram shows on which kind of application a Plugin is available, and the inter-plugins dependencies:

Plugins which can be used for the Client, Server, or Editor

• Scenario Plugin

Plugins which can be used for the Editor

• UACDS Plugin. Depends on the EditorScript Plugin
• EditorScript Plugin
• Look Model Plugin. Depends on the EditorScript Plugin
• Cockpit Plugin

Plugins which can be used for the Server

Note that Plugins which can be used in the Server can also be used in the Editor because the Editor integrates an Embedded Server.

• Image Generation Plugin

Plugins which can be used for the Client

Note that Plugins which can be used in the Client can also be used in the Editor because the Editor integrates an Embedded Server.

• MapClient Plugin
• Script Plugin
• Embedded Client Plugin. Depends on the Script Plugin