Python binding about imagej2 HOT 8 CLOSED

I could definitively help for this kind of project !

from imagej2.

@hadim: We have no plans to develop and support such a binding. But you could probably do so rather easily via Py4J.

I know CellProfiler has developed a "bridge" but I was thinking a much cleaner and less complex (to maintain and to use) solution.

I would strongly encourage you to work with the CellProfiler team, particularly @LeeKamentsky, regarding that. It would be a shame if every group developed their own binding. If you develop a clean, easy-to-use binding that could be adopted by the CP team, that would be really ideal. Furthermore, I urge you to beware the "Not Invented Here" mentality of discarding the CellProfiler Java bridge just because you didn't create it yourself. It may do what you need, and/or be faster to adapt in needed directions than creating something from scratch.

All of that said, there is no way the core ImageJ2 core development team can prioritize native Python interoperability until after the ImageJ 2.0.0 release (which will hopefully be later this year). I'll leave this ticket open, but it's going to be targeting a much later milestone.

from imagej2.

I perfectly understand your point here. I don't need such a binding in a near future (especially not before IJ 2.0.0 is released). But I think it could be very valuable on long term.

I didn't know Py4J, I will have a look.

from imagej2.

My bad, I didn't have a look to CP javabridge for several years and it seems to have deeply evolved and became a standalone project. I will probably try that first.

from imagej2.

OK, fair enough @hadim!

from imagej2.

The CP javabridge was actually Partially Invented Here... We helped @LeeKamentsky a little bit with the MacOSX part. But please do not misread this in any way as if I wanted to take away any credit for this awesome work: there are hundreds and thousands of hours of beautiful work in there, and it most certainly solves hundreds of bugs anyone would make again if they were to Reinvent The Wheel.

from imagej2.

Yah and @dscho has the award-pony to prove he had a role in it. We are
still about a month away from supporting the Javabridge as a stand-alone
package and some details regarding initialization are still in flux, so I
would hold off for a few weeks before investing any major development time
in it. The devil is in the details - the threading and object lifecycle
management needed turns out to be quite complex.

On Mon, Mar 3, 2014 at 4:56 PM, dscho [email protected] wrote:

The CP javabridge was actually Partially Invented Here... We helped
@LeeKamentsky https://github.com/LeeKamentsky a little bit with the
MacOSX part. But please do not misread this in any way as if I wanted to
take away any credit for this awesome work: there are hundreds and
thousands of hours of beautiful work in there, and it most certainly solves
hundreds of bugs anyone would make again if they were to Reinvent The Wheel.

Reply to this email directly or view it on GitHubhttps://github.com/imagej/ImageJ/issues/35#issuecomment-36565087
.

from imagej2.

;-)

from imagej2.