Ticket #338 (closed enhancement: fixed)
Opened 2011-02-14T18:40:58-06:00
Last modified 2012-03-05T14:45:34-06:00
Work with Curtis on Plugin/Module IJ2 interfaces
| Reported by: | aivar | Owned by: | aivar |
|---|---|---|---|
| Priority: | minor | Milestone: |
|
| Component: | Plugin Framework | Version: | |
| Severity: | major | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | #1054 |
Description
Create an intermediate interface for IJ2 modules that provides lists of inputs and outputs. In the case of plugins these inputs and outputs will be designated through plugin annotations. They should also be able to be supplied programmatically for other kinds of plugin modules.
Change History
comment:2 Changed 2011-03-14T18:40:18-05:00 by aivar
- Milestone changed from biweekly-2011: Feb-28 to Mar-11 to imagej-2.0-beta1
comment:3 Changed 2011-07-15T12:26:03-05:00 by curtis
Big progress on this in a9404d5a77e38b315f7c931841e4c1eaeb5e6ca0. Much of the IJ2 infrastructure is now module-based rather than plugin-based. For example, the menu system is all keyed to modules now, rather than only plugins. So in theory it should be possible to code custom modules (i.e., implementing imagej.module.Module directly, and not discoverable plugins), add them to the menus manually, and have them launch the same way, including pre- and post-processing.
The workflow logic in source:trunk/extra/workflow is still not integrated though.
comment:4 Changed 2011-07-27T15:11:16-05:00 by curtis
- Milestone changed from imagej-2.0-beta1 to imagej-2.0-alpha5
comment:5 Changed 2011-10-10T09:49:58-05:00 by curtis
- Status changed from accepted to closed
- Resolution set to fixed
The module interfaces are pretty well fleshed out in the ij-ext project now. The only thing missing is the workflow code, which could live in a new imagej.ext.workflow package. This is a lower priority; see ticket #806 for details.