NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1873 (closed defect: moved)

Opened 2013-05-15T13:46:32-05:00

Last modified 2013-09-25T15:04:23-05:00

New legacy layer approach

Reported by: bdezonia Owned by: bdezonia
Priority: major Milestone: imagej2-b8-analysis
Component: Legacy Compatibility Version:
Severity: serious Keywords:
Cc: Blocked By:
Blocking: #1459


The legacy layer relies on pixel harmonizers to synchronize data. Another approach would be to wrap Img's (and CelImg's) as IJ1 data structures (such as a new kind of ImagePlus, etc.). This code already exists in Imglib world. Also we would add imglib layer to wrap IJ1 ImagePluses (with vstacks or not) to sorts of Imgs. The legacy layer would just wrap things and pass them to IJ1. On return we may unwrap. This would simplify the harmonization code.

Change History

comment:1 Changed 2013-09-25T15:04:23-05:00 by bdezonia

Note that any ImagePlus we implement would have to support getProcessor() and getStack().getProcessor() such that they return the types of processors already known to IJ1. IJ1 has made the setf()/getf() (and all similar) methods final making them impossible to override.

comment:2 Changed 2014-05-02T21:19:31-05:00 by curtis

  • Status changed from new to closed
  • Resolution set to moved