On Fri, Sep 25, 2009 at 10:54:02AM +0200, Frank van Maarseveen wrote: > > Using separate files makes it more transparent and simple, for both > implementation and user. This way .ufraw* files can be checked/modified > outside ufraw with standard tools and it's also easier to do so within > scripts.
I think if ufraw configuration is going to grow beyond a single file, it should move to a ~/.ufraw/ directory. I think it's impolite to clutter a user's home directory with multiple files. I don't like the idea of a fixed set of numbered presets, either. It should be possible to create as many as one wants, and to name them. This could be done quite tidily with <Preset name="foo"> sections in the .ufrawrc. These can then be restricted to only containing tags which relate to the image processing, and not more general configuration parameters such as e.g. SaveConfiguration, or any other such settings we might add in the future. Martin ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ ufraw-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ufraw-devel
