[ImageJ-devel] [IMGLIB] moved algorithm and stats packages out of imglib2-core

[Curtis Rueden]

Hi Albert, Tobias and everyone,

> I.e., Histogram should not have an getHistogram()
> > that returns an int[] array which represents the histogram.  Rather,
> > Histogram itself should represent the histogram.  For example, it could
> > implement RandomAccessibleInterval< IntType > to achieve that, and the
> > histogram could be computed in the constructor.
>
> I agree with that. The scripting library follows this approach to the
> fullest. Functions on images are images themselves.
>

I also think this is a good idea. However, we don't currently have time to
make these changes. So for now I split the imglib2-algorithms package as
discussed. This allowed us to fix the ImageJ2 build.

I have filed a ticket to remind us about the proposed Histogram changes:
  http://code.imagej.net/trac/imagej/ticket/1041

Tobias, you are CCed. Anyone else interested let me know and I will add you
to the CC list.

Regards,
Curtis


On Thu, Mar 1, 2012 at 4:46 AM, Albert Cardona <sapristi at gmail.com> wrote:

> El 1 de març de 2012 5:39, Tobias Pietzsch <pietzsch at mpi-cbg.de> ha
> escrit:
> > Hi all,
> >
> >
> > On 02/29/2012 09:30 PM, Curtis Rueden wrote:
> >>
> >> 2) Split imglib2-algorithms into multiple components:
> >> imglib2-algorithms-bsd and imglib2-algorithms-gpl, for example. Then we
> >> can include imglib2-algorithms-bsd as a dependency for ImageJ2.
> >
> >
> > This is the option I would prefer.
> > If you could do the split, Curtis, that would be great.
> >
> > I do not think that the definition for "core" should be "everything
> > needed by ImageJ2". I don't see a problem with splitting ImageJ2
> > dependencies.
>
> That is sensible.
>
> > I don't have a problem with having Histogram in the core, either.
> > But then it should not implement the Algorithm interface (I don't
> > get the point of the Algorithm interface, to be honest).  Equally
> > important: it should not _feel_ like an algorithm, rather it should
> > _be_ the histogram.  I.e., Histogram should not have an getHistogram()
> > that returns an int[] array which represents the histogram.  Rather,
> > Histogram itself should represent the histogram.  For example, it could
> > implement RandomAccessibleInterval< IntType > to achieve that, and the
> > histogram could be computed in the constructor.
>
> I agree with that. The scripting library follows this approach to the
> fullest. Functions on images are images themselves.
>
> Albert
>
> --
> http://albert.rierol.net
> http://www.ini.uzh.ch/~acardona/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20120301/a0860699/attachment.html>