Ticket #80 (closed feature: fixed)
Opened 2010-06-01T15:27:17-05:00
Last modified 2012-02-23T13:07:37-06:00
Action/Command Architecture Explorations
| Reported by: | gharris | Owned by: | gharris |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | UI Framework | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description (last modified by gharris)
Related to tickets MVC, Undo , & I18N
See research and references at: Actions and Commands
Change History
comment:2 Changed 2010-06-01T16:37:26-05:00 by gharris
- Owner set to gharris
- Status changed from new to assigned
comment:3 Changed 2010-06-07T11:35:58-05:00 by gharris
- Status changed from assigned to accepted
- Component changed from analysis to gui
comment:6 Changed 2010-06-08T10:56:55-05:00 by gharris
- Type changed from defect to task
- Severity changed from serious to non-issue
comment:7 Changed 2010-06-29T10:11:04-05:00 by gharris
- Milestone changed from biweekly-2010: Jun-14 to Jun-25 to biweekly-2010: Jun-28 to Jul-09
comment:8 Changed 2010-06-29T13:19:36-05:00 by gharris
- Milestone changed from biweekly-2010: Jun-28 to Jul-09 to imagej-2.0-beta
comment:9 Changed 2011-02-16T13:39:23-06:00 by curtis
- Status changed from accepted to closed
- Resolution set to fixed
Technically, neither of the terms "action" nor "command" carry over directly to ImageJ2. The basic modular building block of ImageJ2 is the "module," with "plugins" and "scripts" being two forms of modules. A "tool" ties user input to a series of module executions.
In this way, all module executions will be able to be captured (using the postprocessing mechanism) and re-expressed as scripting commands.