[Insight-users] ITK for fluorescence microscopy - BioImageXD

[alex gouaillard]

hi badri,

AFAIK ITK and VTK are *very* well supported on macs.

There around 10 mac builds servers submitting everyday to ITK dashboard.

Then, Rogue Research has been doing a lot of work to make it even  
better in the past year or so (kudos to sean McBride and other there  
for getting all the possible optimization for the mac version of gcc,  
and bill and luis for their hard work on cleaning the corresponding  
warning and errors ).

ITK and VTK both compiles well in 64bits under Mac.

The two problems we were discussing here are related to wxPython and  
QT. Both librairies/toolkit do no support cocoa very well on mac  
(yet). They work well with carbon, which is only 32 bits.

It looks like wxPython is far away from catching up on that.  
Fortunatly, Qt is almost there.

alex.


On May 12, 2009, at 8:54 AM, Badri Roysam wrote:

> I believe that some community initiatives to improve support for ITK  
> & VTK on macs
> is particularly important for the microscopy community since most  
> end users prefer
> macs.
>
>
> Badri Roysam
> Professor, Department of Electrical, Computer and Systems Engineering
> Associate Director, NSF Center for Subsurface Sensing & Imaging  
> Systems (CenSSIS ERC)
> Co-Director, Rensselaer Center for Open Source Software
> Rensselaer Polytechnic Institute
> 110 8th Street, Troy, New York 12180-3590, USA.
> Office(JEC 7010): 518-276-8067, Assistant: 518-276-8525, Lab(JEC  
> 6308): 518-276-8207, Fax: 518-276-8715
> Email: roysam at ecse.rpi.edu, Web: http://www.ecse.rpi.edu/~roysam
>
>
>
> ----- Original Message -----
> From: alex gouaillard [mailto:Alexandre_Gouaillard at hms.harvard.edu]
> To: Lassi Paavolainen [mailto:lopaavol at jyu.fi]
> Cc: ITK [mailto:insight-users at itk.org], Daniel James White [mailto:white at mpi-cbg.de 
> ]
> Subject: Re: [Insight-users] ITK for fluorescence microscopy -  
> BioImageXD
>
>
>> hi,
>>
>> We are also monitoring Qt 4.5 with Cocoa for the same reason. our
>> latest test last week shows that it is not yet working well enough,
>> but it is almost there. We think it's going to work within weeks and
>> not months. Mac is the only platform under which we cannot make a
>> 64bits build as of today. We had been working with wxWindow, and
>> KWWidgets before that, it was not as feature extensive and
>> professional looking as QT is. Moving Qt to LGPL was a great move  
>> from
>> Nokia :D
>>
>> It is surely a naive question , as I don't know how you work
>> internally, but is there a specific reason why you would go from
>> python to Java instead of C++? As you are already using VTK and ITK  
>> as
>> your core, why going through the extra wrapping step when you could  
>> do
>> it all in C++? Then, you would be able to handle maintenance using
>> CMake / CTest / CPack / CDash.
>>
>> Again, I'm sure you have your own reasons, andthat  it is a naive
>> question. I'm just curious.
>>
>> alex.
>>
>>
>> On May 12, 2009, at 7:50 AM, Lassi Paavolainen wrote:
>>
>>> Hi Alex and Dan,
>>>
>>> On Tue, 12 May 2009, alex gouaillard wrote:
>>>
>>>> On May 12, 2009, at 4:24 AM, Daniel James White wrote:
>>>>
>>>>> BXD might well move to java wrapped VTK/ITK from python in the
>>>>> future,  primarily for platform independence reasons: No 64 Bit
>>>>> Carbon
>>>>> on OSX.
>>>>> That would also allow a direct interface with Fiji-ImageJ , which
>>>>> would be very cool.
>>>>
>>>> Why not using Cocoa instead of carbon if you want 64 bits?
>>>> Java rapping is interesting on hits own, of course, for other
>>>> reasons.
>>>
>>> I'm no Mac expert but the reason is that wxPython cannot be compiled
>>> in 64
>>> bits in Cocoa if I remember correctly. We are looking into QT 4.5
>>> for that
>>> reason also.
>>>
>>> Actually that is not the primarily reason to investigate using Java
>>> but
>>> only one. There are also other reasons mainly focusing on software
>>> development process (new architecture, handling of 50k+ LOC,  
>>> testing,
>>> documentation, work force) and other future plans like 64 bitness  
>>> and
>>> networking.
>>>
>>> Of course Python has its own benefits including dynamic type system
>>> and
>>> already well working wrapping of ITK. By the way, is Java wrapping
>>> of ITK
>>> already as well working as is Python wrapping?
>>>
>>> Lassi
>>>
>>> -- 
>>> Lassi Paavolainen, M.Sc.
>>> Software Engineer
>>> BioImageXD (http://www.bioimagexd.net)
>>> lopaavol at jyu.fi
>>
>> _____________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.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-users
>>