Line: 1 to 1 | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Adding Tools to HIPE | |||||||||||
Line: 120 to 120 | |||||||||||
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.
The default dialog for the crop task: | |||||||||||
Changed: | |||||||||||
< < | ![]() | ||||||||||
> > | ![]() | ||||||||||
As for instance you may want to have more control over how the input parameters are presented to the user:
| |||||||||||
Line: 130 to 130 | |||||||||||
![]() | |||||||||||
Changed: | |||||||||||
< < | Provided modifiers have been updated but some modifiers are too wide for this layout (ex. AngleModifier, can have 3 texts and 1 combo in a line). | ||||||||||
> > | Provided modifiers have been updated but some modifiers are too wide for this layout (ex. AngleModifier, can have 3 texts and 1 combo in a line, see rotate later). The default dialog for the crop task, with all sections opened: ![]() | ||||||||||
To adapt to these scenarios and more, the system provides three ways for customizing you Task dialogs:
| |||||||||||
Line: 144 to 147 | |||||||||||
The system provides a default dialog displaying an input area for setting the values of the parameter based on a composition of Modifiers![]() | |||||||||||
Changed: | |||||||||||
< < | ![]() | ||||||||||
> > | ![]() | ||||||||||
The composition of Modifiers![]() | |||||||||||
Changed: | |||||||||||
< < | ![]() | ||||||||||
> > | ![]() | ||||||||||
Currently the system contains basic implementation for the simple types Boolean , Integer , Float , Long , Double , String and few more, so there's still a lot of space for improvements and contribution. You can find the general available modifiers in package herschel.ia.gui.apps.modifier ; please consult the Javadoc of your HIPE installation. | |||||||||||
Line: 221 to 224 | |||||||||||
In case the default input area based on Modifiers doesn't fit your needs you can just replace it by your own implementation. | |||||||||||
Changed: | |||||||||||
< < | Rotate Alternative Signature: | ||||||||||
> > | Rotate Alternative Signature (old): | ||||||||||
![]() | |||||||||||
Added: | |||||||||||
> > | Rotate Alternative Signature (new): ![]() | ||||||||||
If this is the case you need to:
| |||||||||||
Line: 264 to 270 | |||||||||||
Added: | |||||||||||
> > | ![]() You no longer need a signature component to choose your own modifiers for your task (and link them with events ...): Task has a new function public Map<String, Modifier> getCustomModifiers()where you can do just that, see above "Register a Modifier". Conventions for labels for input parameters: (see DM). The static function public static JLabel getDecoratedLabel(TaskParameter tp, boolean isPrimeInput, String altName)provides a decorated label (including tooltip) that follows the standard style. For the function to work properly your task parameters should be fully configured (for example, the parameter description will be the tooltip of the label) If some other function needs to be made public so that tasks can follow the default style, they will be added above. | ||||||||||
Register a Task Signature Component | |||||||||||
Line: 280 to 295 | |||||||||||
See also the Extension Registry documentation for more details. | |||||||||||
Deleted: | |||||||||||
< < | ![]() public static JLabel getDecoratedLabel(TaskParameter tp, boolean isPrimeInput, String altName)provides a decorated label (including tooltip) that follows the standard style. If some other function needs to be made public so that tasks can follow the default style, they will be added above. | ||||||||||
Line: 570 to 579 | |||||||||||
| |||||||||||
Added: | |||||||||||
> > |
| ||||||||||
| |||||||||||
Added: | |||||||||||
> > |
| ||||||||||
| |||||||||||
Added: | |||||||||||
> > |
| ||||||||||
|