Re: [Gimp-developer] GIMP 2.8 Feature Request (2)
- From: Alexia Death <alexiadeath gmail com>
- To: Jay Smith <jay jaysmith com>
- Cc: gimp-developer-list gnome org
- Subject: Re: [Gimp-developer] GIMP 2.8 Feature Request (2)
- Date: Wed, 4 Jan 2012 17:50:37 +0200
On Wed, Jan 4, 2012 at 5:21 PM, Jay Smith <jay jaysmith com> wrote:
> Our workflow is: Using VueScan Professional (independent of Gimp) to scan a
> high volume of TIFF images. Open each image in Gimp to tweak color,
> sharpness, rotation, and crop to desired size. Save as TIFF and close.
> (Downline we use our own scripts and ImageMagick to batch create several
> sizes of JPEGs for web use; the TIFFs are also used for print output and are
> archived as TIFFs.)
Along broad lines this workflow is or should be just as supported with
export as it is with save, just the command you invoke is slightly
different. There's one nag I wish was fixed with export. It should
default to input format for imported files. It's buggersome annoying
that it defaults to png.
> If this process is going to be made a lot more complicated for workflows
> like ours, then I hope that there will eventually be an optional mechanism
> to override the save/export process based on input and output file formats.
A) it wont be. You can just map Ctrl-s to export, if you dont need to
save XCF-s and nothing wil change for you.
b) This mechanism already exists. If you save with same parameters all
the time write/find a plugin that invokes the save with all the
parameters already set. You can just prompt for filename and even
manage folders automatically and save without any hassle. If you
havent done any scripting but have done programming, it shoudnt take
you more than 8 hours to churn out first version, less if you find a
good starting sample from google first.
] [Thread Prev