1.2 Flow of plugin development
The following figure shows an overview and flow of plugin development.
|
The numbers in the figure correspond to the following numbers:
-
A developer develops a plugin in a development environment.
Eclipse, which is provided by Navigation Platform, is used for plugin development.
To use Eclipse, setup is required in advance.
-
The developer sends the developed plugin to the editing environment and execution environment.
The system administrator applies the plugin to the editing environment and execution environment.
-
After plugins are applied, the Content Manager or Content Editor creates Operational Content in the editing environment.
-
For I/O Plugins, the Content Manager or Content Editor associates the plugins with Operational Content by drawing mapping lines between Plugin Parts and Guide Parts.
For Suspend/Resume Plugins and Custom Window Plugins, association is not necessary.
- Reference note
-
If the system configuration does not use an editing environment, a developer might also perform the tasks in 3 and 4 in a development environment. For details about system configurations, see the Hitachi Navigation Platform Setup and Operations Guide. For details about how to create Operational Content, see the Hitachi Navigation Platform Content Editing Guide.
The following provides details about plugin development tasks and includes references.
- Before starting development
-
You must construct a development environment before starting the tasks described here. Note that you must have Windows administrator roles to perform any task described here.
- Upon completion of the development
-
After you have completed development of plugins, send J2EE applications (plugin-name.ear) to an editing environment and execution environment. In the case of developed I/O Plugins, export Operational Content associated with the plugins, and then import them to the editing environment and execution environment.
For details about each task, see the Hitachi Navigation Platform Setup and Operations Guide.
Order |
Task |
I/O Plugin |
Suspend/Resume Plugin |
Custom Window Plugin |
See: |
---|---|---|---|---|---|
1 |
Preparing a development environment (by setting up Eclipse and adding libraries) |
R |
R |
R |
|
2 |
Creating template plugins |
R |
R |
R |
|
3 |
Importing a template plugin project to Eclipse |
R |
R |
R |
|
4 |
Customizing (editing) the template plugin by using Eclipse |
R |
R |
R |
|
5 |
Adding (and implementing) necessary processing to the plugin |
S |
S |
S |
|
6 |
Building a customized template plugin project by using Ant |
R |
R |
R |
|
7 |
Deploying the plugin J2EE application (plugin-name.ear) by using Ant |
R |
R |
R |
|
8 |
Placing Plugin Parts in the Guide area and then associating plugins with Operational Content by drawing mapping lines to connect Plugin Parts and Guide Parts |
R |
N |
N |
|
9 |
Checking the user property file |
R |
R |
S |
|
10 |
Debugging plugins by using the Eclipse debugger function |
R |
R |
R |
- Legend:
-
R: The task is required.
N: The task is not required
S: Perform the task if necessary.
- Note:
-
You can change J2EE server setting items if necessary. For details, see 4.13 Changing J2EE server settings.