Ken Warner wrote:
> May I suggest that your batch processor should itself
> be programable. That is, you should be able to specify
> which scripts or plugins to run in which order and with
> arguments for each to control their actions.
>
> It's a lot of work but I know it's doable.
>
> Limiting your batch processor to a small set of available
> actions will only serve a very small number of people.
>
> Evan Kroske wrote:
>> Hello GIMP users,
>> I'm going to be developing a batch image processor plugin for
>> GIMP, and I'd like to know which functions should be the first on my
>> list. Obviously, scaling is the first priority, because I use that to
>> optimize pictures for my websites. However, past that, I'm not sure
>> which functions are the most used. Should I add ...
>> ... cropping?
>> ... layer management? (eg. adding a layer with a signature to a whole
>> bunch of pictures)
>> ... filters?
>> ... color management?
>> ... or something else?
>> I would like to add all of those functions, but I will probably only
>> get two or three of these actions enabled. What are the most
>> important functions for you?
>>
>> Regards,
>> Evan Kroske
>> Future GSoCer (hopefully)
>> _______________________________________________
>> Gimp-user mailing list
>> Gimp-user@lists.XCF.Berkeley.EDU
>> https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
>>
>
That will certainly be my goal, but I still expect to find some hiccups
or interface inconsistencies. If I'm lucky, I won't need this list, but
if not, I want to know the most important batch functions for me to add.
In fact, my goal is to create a plugin that scans the undo history for
the current image and allows you to apply those changes to a whole bunch
of images. Now that would be slick.
_______________________________________________
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
