ITK/Release 4/Wrapping: Difference between revisions

From KitwarePublic
< ITK‎ | Release 4
Jump to navigationJump to search
 
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Wrapping'''
'''Wrapping'''


= Requirements =
= High-Level Goals =


* Avoid unnecessary dependencies
SIMPLIFY ITK by allowing easy access of the toolkit from other languages, especially scripting languages, hiding some difficulties (templates, compilation ...) along the way.
* Wrap +80% of the toolkit
* Have ITK look similar to the native wrapped language


= Tools =
== Metrics and goals ==
 
* Avoid unnecessary dependencies (see Modular ITK)
* WrapITK
* FASTER
* Swig
** faster compilation
* CableSwig
** limited compilation ( see [[ ITK_Release_4/Modularization | modular itk v4 ]] )
* MUMMY
** faster re-compile (touching a given .h should not trigger a full re-compilation)
 
* Wrap 80%+ of the toolkit
= Languages =
* Have ITK behaves in the different languages as close to the native code as possible
 
** ITK Image to/from target language array conversion
What languages to wrap
** Target language inheritance (SWIG directors)
** Automatic type selection in Python
* Binary distribution
* Automatic Inline documentation


== Languages ==
* Java
* Python
* Python
* Lua ?
* Lua ?
* Tcl ?
* Tcl ?
* see simpleITK


[[/Examples|Comparative Examples]]


= Discussions =
= Required Tools and Technology =


== Tcon July 19 2010 ==
Installation is detailled [[/WrapITK_Installation|here]]


* Dropping CableSwig
== tools ==
* Using Swig Directly
* WrapITK.
** Along with GCC_XML
* Swig
 
* GccXML
* 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.
== WrapITK Configuration and Build Process Internals ==
** Maybe use the package manager (Ryppl ?).
** The same goes for the C++ version.


* Remove (or deprecate) itkSetVectorMacro and itkGetVectorMacro
* [[/BuildProcess | Build Process for Dummies ]]
they make the generated methods unusable in the target languages, and are not used that much in ITK


[glehmann@gbook build]$ grep -r etVectorMacro ~/src/Insight/Code/*/*.h | wc -l
== Parallel Build Status ==
    34


They are used in two quite common filters - ChangeInformationImageFilter and PadImageFilter - and this makes this filter at least partly unusable in the target languages.
* [[ITK_Release_4/Wrapping/Parallel_Build_Status|Parallel Build Status]]


= Discussions and TConfs =


== Tcon 808310 ==
* 19-07-2010 - NoAgenda                                      - [[/19072010_Minutes|Minutes]]
=== Agenda 081310 ===
* 13-08-2010 - [[/13082010_Agenda|Agenda]] - [[/13082010_Minutes|Minutes]]


* gccxml maintenance
== Pending Tasks ==
 
* [http://www.vtk.org/Wiki/ITK_Release_4/Wrapping/Tasks here]
who does it?
migration to CLang?
 
* migrating to WrapITK 0.3
* recode igenerator.py in C++
* languages support
** keep python 2
** keep java
** add C#
** add Python 3?
** remove Tcl?
* redefine the WrapITK libraries (grouping of classes)
 
It seems to be tightly linked to [[ITK_Release_4/Modularization]].
 
* Default wrapped types and abbreviated naming scheme
 
Some choices are already made for [[ITK_Release_4/SimpleITK | SimpleITK]
 
* Wrapping coverage
 
100% filters coverage?
 
* Binary distribution
* ITK Image to/from target language array conversion
* Automatic Inline documentation
* Target language inheritance (SWIG directors)
* Automatic type selection in Python
* Improve 64bits support in ITK — surely done elsewhere already
* GDCM wrapping integration?
 
=== Minutes 081310 ===
 
== Attendees ==
 
  Luis Ibañez
  Gabe Hart
  Gaëtan Lehmann
  Brad King
 
== Topics ==
 
* gccxml maintenance
* migrating to WrapITK 0.3
* recode igenerator.py in C++
* languages support
** keep python 2
** keep java
** add C#
** add Python 3?
** remove Tcl?
* redefine the WrapITK libraries (grouping of classes)
* Default wrapped types and abbreviated naming scheme
* Wrapping coverage
* Binary distribution
* ITK Image to/from target language array conversion
* Automatic Inline documentation
* Target language inheritance (SWIG directors)
* Automatic type selection in Python
* Improve 64bits support in ITK — surely done elsewhere already
* GDCM wrapping integration?

Latest revision as of 16:00, 9 December 2011

Wrapping

High-Level Goals

SIMPLIFY ITK by allowing easy access of the toolkit from other languages, especially scripting languages, hiding some difficulties (templates, compilation ...) along the way.

Metrics and goals

  • Avoid unnecessary dependencies (see Modular ITK)
  • FASTER
    • faster compilation
    • limited compilation ( see modular itk v4 )
    • faster re-compile (touching a given .h should not trigger a full re-compilation)
  • Wrap 80%+ of the toolkit
  • Have ITK behaves in the different languages as close to the native code as possible
    • ITK Image to/from target language array conversion
    • Target language inheritance (SWIG directors)
    • Automatic type selection in Python
  • Binary distribution
  • Automatic Inline documentation

Languages

  • Java
  • Python
  • Lua ?
  • Tcl ?
  • see simpleITK

Comparative Examples

Required Tools and Technology

Installation is detailled here

tools

  • WrapITK.
  • Swig
  • GccXML

WrapITK Configuration and Build Process Internals

Parallel Build Status

Discussions and TConfs

Pending Tasks

Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK/Release_4/Wrapping&oldid=44305"