Our event service allows recording a history that is not only linear, one that can represented in a tree structure (recording input/output relationships between images).
We should totally make a nice UI for that which can also double as a more powerful version of the macro interpreter: rather than having to start the macro recorder before performing image processing, the history should be recorded (with a configurable cut-off size), and the user should be offered a user interface to inspect the history and create scripts/macros/plugins from part of the history.
Our event service allows recording a history that is not only linear, one that can represented in a tree structure (recording input/output relationships between images).
We should totally make a nice UI for that which can also double as a more powerful version of the macro interpreter: rather than having to start the macro recorder before performing image processing, the history should be recorded (with a configurable cut-off size), and the user should be offered a user interface to inspect the history and create scripts/macros/plugins from part of the history.
Migrated-From: http://trac.imagej.net/ticket/1797