Re: [UFRaw-Devel] Per-image configuration files for the Gimp plug-in

[kevin g. <km...@bi...>]

I've been using my patch now for a few weeks and, regardless of it's 
official acceptance, I'll continue to apply it in future releases. That's 
how much I want it. It greatly simplifies the workflow if I have to go 
back to the original RAW image.

I realise that the patch in it's current form leaves a lot to be desired 
from a technical POV - I only developed it to a proof-of-concept stage. 
But, as noted above, even in it's current form it is now a permanent part 
of my software stack.

I also realise that others may not want to have this facility, so it would 
make sense to have it as a configurable option.

If it is accepted for inclusion in the official release, I am happy to 
continue development of the patch if given a little guidance as to what is 
required.

Cheers,
Kev

On Mon June 20 2011 18:39:29 Tomasz Golinski opined:
> > I think that most users would not expect UFRaw to behave this way.
> > First, per image data is not expected to be saved when you load an
> > image. Second, writing to the folder with the raw file might not be
> > desirable. In the better case this folder would be read-only, in the
> > worst case UFRaw would write to a folder that the user did not want to
> > change.
> 
> For my workflow that possibility would be handy. If this behaviour would
> be configurable (and tunable), there would be no harm in adding this
> functionality. I even asked you some time ago about something like this.
> 
> Best
> Tomasz.
> 
> 
---------------------------------------------------------------------------
> --- EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> ufraw-devel mailing list
> ufr...@li...
> https://lists.sourceforge.net/lists/listinfo/ufraw-devel