RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

operation logging

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
operation logging Tim Chen 10 Nov 06:27
  operation logging Martin Nordholts 10 Nov 08:31
Tim Chen
2009-11-10 06:27:32 UTC (over 15 years ago)

operation logging

Hi all,

I am trying to build an instrumented gimp that can record user operation sequentially for further analysis, similar to the command recorder in this project "http://vis.berkeley.edu/papers/tutgen/"

At first, I tried digging around the code at "http://www.ingimp.org" , but it seems like that they are actually trying to prevent collecting such fine grained data to preserve user privacy.

Than I come across this feature requirement " https://bugzilla.gnome.org/show_bug.cgi?id=51937" about script recording.

So, I was wondering

1. What's the current progress about script recording? is there any API for such function atm?

2. If not, can someone point me the correct direction, like which module to look at, for hacking the GIMP code?

Thanks a lot! -Tim

Martin Nordholts
2009-11-10 08:31:41 UTC (over 15 years ago)

operation logging

On 11/10/2009 06:27 AM, Tim Chen wrote:

Than I come across this feature requirement "https://bugzilla.gnome.org/show_bug.cgi?id=51937" about script recording.

So, I was wondering

1. What's the current progress about script recording? is there any API for such function atm?

Exactly how to introduce script recording is a highly debated topic. Some wants it to be a layer on top of app/core, some wants it to be inside app/core. There is no API in place. A good first step would be to get something that works and work from there.

I've uploaded my postponed attempt to with the following commits: http://www.chromecode.com/gimp/gimp-undo-rewrite-2009-11-10_0825.tar.gz

Tue Sep 1 21:41:31 2009 +0200 app: Integrate GimpCommandGroup into undo mechanism Tue Sep 1 19:12:17 2009 +0200
app: Add GimpImageCommand and implement for resolution and undo Tue Sep 1 19:04:35 2009 +0200
app: Update GimpCommand
Tue Sep 1 08:32:08 2009 +0200
app: Update GimpCommand
Sun Aug 30 23:11:13 2009 +0200
app: Add GimpCommandGroup
Sun Aug 30 22:09:13 2009 +0200
app: Update GimpCommand
Sun Aug 30 20:17:15 2009 +0200
app: Add and use GimpLutCommand
Sun Aug 30 19:01:55 2009 +0200
app: Fix GimpCommand
Sun Aug 30 15:10:58 2009 +0200
app: Add GimpImage infrastructure for new undo system Sun Aug 30 15:09:36 2009 +0200
app: Add GimpUndoTree
Sun Aug 30 10:44:02 2009 +0200
app: Add menu items for macro recording Sun Aug 30 11:40:44 2009 +0200
app: Improve brush outline for fuzzy brushes Sat Aug 29 19:24:36 2009 +0200
app: Add GimpCommand

2. If not, can someone point me the correct direction, like which module to look at, for hacking the GIMP code?

Explore the directories under http://git.gnome.org/cgit/gimp/tree/app and also see http://git.gnome.org/cgit/gimp/tree/devel-docs/structure.xml

Regards, Martin