Ticket #14 (closed feature: fixed)
Opened 2010-02-16T21:17:18-06:00
Last modified 2012-02-23T11:10:43-06:00
Better event notifications
| Reported by: | curtis | Owned by: | gharris |
|---|---|---|---|
| Priority: | major | Milestone: |
|
| Component: | Core | Version: | |
| Severity: | non-issue | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description
ImageJ provides hooks to external software to listen for various types of events: CommandListener, DialogListener, IJEventListener and ImageListener. These are useful, but do not completely encompass the operations that third party applications may be interested in monitoring. Further, the current mechanism blends events corresponding to the underlying image data with those relating to the GUI (e.g., CommandListener is AWT menu-based—see the related ticket on separation of concerns).
We would like to flesh out ImageJ's event notification system to notify listeners of any specific operation performed on image data or otherwise. If comprehensive enough, these events could form the basis for a command history needed for better undo/redo support as well being useful as part of a better scripting infrastructure.
Change History
comment:1 Changed 2010-02-16T21:20:09-06:00 by curtis
comment:3 Changed 2010-11-15T10:38:11-06:00 by gharris
- Status changed from accepted to closed
- Resolution set to fixed
We will use a publish/subscribe EventBus based on NetBeans Lookup.
See: imagejdev:branches/ijx/imagej/src/main/java/ijx/event/
This is based on http://netbeans.dzone.com/news/publish-subscribe-netbeans-pla
One technology to consider when developing an event-driven framework might be the Guice-driven GUTS library, specifically its Event Bus.