IntegrationLevel2Details: Difference between revisions
MarcoNolden (talk | contribs) (Created page with '== Scenario 2a == I have an image processing module that I want to run in the Slicer, MITK or GIMIAS application. The parameters of the module shall be adjustable in the applica…') |
MarcoNolden (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
I use the CTK command line interface module which helps me to publish my parameters, parse command line calls and on the host to communicate the processing parameters between my module and the application. | I use the CTK command line interface module which helps me to publish my parameters, parse command line calls and on the host to communicate the processing parameters between my module and the application. | ||
== Limitation === | === Limitation === | ||
You do not have access to application features or other modules from inside your module. | You do not have access to application features or other modules from inside your module. | ||
Revision as of 09:29, 27 January 2011
Home < IntegrationLevel2DetailsScenario 2a
I have an image processing module that I want to run in the Slicer, MITK or GIMIAS application. The parameters of the module shall be adjustable in the application, e.g. with a generated GUI.
Solution
I use the CTK command line interface module which helps me to publish my parameters, parse command line calls and on the host to communicate the processing parameters between my module and the application.
Limitation
You do not have access to application features or other modules from inside your module.
Scenario 2b
I have an application, e.g. a PACS/DICOM viewer, that I want to extend with the possibility to run command line modules following the CTK standard / parameter conventions.
Solution
You use the command line interface support module for parsing parameter descriptions. If your application is using Qt you can optinally use the GUI generator for creating a GUI for the module parameters.
