Documentation/Third Party Dependencies

From Commontk
Revision as of 07:10, 28 November 2011 by Sascha (talk | contribs) (moved Documentation/Architecture to Documentation/Third Party Dependencies: Page contents did not match the title.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
Home < Documentation < Third Party Dependencies

While the details of the implementation have yet to be finalized, a few of the design principles have been decided by the founding group. In particular, several core libraries will serve as the foundation.

Overall object structure will be based on Qt 4.5

See the [wiki:WidgetPlans Widget Plans page]. See the [wiki:CodingGuidelines Coding Guidelines page].

DICOM support will be implemented using DCMTK

Visualization will use VTK

Analysis algorithms will use ITK

Software engineering methodology will follow the ITK style (leveraging CMake and friends)

A To-be-determined wrapping tool will support calling CTK from Python, Tcl, Java, C#, etc

Open Questions

  • Qt Script (javascript) provides a subset of "traditional" VTK-style wrapping. PyQt is GPL so not usable in CTK. What are the other alternatives?
    • Perhaps PythonQt - it is LGPL and lighter (less complete) than PyQt. It is a product of the MeVisLab effort.
    • PySide appears to be the nokia-sponsored replacement for PyQt.
  • What third party widget libraries exist for Qt? What licenses do they use? (Since the open source version of Qt was GPL until recently, most third party libraries are probably GPL also). For example, the QDCWS project combines DCMTK with Qt but is GPL (and no longer active, apparently - email to the developer bounced).