Difference: DpHipePluginsDeveloperManual (13 vs. 14)

Revision 142011-03-09 - PaulBalm

Line: 1 to 1
 
META TOPICPARENT name="DpHipePlugins"

Plug-in Developer Manual

Line: 196 to 196
 

The plug-in installation process

Changed:
<
<
The standard plug-in installation process just decompresses the plug-in into the plug-in directory and "starts" the plug-in. The plug-in directory is $HOME/.hcss/apps/hipe/plugins/[name]/[version]. You can view this directory by opening the plug-ins panel in HIPE (select Plug-ins from the Tools menu). Select the plug-in and click Browse.
>
>
The standard plug-in installation process just decompresses the plug-in into the plug-in directory and "starts" the plug-in. The plug-in directory is $HOME/.hcss/apps/hipe/plugins/[name]/[version]. You can view this directory by opening the plug-ins panel in HIPE (select Plug-ins from the Tools menu). Click the plug-in and select "Browse plug-in" from the View menu in the plug-ins panel.
  Starting the plug-in means:
Changed:
<
<
  • add all JARs to the Java classpath and the Jython system path
>
>
  • add all JARs to the Java and Jython class-loader(s)
 
  • load the custom properties
  • execute the initialization script, load
  • add the menu items for the user scripts
Line: 204 to 204
 
  • execute the initialization script, load
  • add the menu items for the user scripts
  • execute any registered PluginProcessors (see below)
Added:
>
>
 In this order.
Changed:
<
<
In general, the installation process of a plug-in consists of three steps or phases. For simple plug-ins, such as have been described until now, nothing is done during the second and third phase. Only the first phase, which is called "bootstrap", is executed. During this installation, the plug-in is downloaded from the URL that indicates its location, and the jar or zip is decompressed in the plug-in directory. Not that the directory, that the plug-in is unpacked into, contains the version of the plug-in. This means that multiple versions of a plug-in can exist on a user's disk, but when HIPE starts, only the latest version of each plug-in will be started.
>
>
In general, the installation process of a plug-in consists of two steps or phases. For simple plug-ins, such as have been described until now, the second phase is skipped. Only the first phase, which is called "bootstrap", is executed. During this bootstrap installation, the plug-in is downloaded from the URL that indicates its location, and the jar or zip is decompressed in the plug-in directory. Note that the directory, that the plug-in is unpacked into, contains the version of the plug-in. This means that multiple versions of a plug-in can exist on a user's disk, but when HIPE starts, only the latest version of each plug-in will be started.
  The second phase is called "custom installation". During this phase, a complete, stand-alone installation program can be executed. Often such programs are Java WebStart programs, but you can also include the installation program in the plug-in itself. If you want to include the custom installation in the plug-in, see the next section for details. If you want to use a WebStart installation program, see the section "Using a WebStart installer".
 
This site is powered by the TWiki collaboration platform Powered by Perl