Hi Albert,<br><br>Thanks for your comments. To be clear, something like EasyMock would be for the unit tests, not for use in ImageJ core itself. The unit tests are mainly a solid way to help avoid regression bugs as the code evolves.<br>
<br>-Curtis<br><br><div class="gmail_quote">On Tue, Apr 20, 2010 at 7:39 AM, Albert Cardona <span dir="ltr"><<a href="mailto:sapristi@gmail.com">sapristi@gmail.com</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;">
Rick,<br>
<div class="im"><br>
<br>
> I thought this article was good for demonstrating how to apply Easymock to<br>
> imagej/imglib.<br>
<br>
<br>
</div>ImageJ 1.0 and earlier was small and simple, and had the<br>
extraordinarily valuable quality that it worked. It was immediately<br>
used in production. Biological researchers applied it for their image<br>
processing needs. Their feedback fueled the growth of ImageJ over the<br>
next decade.<br>
<br>
I suggest you build a small application that uses imglib/ImageJ2.0<br>
features rather than a mock up. Effort-wise, it may be about the same.<br>
<br>
Best,<br>
<br>
Albert<br>
<font color="#888888">--<br>
<a href="http://albert.rierol.net" target="_blank">http://albert.rierol.net</a><br>
<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>
</font></blockquote></div><br>