[ImageJ-devel] Extensions Classes

[Adam Fraser]

I'm slightly removed from this discussion about ROIs, so take this with a
grain of salt.  What makes sense to me would to to have the ROI to return
the data in the cube, then it'd be the viewer's job to subset that further
(possibly by using a second ROI) and display it.

Am I making sense? Stop me if I'm misunderstanding the ROI spec.
-Adam

On Fri, May 7, 2010 at 5:56 AM, Jean-Yves Tinevez <tinevez at pasteur.fr>wrote:

>
> Let us now consider a 3D ROI, in the shape of a cube.
>
> To be drawn on the first viewer, the slice viewer, the ROI needs to have a
> method that specifies what is the currently displayed slice to be properly
> drawn, something like:
>
> @Override
> public abstract void draw(final int current_slice);
>
> On the other hand, the second viewer does not require this, since the ROI
> will be drawn at once. This gives a draw method in the ROI which is like:
>
> @Override
> public abstract  void draw();
>
> How do we deal with that in the mother interface? How do we deal with the
> fact that different viewers might have different requirements for drawing
> objects (images or ROI) and how do we make a mother interface for ROIs, and
> a mother interface for Viewer?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20100507/996ac1b1/attachment.html>