Difference: DpHipeComponents (2 vs. 3)

Revision 32008-01-15 - JorgoBakker

Line: 1 to 1

META TOPICPARENT	name="DpHipe"

Adding Components to existing Views

Line: 13 to 13

Outline View

Added:

>
>

Whenever the user selects a session variable e.g. the Variables View, a SelectionEvent is sent around. The Outline View is listening to such an event and it tries to find the appropriate component that can show the outline information of that variable.

<-- If you follow the contract on outline components -->

Line: 25 to 26

Suppose you would like to create an outline for herschel.share.fltdyn.time.FineTime and you would like to show the contents in the outline view whenever a session variable of that type is selected by the user.

Component Implementation

Added:

>
>

In this example, we simply use a javax.swing.JLabel and write the contents of the FineTime object into the text of that label.

Line: 39 to 41

}

Added:

>
>

Component Registry

Added:

>
>

The following snippet, could then go into your __init__.py:

Line: 63 to 67

More information about the extension registry can be found in its Java API (herschel.ia.core.ExtensionRegistry).

Added:

>
>

Added:

>
>

Editor Area

Added:

>
>

The above showed an example of extending the outline view by adding a OutlineComponent. Similarly, you can contribute by developing a specific editor component.

Editor components are browsers or editors of data contents of a specific variable that is selected in the HIPE session.

Line: 87 to 94

}

Added:

>
>

\ No newline at end of file

View topic | History: r23 < r22 < r21 < r20 | More topic actions...