Ticket #1019 (closed feature: wontfix)
Opened 2012-02-26T22:02:31-06:00
Last modified 2014-08-20T12:24:04-05:00
Reimplement IJ1 features that the legacy layer cannot support
| Reported by: | curtis | Owned by: | bdezonia |
|---|---|---|---|
| Priority: | critical | Milestone: | imagej-2.0.0 |
| Component: | Plugins | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | #1171, #1172, #1366, #1456 | |
| Blocking: | #1010 |
Description
For a variety of reasons, IJ has some functions that cannot be supported via the legacy layer. In particular, highly UI-interactive plugins (such as the Shadows Demo; see ticket #647) may be infeasible to support. Fortunately, these sorts of plugins are also unlikely to be part of automated macro and script workflows. So we should be able to provide backwards compatibility by reimplementing them in the IJ2 framework instead.
Change History
comment:11 Changed 2012-03-05T11:01:19-06:00 by curtis
- Blocked By 756 added
(In #756) Due to restrictions in the legacy layer, the solution is to implement a pure IJ2 version of Threshold.
comment:26 Changed 2012-09-06T16:15:51-05:00 by bdezonia
- Blocked By 1456 added
(In #1456) Some IJ1 plugins cannot be fully supported by our legacy layer data translation approach. Rewrite such (usually gui enhanced) plugins as pure IJ2 implementations.
See blocked ticket #1010 for further description
comment:27 Changed 2014-08-20T12:24:04-05:00 by curtis
- Status changed from new to closed
- Resolution set to wontfix
As I wrote in ticket #1456:
We are no longer supporting use of ImageJ 1.x commands from modern ImageJ2 UIs. These plugins work fine in the legacy ImageJ 1.x UI, and adding them to ImageJ2 is not urgent.
Of course, we would love to have all of this functionality available as "pure IJ2" commands, so that they are usable headless and from the variety of contexts IJ2 makes possible: e.g., CellProfiler, OMERO and KNIME. But in practice, most of these commands are interactive in some way and will need to be reconsidered and recast into the headless paradigm (i.e., parameterized inputs and outputs). We will tackle this work on an as-needed basis, with help from the community over a course of years. But first the ImageJ2 core needs further stabilization. So the goal of porting IJ1 plugins to IJ2 is, in general, on pause for the time being.
Also worth noting that in many (most?) cases, we will want to make image processing functionality available as ImageJ OPS Op plugins, rather than vanilla SJC Commands, to maximize their usability and interoperability.