Bug #3999
closed
WRP - create event-driven states for Kepler
Added by ben leinfelder over 15 years ago.
Updated over 15 years ago.
Description
This is probably more general than the "reporting" module, but I am putting it here because this has the most immediate need.
While the primary focus will be GUI events like selecting a workflow execution in the WRM interface and having that show the model as it existed when the workflow ran, we should also think about it in terms of triggering actions after certain conditions are met (automatically generating a report after the workflow has been executed). We may also wish to use this mechanism for some of the automated archiving and publishing to the remote (metacat-based) repository when the time comes.
Bottom line: tabs/views need to be alerted of certain events so that they can react appropriately to those events.
Looking at taking work done in the Morpho project that deals with tracking application events and state changes and broadcasting them to listeners.
Re-targeting to 2.0.0 because we'll need it for the WRM/WRP/Reporting modules to "talk to each other"
Added Morpho-based "event-state" module to be use for communicating between tabs/views.
Likely need modifications to the tabbing interface to make full use of this - right now it's pretty arcane to get tabs talking to each other in a "generic way".
Still not entirely clear how central/extensible we want the various events and states will be.
There's a base StateChangeEvent that can be extended by other modules...that's a starting place.
using this to update the Report Viewer when the view is selected. Also alerts the Report View TOC of a report instance change.
We may end up using it to tie in some of the Report Layout events (editing properties).
Original Bugzilla ID was 3999
Also available in: Atom
PDF