Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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: | |||||||
![]() | ||||||||
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: ![]() | |||||||
Modifier![]() | ||||||||
Added: | ||||||||
> > |
One of the Modifier in the input area for the crop task: ![]() | |||||||
Currently the system contains basic implementation for the simple types![]() | ||||||||
Line: 121 to 130 | ||||||||
Register a Modifier | ||||||||
Changed: | ||||||||
< < | The registration of the Modifier is done again in the __init__.py via the ModifierFactory![]() | |||||||
> > | 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: ![]() | |||||||
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: | ||||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
|