ITK/Release 4/Wrapping: Difference between revisions

From KitwarePublic
< ITK‎ | Release 4
Jump to navigationJump to search
Line 43: Line 43:
* Make easy to add new types (e.g. another pixel type for the image...)
* Make easy to add new types (e.g. another pixel type for the image...)
** Run time binding may help here (along with the internal finder)
** Run time binding may help here (along with the internal finder)
* Make possible (easy?) to distribute binaries of the wrapping.

Revision as of 13:41, 19 July 2010

Wrapping

Requirements

  • Avoid unnecessary dependencies
  • Wrap +80% of the toolkit
  • Have ITK look similar to the native wrapped language

Tools

  • WrapITK
  • Swig
  • CableSwig
  • MUMMY

Languages

What languages to wrap

  • Python
  • Lua ?
  • Tcl ?


Discussions

Tcon July 19 2010

  • Dropping CableSwig
  • Using Swig Directly
    • Along with GCC_XML
  • Two Levels of Wrapping
    • Wrapping the Simplified Layer (many wrapping tools will do)
    • Wrapping the Templated Layer (WrapITK,GCC_XML)
  • Managing multiple component images
    • Microscopy use cases
    • Remote Sensing cases
    • itkVectorImage ?
    • need a "component-by-component" filter driver ?
  • Make easy to add new types (e.g. another pixel type for the image...)
    • Run time binding may help here (along with the internal finder)
  • Make possible (easy?) to distribute binaries of the wrapping.