I am Shotwell and Rawstudio user and have submitted small patches to both projects. This combo, plus sometimes a bit of the GIMP, does everything I need. Only problem is the interaction between both programs: you have to manually specifiy were developed jpegs are stored, duplicate pictures show up, raw files are unlinked from jpegs, Shotwell gets confusing when you delete pictures from within Rawstudio, etc. While I played around with the idea of adding more features to Shotwell, to make it my only tool, I have come to the conclusion that it is better to keep that program simple but powerful. That is, leave the orgainzing and sharing to Shotwell, the developing to Rawstudio and the editing to the GIMP. As you probably know, the first and the last play very nice together: Shotwell makes a copy of the JPEG and calls GIMP to edit it. This edit is saved and transparently replaces the original image for all practical purposes.
So, how could Rawstudio (or similar programs) be brought into this workflow? Duplication of the original raw isn't very practical, so 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, that is remove every GUI element related to browsing, organization and sharing, including the filmstrip and some menu items, 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. What do you think? Is this approach feasible? Or am I missing something? C.f. http://redmine.yorba.org/issues/3061 The comments to this ticket suggest an alternative approach: leaving the decision on were to save the developed files to the user and then doing some filename and exif magic to link them to the RAWs. Regards, Camilo _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
