Ticket #1016 (closed feature: fixed)
Opened 2012-02-24T15:08:21-06:00
Last modified 2014-08-20T12:34:58-05:00
Ensure all ImageJ1 functionality is available in ImageJ2
| Reported by: | curtis | Owned by: | curtis |
|---|---|---|---|
| Priority: | blocker | Milestone: | imagej-2.0.0 |
| Component: | Core | Version: | |
| Severity: | critical | Keywords: | |
| Cc: | Blocked By: | #983, #1010, #1091, #1354, #1430 | |
| Blocking: |
Description
At minimum, ImageJ2 must be able to do everything ImageJ1 can do. Of course, ImageJ2 has many new capabilities, but it must be possible to accomplish the same tasks you can already do in ImageJ1. Otherwise, it is not feasible for users to completely switch to ImageJ2.
Change History
comment:5 Changed 2014-08-20T12:34:58-05:00 by curtis
- Status changed from new to closed
- Resolution set to fixed
The ImageJ2 vision continues to be to expand the paradigm of ImageJ 1.x into new territory, such as N-dimensional image processing, with a much greater emphasis on reusability, modularity and interoperability. However, it has become clear that recapitulating all ImageJ 1.x commands verbatim is not the way to go. Rather, we are creating new frameworks such as ImageJ OPS which seek to provide image processing capabilities beyond what ImageJ 1.x can do, while not being restricted to ImageJ 1.x's specific technical design or user interface.
So the UI and functionality of ImageJ2 will diverge more from ImageJ 1.x than we had originally planned, but with the continued goal of a software application—and set of libraries—that deliver everything ImageJ 1.x can provide, and much more.