Ticket #1011 (closed feature: fixed)
Opened 2012-02-24T13:15:18-06:00
Last modified 2014-08-20T12:09:34-05:00
Robust ImageJ1 legacy layer
| Reported by: | curtis | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | blocker | Milestone: | imagej-2.0.0 |
| Component: | Legacy Compatibility | Version: | |
| Severity: | critical | Keywords: | |
| Cc: | Blocked By: | #301, #509, #528, #530, #531, #532, #537, #546, #549, #552, #559, #573, #578, #647, #652, #693, #740, #751, #756, #757, #758, #761, #766, #773, #833, #842, #843, #868, #870, #905, #906, #908, #909, #964, #1259, #1354, #1471 | |
| Blocking: | #1010 |
Description
Our primary strategy for interoperability between ImageJ1 and ImageJ2 is a "legacy layer" that translates data structures between IJ1 and IJ2 on the fly. In this way, we can execute IJ1 plugins, macros and scripts on IJ2 data by first translating it into IJ1 format, executing the code, then translating the results back to IJ2. All of this happens transparently, with an ImageJ1 instance running "under the hood" of ImageJ2.
Change History
comment:40 Changed 2014-08-20T12:09:34-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
All constituent tickets resolved or moved.