On Fri, Jun 29, 2012 at 7:08 AM, Lucas B. Cohen <[email protected]> wrote: > OTOH, in my personal case, it would be enough in the sense that it would > bring me something new, as opposed to a comfort improvement to something > I can already achieve in a much less elegant way at the moment (I resort > to importing developed images back into shotwell, alongside the original > ones taken from my camera, by re-importing Shotwell's photo import folder) > > So I guess it depends who you ask.
Of course. >> 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. > > It's quite probably a more costly idea, yes. I've tried to make a > suggestion that is as simple as I can imagine in terms of UI (extra > nodes in the side pane) and in terms of automation (none) in the issue > where it's been discussed [1], but I'm aware it means I like both your proposal and also Bruno's suggestion[2] you linked in a previous post. While ticket #9020 deals more with grouping "physical images" (different developments of 1 raw or diferent source jpegs), Bruno's is more about having various "virtual images" (sets of changes stored in the database). I am not sure if both issues can be treated as one, and presented transparently to the user as such, or if they are fundamentally different problems. [1 raw] -> N jpegs -> M virtual images > How deep-trenched is the 1-to-1 relationship between raw master and > developed image, was pretty much what I was wondering when I asked > "Would it be breaking important fundamental assumptions about data > structures [...] ?" in my previous message. I must confess to not having > your coding skills, and never having looked at the Shotwell sources, so > I don't have any kind of concrete answer. Neither do I. But discussing this matter has helped me a lot to get a clearer picture of the problem. And the code is out there, for all of us to delve into. As soon as I get a little time (been a bit busy with other projects), and if you or the shotwell devs don't beat me to it, I'll see what can be done. Regards & thanks for your help, Camilo [2] http://redmine.yorba.org/issues/2474 _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
