>Turgut, > >sadly, I don't think this sort of workflow is going to work well with >Shotwell today. The problem is that there's really no easy way to sync i>nformation (and photos) between two Shotwell databases. A major future >goal for Shotwell is to make this kind of workflow reasonable, but we're >not there yet. See > >http://redmine.yorba.org/issues/1292 > >adam
Hi Adam, Thanks for your comment and the pointer. Of course, that type of syncronization would be ideal. In the meantime, I am willing to continue work on the premise that changes happen only on one computer at a time. If I change things in both computers then I need to lose the changes made in one. This was my work-flow with the behaviour that f-spot had which was to simply ignore the missing photos. The 'mark missing photos" type of behaviour was enabled by extensions (I think, I never used it). It seems to me that shotwell also would not crash if missing photos are not market out or updated, so I wonder if it is possible to "opt out" from the time spent looking for and marking up the missing photos. A simple configuration switch may be? Am I making sense? Thanks, Turgut _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
