Ticket #10 (assigned feature)

Opened 9 years ago

Last modified 7 years ago

Maintain strict separation of concerns (i.e., UI independence)

Reported by: curtis Owned by: curtis
Priority: blocker Milestone: imagej-2.0.0
Component: Core Version:
Severity: serious Keywords:
Cc: Blocked By: #138, #190, #214, #579, #860, #884, #911, #995
Blocking:

Description (last modified by curtis) (diff)

Currently, ImageJ has several design issues that impact any possibility of running it without a GUI in a headless environment:

  • Commands are tied to specific AWT menu items
  • The macro system is tied to the AWT-driven GenericDialog
  • The code was generally designed assuming AWT GUI elements are available

We want to separate ImageJ into a (headless) library layer that performs image processing without a GUI, and one or more graphical layers that provide user interaction and call into the library to perform tasks.

As part of this task, we are exploring strategies to organize this separation, such as a  Model-View-Controller (MVC) architecture. There are various MVC frameworks available such as  Struts and  Spring, though they are generally targeted toward web applications rather than desktop ones. We plan to examine these, though it is equally likely we will avoid dependencies on third-party libraries in favor of a simpler design.

For relevant discussion, see the " Separation of concerns (MVC, AWT/Swing/etc.)" thread on the ImageJX discussion group.

Change History

comment:1 Changed 9 years ago by curtis

According to its author,  Endrov has a strict separation of concerns. And  Bio7 is built using the  Eclipse Rich Client Platform.

comment:2 Changed 9 years ago by curtis

  • Description modified (diff)

comment:3 Changed 9 years ago by gharris

  • Status changed from new to accepted

comment:4 Changed 8 years ago by curtis

  • Status changed from accepted to closed
  • Resolution set to fixed

Our current approach is to use SezPoz for dependency injection, with a GUI-independent plugin/module/tool interface hierarchy. Depending on the execution context (in a GUI, headless from a console, etc.) the mechanism for plugin and module execution will change. It looks unlikely at this time that we will need to rely on any formal MVC framework.

comment:5 Changed 7 years ago by curtis

  • Type changed from task to story

comment:6 Changed 7 years ago by curtis

  • Blocking 6 added

comment:6 Changed 7 years ago by curtis

  • Summary changed from Explore MVC frameworks for separation of concerns to Maintain strict separation of concerns (i.e., UI independence)

comment:7 Changed 7 years ago by curtis

  • Blocked By 138 added

comment:8 Changed 7 years ago by curtis

  • Blocked By 190 added

comment:9 Changed 7 years ago by curtis

  • Blocked By 214 added

comment:10 Changed 7 years ago by curtis

  • Blocked By 995 added

comment:7 Changed 7 years ago by curtis

  • Status changed from closed to reopened
  • Resolution fixed deleted
  • Milestone changed from imagej-2.0-alpha1 to imagej-2.0-final

comment:8 Changed 7 years ago by curtis

  • Owner changed from gharris to curtis
  • Status changed from reopened to assigned

comment:9 Changed 7 years ago by curtis

  • Blocked By 860 added

comment:10 Changed 7 years ago by curtis

  • Blocked By 911 added

comment:11 Changed 7 years ago by curtis

  • Blocked By 660 added

comment:12 Changed 7 years ago by curtis

  • Blocked By 579 added

comment:13 Changed 7 years ago by curtis

  • Blocked By 660 removed

comment:14 Changed 7 years ago by curtis

  • Blocked By 884 added

comment:15 Changed 7 years ago by curtis

  • Blocking 6 removed
Note: See TracTickets for help on using tickets.