Difference: DpHipeRegistry (8 vs. 9)

Revision 92010-06-10 - DavideRizzo

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

The Extension Registry

<-- summary -->
Changed:
<
<
You must register your contribution (whether it is a tool, perspective, view, component to views or component to the editor area) to HIPE to make it part of the application. Registering means that you have to write add an entry to the jython package module (aka __init__.py) within the sub-system that is under your control.
>
>
You must register your contribution (whether it is a tool, perspective, view, component to views or component to the editor area) to HIPE to make it part of the application. Registering means that you have to write add an entry to the jython package module (aka __init__.py) within the sub-system that is under your control.
  This section explains the workings of the registry works and how it can automatically find your contribution.
Line: 18 to 18
 
Deleted:
<
<
 

Introduction

The registry mechanism relies on the recursive reading of the jython package modules built into the HCSS. The application will execute the following line:
Line: 155 to 154
  It is a component that shows structure of a Product within the Outline View.
Changed:
<
<
Warning, important PaulBalm: Note that for Factory Extensions, arg1 is a classname and arg2 is the ID of the view the factory belongs to. For Component Extensions, arg1 is the ID of the factory and arg2 is a classname. These feel switched with respect to each other, so check the definitions carefully.
>
>
Warning, important Note that for Factory Extensions, arg1 is a classname and arg2 is the ID of the view the factory belongs to. For Component Extensions, arg1 is the ID of the factory and arg2 is a classname. These feel switched with respect to each other, so check the definitions carefully.
  See also the component contribution pages.
 
This site is powered by the TWiki collaboration platform Powered by Perl