IntegrationLevel2Details: Difference between revisions

From Commontk
Jump to navigationJump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[File:CTK-Level2.png]]
== Scenario 2a ==
== Scenario 2a ==



Latest revision as of 10:03, 31 January 2011

Home < IntegrationLevel2Details

CTK-Level2.png

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 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.