[Insight-developers] Re: Integrating WrapITK into ITK CVS

[Gaetan Lehmann]

On Sun, 03 Sep 2006 14:59:39 +0200, Luis Ibanez <luis.ibanez at kitware.com>  
wrote:

>
> Hi Gaetan, Zach
>
>
>
> Thanks for clarifying the situation with the API of the Wrapping
> in the target languages, and the proposed changes to CableSwig.
>
>
>
> It seems that we all agree in uploading WrapITK now, and to look
> later at the potential CableSwig improvements.
>
>
>
> Here is a suggestion for a plan of action:
>
>
> 1) Freeze the repository for a couple of days. That is, remove write
>     access from everybody, except the developers that will be involved
>     in integrating WrapITK.
>
> 2) The developers that will do the integration will be: Gaetan, Zach,
>     and will have support from Luis, Bill Hoffman and Brad)
>
> 3) We will tag the repository as "Before adding WrapITK".
>
> 4) Proceed to commit WrapITK code
>
> 5) Stabilize the major platforms: Linux, Windows.
>
> 6) Tag the repository as "After adding WrapITK"
>
> 7) Open again write access to restore the status before (1).
>
>
>
> I would suggest the following schedule:
>
>
>     --------------------------------------------------
>     |  Tasks  | Dates                                |
>     --------------------------------------------------
>     | (1,2,3) | Wednesday September 6th              |
>     | (4)     | Thursday-Friday September 7-8th      |
>     | (5)     | Weekend Sept 8-9th                   |
>     | (6,7)   | If Dashboard green: Monday Sept 10th |
>     --------------------------------------------------
>
>
>
> Gaetan:
>
>       As preparation, what you may want to do is to start in
> your local copy of ITK setting all the infrastructure, so you
> will be ready to commit the changes. Let's make WrapITK to be
> an option in CMake, OFF by default. In this way we can turn it
> ON, machine by machine in the Dashboard. Depending on how things
> go by mid October, we should vote on whether we want WrapITK to
> be the default wrapping for ITK 3.0.
>
>
>
> Please let us know if this sounds reasonable to you,

It looks nice to me :-)

Gaetan


>
>
>     Thanks
>
>
>
>       Luis
>
>
>
>
> ----------------------
> Gaëtan Lehmann wrote:
>>  Hi Luis,
>>  I also thought to the possible changes to cableswig:
>>  - Change of API in the cmake part
>> The usage of cableswig is fully hidden in WrapITK and in its external   
>> projects: everything is generated by cmake. They were some exceptions  
>> (for  vcl_complex for example), but even those more difficult cases are  
>> now  generated with cmake.
>>  - Change of API in the target language
>> All the changes we can plan in cableswig will not change the api of ITK  
>> in  the target languages - the names of the instantiations are now  
>> good  enough, and all the other names are the names defined in ITK.  
>> With the  changes in cableswig, we'll "only" add new features and  
>> better integration  with the target languages.
>>  So I think we should upload WrapITK into ITK now, keep cableswig as it  
>> is  for the upcoming release (3.0), but still continue to work on  
>> cableswig  for the next release (3.2).
>>  Regards,
>>  Gaetan
>>   Le Sun, 03 Sep 2006 01:38:09 +0200, Luis Ibanez  
>> <luis.ibanez at kitware.com>  a écrit:
>>
>>>
>>> Hi Gaetan,
>>>
>>> That is great news.
>>>
>>> Should we hold on modifications related to CableSwig
>>> and upload the current version of WrapITK into ITK ?
>>>
>>> We talked about this during the tcon, and the only concern was
>>> the possibility that the future proposed changes to CableSwig
>>> may change the API of the wrapping. Do you think this is a real
>>> source of concern ?
>>>
>>>
>>> Please let us know,
>>>
>>>
>>>     Thanks
>>>
>>>
>>>        Luis
>>>
>>>
>>>
>>> ---------------------
>>> Gaëtan Lehmann wrote:
>>>
>>>>  Hi,
>>>>  I have made the changes I wanted to do. Quite surprisingly, I have  
>>>> even
>>>> turn on some features that we had disabled in the past, because of  
>>>> build
>>>> or runtime errors. Not sure what happened - perhaps Brad or Bill have
>>>> fixed some stuff in cableswig ? - but that's nice :-)
>>>> All the tests are passing, with the 3 languages. I think everything is
>>>> ready to move WrapITK to ITK cvs.
>>>> However I'm not sure what is the right procedure to do that. Please  
>>>> let  me
>>>> know how you would like to proceed.
>>>>  Thanks,
>>>>  Gaetan
>>>>   PS: sorry for the double post - the list is asking me to remove  
>>>> some   recipients
>>>>  Le Fri, 25 Aug 2006 22:24:25 +0200, Luis Ibanez   
>>>> <luis.ibanez at kitware.com>
>>>> a écrit:
>>>>
>>>>> We need to put together a schedule + transition plan
>>>>>    on how to bring WrapITK into the ITK CVS repository.
>>>>>     For example:
>>>>>        September 1st:  Commit WrapITK code under
>>>>>                       Insight/Wrapping. This include
>>>>>                       a pre and post CVS tag. We may
>>>>>                       freeze the repository for a couple
>>>>>                       of days in order to do this.
>>>>>        September 10:   Complete configuration changes
>>>>>                       on CMakeLists.txt files for
>>>>>                       making WrapITK an option
>>>>>        September 15:   Enable WrapITK as default
>>>>>                       wrapping in several platforms
>>>>>                       on Dashboard machines.
>>>>>                       Linux gcc 3.4, 4.0 and VC++ 7.1.
>>>>>        September 25:   Enable WraptITK as default
>>>>>                       wapping in all Dashboard machines
>>>>>
>>>>
>>>
>>>
>>
>



-- 
Gaëtan Lehmann
Biologie du Développement et de la Reproduction
INRA de Jouy-en-Josas (France)
tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
http://voxel.jouy.inra.fr