Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New legacy layer approach #3

Closed
ctrueden opened this Issue May 3, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@ctrueden
Copy link
Member

ctrueden commented May 3, 2014

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.

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.

Migrated-From: http://trac.imagej.net/ticket/1873

@hinerm hinerm added the duplicate label Mar 23, 2015

@hinerm

This comment has been minimized.

Copy link
Member

hinerm commented Mar 23, 2015

Covered by #86

@hinerm hinerm closed this Mar 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.