Am 29.06.2012 13:17, schrieb Lucas B. Cohen:
On 2012.06.27 10:39, Camilo Polymeris wrote:
I thought we could add a command line similar to this:
rawstudio --input something.raw --output something_developed.jpeg
This would fire up rawstudio in a "one image" mode, [...] plus automatically
save
the developed file on exit. Shotwell could then integrate this file
into its pipeline, just like it does with something_modified.jpeg
files.
Out of curiosity, juut to see if any of my very basic development
knowledge has any real world use, how do you envision Shotwell would
"integrate this file into its pipeline" ? Would it react upon seeing the
Rawstudio child process returning 0, then try to import the produced
file living in what was the second parameter passed to rawstudio
(something_developed.jpeg), which I imagine would have to be an absolute
path ?
I would imagine it as you described. Only that we could check after the
exit of Rawstudio whether the output file exists. If yes we import it as
a developed version of the photo, if no we do nothing. Also other photo
management software does it like that.
By the way: The raw developer software UFRaw [1] already supports this
process. You can specify commandline arguments to where the developed
file should be saved, e.g. "ufraw --out-type=jpeg --compression=90
--output=something_developed.jpg something.raw". Then, the software
opens, lets you edit the photo and writes the jpeg.
Regards,
Fabian
[1] http://ufraw.sourceforge.net/
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
