Hi Lee,<br><br>Great, I tested both pipelines and they work like a charm on my Windows XP system with the build you sent. I took some screenshots and will incorporate into my talk.<br><br>-Curtis<br><br><div class="gmail_quote">
On Thu, Sep 23, 2010 at 1:32 PM, Lee Kamentsky <span dir="ltr"><<a href="mailto:leek@broadinstitute.org">leek@broadinstitute.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
OK, I just finished 4 days of hacking to get CellProfiler to read
the @parameter tags. I also took the plugin that we use the most,
"Tubeness", and converted it to use the tags and removed its gui
code (dialog stuff + image display). The result: CellProfiler runs
an ImageJ plugin, displaying the parameters (including input and
output images) as settings in our module. In this case,
"InputImage", "Sigma", "Use calibration" and "Output image" are the
parameters. The result appears below, totally seamless.<br>
<br>
Curtis, I'll probably give you two pipelines: one that runs on the
current CellProfiler release with the old ImageJ and one that is my
personal build with a bleeding-edge ImageJ 2.0 build. This
reinforces the message we want to send: <br>
<br>
Your plugin is the manifestation of your method or algorithm which
is what's important to you.<br>
Your plugin conforms to the ImageJ 2.0 standard.<br>
Your method can be used by any software that accepts ImageJ 2.0
plugins.<br>
<br>
How cool.<br>
<br>
--Lee<br>
<br>
<img alt="ImageJ 2.0 / CellProfiler 2.0" src="cid:part1.02030204.01010503@broadinstitute.org" height="729" width="1407"><br>
</div>
<br>_______________________________________________<br>
ImageJ-devel mailing list<br>
<a href="mailto:ImageJ-devel@imagejdev.org">ImageJ-devel@imagejdev.org</a><br>
<a href="http://imagejdev.org/mailman/listinfo/imagej-devel" target="_blank">http://imagejdev.org/mailman/listinfo/imagej-devel</a><br>
<br></blockquote></div><br>