Why have a Recover Changes Tool? You have an object in the system that represents the changes. This object is the responsible party who has all the information we want and knows just what to do with it. Why don't we talk directly to it? Going through a tool is like passing each message through a secretary, who only knows what she's been told - which is not much - and who's information is rarely up to date.
Scenario: You start with something visual that represents the changes, like a picture of a scenography machine. Clicking it opens, say, a GT Inspector, but turbocharged. In addition to a custom presentation, you can operate through it just like any other object. So you go through a few panes paring down the list by e.g. selecting only changes for a particular class. Then, you kick in the turbo boost, select the items of interest from the last pane, and "go on selection" to open a new pane on just the items selected in the presenter (col species copy with). Now the custom actions that were formerly hosted by the tool are right there in the presenter, so you "file in" and go about your business. Ideally, the object, possible visualizations, and actions were meta-described well enough (a la Magritte) that one could build this feature in GT mostly by wiring
Why have a Recover Changes Tool? You have an object in the system that represents the changes. This object is the responsible party who has all the information we want and knows just what to do with it. Why don't we talk directly to it? Going through a tool is like passing each message through a secretary, who only knows what she's been told - which is not much - and who's information is rarely up to date.
Scenario: You start with something visual that represents the changes, like a picture of a scenography machine. Clicking it opens, say, a GT Inspector, but turbocharged. In addition to a custom presentation, you can operate through it just like any other object. So you go through a few panes paring down the list by e.g. selecting only changes for a particular class. Then, you kick in the turbo boost, select the items of interest from the last pane, and "go on selection" to open a new pane on just the items selected in the presenter (col species copy with). Now the custom actions that were formerly hosted by the tool are right there in the presenter, so you "file in" and go about your business. Ideally, the object, possible visualizations, and actions were meta-described well enough (a la Magritte) that one could build this feature in GT mostly by wiring