Difference: DpHipePluginsUserManual (3 vs. 4)

Revision 42010-09-14 - PaulBalm

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

HIPE Plug-in User Manual

This is the user manual for HIPE Plug-ins. It describes what plug-ins are, where to get them, how to install them, and how to get rid of them.

Changed:
<
<
If you are interested in creating plug-ins yourself, please refer to the Plug-in Developer's Manual [TBD]. For the motivation behind design choices made when building the Plug-in Framework for HIPE, see the Design Document.
>
>
If you are interested in creating plug-ins yourself, please refer to the Plug-in Developer's Manual. For the motivation behind design choices made when building the Plug-in Framework for HIPE, see the Design Document.
 

Introduction: What's a plug-in and what's it for

Plug-ins are intended to make it easy to share software (written in Java and/or Jython) and to share data in the form of LocalStores. A secondary purpose is to allow existing applications to be "plugged into HIPE": A plug-in for an existing application can add menus and menu items to HIPE. The user can then use those menus to use the application, within HIPE.

Added:
>
>
A plug-in contains scripts that are to be run at start-up, for example scripts that define Tasks. Such scripts are also run at the start-up of jylaunch, so that you can also use (for example) Tasks or data pools from plug-ins. You still need HIPE to install the plug-ins, and jylaunch loads the plug-ins from the same directories as HIPE.
 The plug-in framework was designed to make it very easy for users to install and use plug-ins, while at the same time making it simple for creators of plug-ins to produce the plug-ins. In most cases, creating a plug-in is a matter of zipping or jarring whatever it is you want to share, and putting it on-line. The user gets the URL of the plug-in, puts it into HIPE and hits install. In many case (nearly all, I hope), this will be enough. Clearly, it will require more work to create a plug-in that adds menus, Views, Perspectives, and so on, but for the user this doesn't make a difference. Installation is one-click in principle. A plug-in developer may construct a custom installer for a plug-in allowing more configuration, but requiring more clicks from the user.

How to get plug-ins

Changed:
<
<
Anyone can put a plug-in on-line anywhere, but we have created a Wiki page that is intended as a repository, or at least a starting point for finding the plugins. The Wiki is DpHipePlugins. It is not necessary to bookmark or remember the address of this page. If you select Plug-ins from the Tools menu in HIPE, the Plug-ins panel opens. This panel shows the currently installed plug-ins and has two links at the top: One for finding new plug-ins and one for installing new plug-ins. Clicking the "find new plug-ins" link opens a web-browser and navigates to the DpHipePlugins Wiki.
>
>
Anyone can put a plug-in on-line anywhere, but we have created a Wiki page that is intended as a repository, or at least a starting point for finding the plug-ins. The Wiki is DpHipePlugins. It is not necessary to bookmark or remember the address of this page. If you select Plug-ins from the Tools menu in HIPE, the Plug-ins panel opens. This panel shows the currently installed plug-ins and has two links at the top: One for finding new plug-ins and one for installing new plug-ins. Clicking the "find new plug-ins" link opens a web-browser and navigates to the DpHipePlugins Wiki.
  Using the URL where a plug-in is offered (the plug-in download URL, so to speak), you can install the plug-in. In the Plug-ins panel click the link to Install a new plug-in. Enter the URL in the URL field and click Install. That's all!
 
This site is powered by the TWiki collaboration platform Powered by Perl