Difference: DpHipeTools (10 vs. 11)

Revision 112008-02-15 - 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.
Changed:
<
<
* The default dialog:
>
>
The default dialog for the crop task:
  crop.jpg

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

Line: 99 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 loads 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.

The input area for the crop task:
crop_input.jpg

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.
Added:
>
>
One of the Modifier in the input area for the crop task:
crop_modifier.jpg
 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.

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

Line: 121 to 130
 

Register a Modifier

Changed:
<
<
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).
>
>
The registration of the Modifier is done again in the __init__.py via theExtensionRegistry with the usual syntax (please note the name of the factory: factory.modifier).

Be aware that the registration is system wise so the registration overrides any other registered modifier.

 
 REGISTRY.register(COMPONENT,Extension(

Line: 130 to 141
  "factory.modifier", "herschel.ia.MyClass")
Added:
>
>
In case the Modifier you have created is only applicable to a specific task or even to a specific parameter of a specific task you can simply assign it to the Task Parameter itself:

        // In your task constructor
        TaskParameter parameter =  new TaskParameter("input", String.class);
        parameter.setModifier(new MyModifer());
 

Signature Components

Line: 137 to 158
 
Added:
>
>

Rotate Alternative Signature:
rotate.jpg

 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: 179 to 205
 
Added:
>
>
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1203070875" name="crop_input.jpg" path="crop_input.jpg" size="17033" user="Main.NicolaDeCandussio" version="1"
META FILEATTACHMENT attr="h" autoattached="1" comment="Rotate Alternative Signature" date="1203074625" name="rotate.jpg" path="rotate.jpg" size="19901" user="Main.NicolaDeCandussio" 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"
Added:
>
>
META FILEATTACHMENT attr="h" autoattached="1" comment="modifier" date="1203071348" name="crop_modifier.jpg" path="crop_modifier.jpg" size="16408" user="Main.NicolaDeCandussio" version="1"
 
META FILEATTACHMENT attr="h" autoattached="1" comment="" date="1203007458" name="crop.jpg" path="crop.jpg" size="20487" user="Main.NicolaDeCandussio" version="1"
 
This site is powered by the TWiki collaboration platform Powered by Perl