On Wed, Jun 27, 2012 at 2:22 PM, Eric Gregory <[email protected]> wrote: > On Wed, Jun 27, 2012 at 1:39 AM, Camilo Polymeris <[email protected]> > wrote: > >> >> 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? > > > Yes, that would be perfect! When we implemented the multiple RAW > development feature a while ago, we had this exact scenario in mind. > Unfortunately none of the RAW developer apps had the ability to operate in a > "client mode" like this at the time. > > If you could get this added to Rawstudio, we'd be very interested in > adapting Shotwell to support the feature. It would go a long way towards > making life better for those of us who shoot RAW photos.
Great. Let's see what the rawstudio devs say. In the meanwhile I have written a patch[1,2] for rawstudio that provides this "client mode" functionality. It probably still is less than optimal, but it is a start. Camilo [1]http://bugzilla.rawstudio.org/show_bug.cgi?id=556 [2]http://bugzilla.rawstudio.org/attachment.cgi?id=112&action=view _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
