[Insight-users] ITK for fluorescence microscopy - BioImageXD

[alex gouaillard]

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