After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 333562 - Add a text-based workflow recorder
Add a text-based workflow recorder
Status: RESOLVED DUPLICATE of bug 51937
Product: GIMP
Classification: Other
Component: General
2.2.x
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-06 03:38 UTC by vabijou
Modified: 2008-01-15 13:05 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description vabijou 2006-03-06 03:38:19 UTC
The Undo History periodically purges itself (based on the amount of memory you 
have set up, I suppose).  It would be nice, though, if GIMP recorded and saved 
the workflow steps that were used as a retrievable text report.  No image data 
would be saved, but notes that layers were added, tools were used (with their 
settings noted and on which layer they were used), filters and script-fus that 
were run are noted (again, settings, layers, etc.).  Basically, one would be 
able to review this log and get a good idea of what was done to the image.  
This log should be stored with the file for as long as desired by the user.  
Enough smarts to know that a visibility on and then immediately off, or 
something that is done and then immediately undone, accomplished nothing 
material and are not worth recording would be nice as well.
Comment 1 Michael Schumacher 2006-03-06 13:02:40 UTC

*** This bug has been marked as a duplicate of 51937 ***
Comment 2 vabijou 2006-03-06 15:51:33 UTC
What I intended by submitting Bug 333562 was something different than a script recorder.  I assume the script recorder discussed in bug 51937 was geared toward generating macros that could be executed to perform an action.  I was just wanting a record of the actions that were performed, essentially a tool for logging workflow.  It may or may not be the same tool discussed in bug 51937, depending upon how bug 51937 is implemented.