Difference: DpHipeTools (9 vs. 10)

Revision 102008-02-14 - NicolaDeCandussio

Line: 1 to 1

META TOPICPARENT	name="DpHipe"

Adding Tools to HIPE

Line: 82 to 82

The system generates a default input dialog for all registered tasks within the software. As the system does not know the intent of your task, it can only provide a dry-listing of all requested parameters; such a dialog may not be suitable for your purposes.

Added:

>
> * The default dialog:

As for instance you may want to have more control over how the input parameters are presented to the user:

you may only want to provide a sub-set of parameters (and leave the full-set to expert users on the command-line)
you may want to organize your parameters by grouping them in tabs, or putting a border around a group of parameters

Line: 96 to 99

Parameter Modifiers

Changed:

<
< The system provides a default dialog displaying an input area for setting the values of the parameter. Based on the type of the value of the Task Parameter the input area dinamically load the most appropriated (and registered) component satisfying the contract of the

>
> The system provides a default dialog displaying an input area for setting the values of the parameter. Based on the type of the value of the Task Parameter the input area dinamically loads the most appropriated (and registered) component satisfying the contract of the

Modifier.

Changed:

<
< Currently the system contains basic implementation for the simple types Integer, Float, Long, Double.

>
> Currently the system contains basic implementation for the simple types Integer, Float, Long, Double so there's still a lot of space for improvements and contribution.

Added:

>
>

If your Task Parameter doesn't follow into the mentioned types you need to:

Implement a Modifier
Register it to the system.

Implement a Modifier

The modifier interface consists of two explicit contracts

Support the drag and drop features (the set/getVariableSelection)

Support the inspection for Object (the set/getObject)
and two implicit contracts inherited by the ExtensionRegistry

Be JComponent

Have an empty constructor

Register a Modifier

The registration of the Modifier is done again in the __init__.py via the ModifierFactory with the same syntax (please note the name of the factory: factory.modifier).
 REGISTRY.register(COMPONENT,Extension(
        "MyModifier",
        "herschel.ia.mymodifier.MyModifier",
        "factory.modifier",
        "herschel.ia.MyClass")

Signature Components

Added:

>
>

For that you can implement a herschel.ia.task.gui.dialog.SignatureComponent and register it as follows (again in the __init__.py):

    REGISTRY.register(COMPONENT,Extension(

Line: 128 to 161

See also the Extension Registry documentation for more details.

Note that your GUI component must have a default constructor!

Added:

>
>

Task Dialogs

The default dialog provided by the system is result of the composition of a main input area (TaskSignatureComponent) and a panel containing the buttons (JTaskButtonsPanel). The main panel is based

Line: 142 to 177

<-- Author: JorgoBakker - 21 Dec 2007 -->

Changed:

<
<

META FILEATTACHMENT	attachment="hipe-tools.jpg" attr="h" comment="Task, tools and variables" date="1198422542" name="hipe-tools.jpg" path="hipe-tools.jpg" size="13675" stream="hipe-tools.jpg" user="Main.JorgoBakker" version="1"

>
>

META FILEATTACHMENT	attr="h" autoattached="1" comment="Task, tools and variables" date="1198422543" name="hipe-tools.jpg" path="hipe-tools.jpg" size="13675" user="Main.JorgoBakker" version="1"
META FILEATTACHMENT	attr="h" autoattached="1" comment="" date="1203007458" name="crop.jpg" path="crop.jpg" size="20487" user="Main.NicolaDeCandussio" version="1"

View topic | History: r113 < r112 < r111 < r110 | More topic actions...