On Wed, Jun 27, 2012 at 12:18 PM, Lucas B. Cohen <[email protected]> wrote: > Dear Camilo, dear list, >[...] > I find both your stance and your experience interesting.
Thanks, but the later is rather limited. In particular regarding to the shotwell photo pipeline. > I've been experimenting with RAW image development for a little while, > and what I'm beginning to imagine is that it would be useful to have the > possibility of assigning more than one developed versions of a picture > to a single raw master, in an explicit manner, inside Shotwell. Yes! I would very much like this to be a feature of Shotwell, too. Question is: is this enough on its own or should it be complementary with the approach I was suggesting? I suspect, while more versatile, specially for the advanced user, your idea is harder to implement. It all depends on how ingrained the "1-raw-for-1-image" relationship is in the internals of shotwell. Both in the pipeline as in the UI. > Rationale : sometimes I can be equally satisfied with two different > development results ; or would like to be able to quickly switch between > candidates to a final result, inside Shotwell, where I already have an > established pattern of skimming through multiple shots of a single > subject with a single framing to select my favorite one, then reject and > later delete all the others. Yep. As you know, rawstudio calls these "snapshots", and even though they allow only 3, they make life much easier (if only they stored crops!). If the idea I suggested works, you could open rawstudio to switch snapshots and the selected one would be passed back to shotwell. Not as practical as having the feature right inside shotwell, but a workaround until this is implemented, too. Thanks for your comments. Regards, Camilo _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
