Hi,
On Thu, 2006-07-13 at 08:47 -0500, Kent Tenney wrote:
> Does that require writing c code or can it be scripted?
It requires writing C code, but anyone can learn C in a day or two.
Sven
___
Gimp-user mailing list
Gimp-user@lists.XCF.Berkeley.EDU
On 7/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am not following your use of "immutable" (it seems to contradict the
statements in parentheses). Perhaps you could clarify that part.
I mean that I do not want to make any changes to the image as
it came from the camera/scanner, as doin
On 7/12/06, Sven Neumann <[EMAIL PROTECTED]> wrote:
Hi,
On Wed, 2006-07-12 at 08:43 -0500, Kent Tenney wrote:
> A good start in this direction would be if I could automatically
> save curves and levels files when applying these edits. I could
> then script associating the color transforms with
Hi,
On Wed, 2006-07-12 at 08:43 -0500, Kent Tenney wrote:
> A good start in this direction would be if I could automatically
> save curves and levels files when applying these edits. I could
> then script associating the color transforms with the image.
Feel free to contribute PDB functions that
On Wed, Jul 12, 2006 at 08:43:35AM -0500, Kent Tenney wrote:
>
> A good start in this direction would be if I could automatically
> save curves and levels files when applying these edits. I could
> then script associating the color transforms with the image.
>
> Questions:
> Is it possible to scr
I am not following your use of "immutable" (it seems to contradict the
statements in parentheses). Perhaps you could clarify that part.
Also, I would caution that in GIMP parlance, the term "resize"
generally refers to changing the canvas size of the image (without
affecting the pixel data
Howdy,
I am interested in implementing a workflow capability
to Gimp based on the following principles;
- the original file is immutable. (any edits of it lose information)
- the destination file is immutable. (assuming that lossy compression
is used, (usually the case))
This implies that tha