Ticket #80 (closed feature: fixed)

Opened 9 years ago

Last modified 7 years ago

Action/Command Architecture Explorations

Reported by: gharris Owned by: gharris
Priority: major Milestone: imagej-2.0-alpha1
Component: UI Framework Version:
Severity: non-issue Keywords:
Cc: Blocked By:
Blocking:

Description (last modified by gharris) (diff)

Related to tickets MVC, Undo , & I18N

See research and references at:  Actions and Commands

Change History

comment:1 Changed 9 years ago by gharris

  • Description modified (diff)

comment:2 Changed 9 years ago by gharris

  • Owner set to gharris
  • Status changed from new to assigned

comment:3 Changed 9 years ago by gharris

  • Status changed from assigned to accepted
  • Component changed from analysis to gui

comment:4 Changed 9 years ago by gharris

  • Description modified (diff)

comment:5 Changed 9 years ago by gharris

  • Description modified (diff)

comment:6 Changed 9 years ago by gharris

  • Type changed from defect to task
  • Severity changed from serious to non-issue

comment:7 Changed 9 years ago by gharris

  • Milestone changed from biweekly-2010: Jun-14 to Jun-25 to biweekly-2010: Jun-28 to Jul-09

comment:8 Changed 9 years ago by gharris

  • Milestone changed from biweekly-2010: Jun-28 to Jul-09 to imagej-2.0-beta

comment:9 Changed 9 years ago 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.

comment:10 Changed 7 years ago by curtis

  • Type changed from task to feature
Note: See TracTickets for help on using tickets.