Juergen Weber wrote:

I always was missing to batch-(B&W convert | sharpen | resize) images via the GUI.

[...]

So you could try out your image manipulations on the GUI and then copy the commands from the trace it to scripts.

Is that already possible? Or is there a better way to create batches?

Try David's Batch Processor:

http://members.ozemail.com.au/~hodsond/dbp.html

Juergen Weber wrote:

Programming scripts would still be easier if Gimp would trace to stdout what the user is doing on the GUI, i.e. it should print out the script-fu commands that correspont to the interactive actions.

So you could try out your image manipulations on the GUI and then copy the commands from the trace it to scripts.

Is that already possible? Or is there a better way to create batches?

That isn't possible at this time. What you are asking for is along the lines of what is asked for in GIMP bug #51937.

See http://bugzilla.gnome.org/show_bug.cgi?id=51937

Juergen Weber wrote:

As I understand the page, DBP offers a fixed set of processing option whereas a script recorder should apply any operation on a set of images, e.g. apply "Converting Color Images to B&W using Channel Mixer in The GIMP" (http://www.gimpguru.org/Tutorials/ChannelMixer/) to lots of images.

Yes, that's right. However, you did specifically mention conversion to B&W, sharpening, and resizing; and trying out the manipulations on a test image before applying them to the batch. DBP does all of those.

As Kevin pointed out, it's not currently possible to record an arbitrary set of commands given to Gimp. DBP tries to provide some of the most common operations.

Juergen Weber wrote:

Tracing the commands would be a light variant of this. Outputting a trace should not be more than some log statements, would it?

And http://bugzilla.gnome.org/show_bug.cgi?id=51937#c25 allready has my suggestion.

Anyway, a pity that the bug has been opened in 2001 and still no Script recorder in Gimp core.

The comments in the bug report explain why it is not an easy thing to do and why it hasn't been done before now. Comment #26 and #27 mention the difficulties of implementing this feature.

That isn't possible at this time. What you are asking for is along the lines of what is asked for in GIMP bug #51937.

See http://bugzilla.gnome.org/show_bug.cgi?id=51937

Which was posted in '01. Perhaps it's time to revisit this request?

___

Greg wrote:

That isn't possible at this time. What you are asking for is along the lines of what is asked for in GIMP bug #51937.

See http://bugzilla.gnome.org/show_bug.cgi?id=51937

Which was posted in '01. Perhaps it's time to revisit this request?

Reading the comments would be a good start if you want to give it a try. They'll give you an idea of the difficulties that you'll encounter.

HTH, Michael

On Sat, Nov 10, 2007 at 06:17:25PM +0100, Juergen Weber wrote:

On Nov 9, 2007 12:05 AM, Michael Schumacher wrote:

Greg wrote:

That isn't possible at this time. What you are asking for is along the lines of what is asked for in GIMP bug #51937.

See http://bugzilla.gnome.org/show_bug.cgi?id=51937

Which was posted in '01. Perhaps it's time to revisit this request?

Reading the comments would be a good start if you want to give it a try. They'll give you an idea of the difficulties that you'll encounter.

Well, in http://bugzilla.gnome.org/show_bug.cgi?id=51937#c14 Rapha?l Quinet says, he allready was working on the feature, whereas in http://bugzilla.gnome.org/show_bug.cgi?id=51937#c6 Hans Breuer appended some code.

So the situation doesn't seem so bleak, does it?

If you have this great concept of a script-callable api, it seems tantalizingly close to use the api from a script recorder, too.

How is that close? The UI has to be refactored to use that API as well, which is 80% of the work. It's a large job, and none of the code in bug even touches upon that. You also have to solve the problem of translating tool mouse movements into API calls efficiently.

It's pretty rude to imply that something is easy when you haven't even taken the time to actually think through how much work is involved.

-Yosh