Re: ufraw (and others) integration

[Ulf Rompe <Ulf Rompe icem com>]

Am Donnerstag, den 06.09.2007, 11:12 +0200 schrieb Stephane Delcroix:
> An update on the RAW status...
> 
> - since a few days, db supports versions of images with different
> extensions
> - I wrote an addin that'll help you fix your actual db by merging raw
> +jpeg files of the same image as only one image with versions. This
> will
> be available very soon via the 'Manage extensions' menu entry.
> - I wrote a patch for ufraw and it was accepted so f-spot can force
> the
> output file while converting to raw. I still have to write an addin so
> it "Develop in ufraw" appears in everyone's contextual menu.

Thanks a lot! It may seem pointless to post to a mailing list just to
say "thank you", but I believe you have just enlarged F-Spot's user base
a lot with this single mail. At least you finally got me into the boat. 

Right now I'm in the process of importing and sorting my whole image
base into F-Spot. It will be a lot of work since, lacking a good photo
organizer, my collection has become neglected over the years. But I've
been waiting for raw support in F-Spot since it first appeared on the
web site as the planned "first class raw support". This being a while
ago, you can imagine how happy I am now!

> - the code for reparenting an image as version of another dy drag'n
> drop is already in trunk, just not compiled yet (compile with
> -d:ENABLE_REPARENTING if you want to give it a try)

I will definitely check this out next week since I have lots of
derivative files with a revision number as part of the file name (see
http://exiflow.sf.net/ for the naming scheme) so your raw+jpeg merger
extension can't catch them. But with some manual reparenting (or maybe
my first reconnaissance of C# with a slight modification of your
extension) I will be able to keep my preprocessing chain as it is with
exiflow and then do everything I need with F-Spot.

Thank you SO MUCH for that!

[x] ulf 

-- 
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.