[Insight-developers] Wrapping - WrapITK

Alexandre GOUAILLARD agouaillard at gmail.com
Sun Nov 7 16:57:29 EST 2010


hi david,

long time since beijing.

thanks for the offer.

It looks like the tcl wrapping (new wrapitk merged into the v4 branch)
is operational, at least under linux. It fails under mac, but I kind
of remember that tcl shipped with mac is not working by default, so I
guess I need to put a little bit more energy in getting a cleaner
version of tcl, recompiling it, and trying again.

regards,

alex.


On Mon, Nov 8, 2010 at 12:07 AM, Holmes, David R. III, Ph.D. [RO
RM1-24] <Holmes.David3 at mayo.edu> wrote:
> Alex-
>
> If you get in a bind with the TCL wrapping and everyone is pushing for it (which it doesn't look like there is much interest), please let me know.  I gave Gaetan some code a very long time ago (years) which he may have used in early versions of wrapITK for TCL.  I might be able to look at it again.  Otherwise, TCL can quietly be put to pasture.
>
> Thanks
>
> david
>
> ====================================================
> David R Holmes III
> Biomedical Imaging Resource Core Facility Director
>
> Department of Physiology and Biomedical Engineering
> Mayo Clinic College of Medicine
>
> Ph:  507-266-4250       Fax:  507-284-1632
> holmes.david3 at mayo.edu
> ====================================================
>
>
> -----Original Message-----
> From: insight-developers-bounces at itk.org [mailto:insight-developers-bounces at itk.org] On Behalf Of Alexandre GOUAILLARD
> Sent: Thursday, November 04, 2010 9:40 AM
> To: kent williams
> Cc: ITK
> Subject: Re: [Insight-developers] Wrapping - WrapITK
>
> hi kent,
>
> I think moving to python makes a lot of sense and is definitely the
> way of the future.
>
> WrapITK was a one man show. The mechanism for tcl wrapping is in
> place. I'm going to run it and see if we're lucky or not. I'm neither
> a tcl expert nor (yet) a wrapitk expert, so I might need your help to
> read / guess through the errors though. In one hour together in iowa
> we should be able to assess the needed effort (or actually make it
> work, who knows)
>
> We decided at washington that TCL would not be a "first class"
> citizens of itk wrapping, i.e. that the mechanism to wrap in tcl would
> be here, but maintenance should be done by elements of the community
> that need it (as opposed to python, java and C#).
>
> alex.
>
> On Thu, Nov 4, 2010 at 10:26 PM, kent williams
> <norman-k-williams at uiowa.edu> wrote:
>> Alexandre -- Tcl wrapping in the abstract would be A Good Thing.  But for
>> BRAINS development at Iowa the current thinking is to abandon Tcl as a
>> scripting language and move to Python when we go to ITKV4.  At this point --
>> no offense -- Tcl hasn't gotten much love from WrapITK, and what Hans told
>> me is that it wasn't going to be supported in ITKV4.
>>
>> On the other hand, most of the current BRAINS3 tests are in Tcl and exercise
>> Tcl wrapping.  Will the new WrapITK change the bindings enough to break
>> existing code?  If the bindings are intact, testing with BRAINS3 could be
>> done quickly.
>>
>> 30 Hours on a plane? I can't begin to tell you how much I'd dread such a
>> thing!
>>
>>
>> On 11/4/10 2:10 AM, "Alexandre GOUAILLARD" <agouaillard at gmail.com> wrote:
>>
>>> dear all,
>>>
>>> just a quick message to let you know that Gaetan merged the newest
>>> version of wrapitk in an itkv4 branch there:
>>> https://github.com/glehmann/ITK/tree/wrapitk
>>>
>>> and that I'm actively working on making it work.
>>>
>>> As of today, the python (2.x) version is fully operational and Im
>>> working on the java wrapping. I sent an experimental, but dashboard
>>> seems to be unstable still. The idea is to have a fully operational
>>> integration by next week to present at the meeting (along with a full
>>> implementation of PACS support from mathieu M., support for RT STRUCT,
>>> and most of the streaming for Dicom as well).
>>>
>>> kent: if java wrapping is working early enough, I will spend some of
>>> my 30 hours of plane this week end to take a look at the tcl wrapping.
>>> If you want, we can try to take some time to look into it, even though
>>> I do not commit to make it work.
>>>
>>> wanlin, wen li, luis and the few waiting for me to bring in some mesh
>>> filters, sorry, I won't be able to work on that until monday at best.
>>>
>>> alex.
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Kitware offers ITK Training Courses, for more information visit:
>>> http://kitware.com/products/protraining.html
>>>
>>> Please keep messages on-topic and check the ITK FAQ at:
>>> http://www.itk.org/Wiki/ITK_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>
>>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>


More information about the Insight-developers mailing list