Ticket #1010 (closed feature: fixed)
Opened 2012-02-24T12:58:41-06:00
Last modified 2014-08-20T12:28:27-05:00
Full backwards compatibility with ImageJ1
Reported by: | curtis | Owned by: | bdezonia |
---|---|---|---|
Priority: | blocker | Milestone: | imagej-2.0.0 |
Component: | Legacy Compatibility | Version: | |
Severity: | critical | Keywords: | |
Cc: | Blocked By: | #207, #795, #852, #878, #891, #897, #1011, #1014, #1019, #1254, #1354 | |
Blocking: | #1016 |
Description
ImageJ2 must be backwards compatible with ImageJ1, able to run existing plugins, macros and scripts with no changes. See blocking tickets for details.
Change History
comment:40 Changed 2012-02-26T20:14:55-06:00 by curtis
- Milestone changed from imagej-2.0-beta1 to imagej-2.0-final
comment:49 Changed 2014-08-20T12:28:27-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
We have accomplished this goal by creating a legacy ImageJ 1.x user interface plugin for ImageJ2. All ImageJ 1.x functionality is accessible when running with this "legacy UI" active. When running with any other UI, ImageJ 1.x functionality is not available, except at the library level (i.e., you can call ij.* classes yourself, as needed, though it is ultimately not recommended for "future-proof" projects to do so).