Hi Adam, Thanks again for all your responses and links. My comments are below:
> > This won't work since Shotwell is completely non-destructive: when you make > changes to a photo, Shotwell records the edits in its database (and reapplies > them every time you open a photo) but doesn't write to the original photo > file. And there's no way to propagate those edits from one database to the > other. So your second machine will have no way of seeing the changes made on > the first machine, unless you explicitly export all photos which you have > changed. > > > Thus, Shotwell's data model currently makes it hard to share edited photos > with other instances of Shotwell or other applications. This is a > significant > limitation, and we want to change this at some point, probably by keeping > more > information about edits in files. See > > http://redmine.yorba.org/issues/1798 > http://redmine.yorba.org/issues/1879 > Reading this, I am bit puzzled because I am copying the photos.db file between computers so I would imagine the changes would propagate. I was following the FAQ entry here: http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ#How-can-I-copy-my-Shotwell-library-to-a-new-computer I guess I am being unclear in my description, so I am editing my original one There are two computers: a- Main computer: - all photos are linked (by symbolic links) to folders in a folder "sync" e.g. in other words, there is a folder sync made of bunch of symbolic links that point to where the photos are - let's say the absolute path to this folder is /sync - .shotwell/data/photo.db is a symbolic link to /sync/photo.db b- A laptop computer with limited hard-drive space - it has /sync with the same symbolic links but most of them point to nowhere. - it has a sub-set of the photos that I am just working on or have just copied from various sources - /sync has symbolic links that point to that subset - .shotwell/data/photo.db is a symbolic link to /sync/photo.db - photo.db gets synced with that in the main computer (a) every night or as often as possible. (a) acts as the "Master" and (b) the "Slave". I only edit photos in one computer at a time and if by accident I edit them in both, (a) overwrites (b) by copying its photo.db over that of (b) At the end, both computers end up with the same photo.db but *without* merging , just simply overwriting. If I am patient enough to wait for the missing photos marking/unmarking process, it seems to work fine to me. Let me know if this makes sense and if this could be implemented with the feature I have requested. As a side note, I agree with some people in the mailing list and the links you mention above that this could be a preference to basically apply the changes a copy of the photos, keeping the originals intact. f-spot did it like this: P2118231 (Modified).JPG P2118231 (Modified (2)).JPG It is bit confusing if you then view your photos outside f-spot but one could get used to it. I have a peace of mind that if f-spot is non-functional then I still have all the changes I did to my photos in my files, I can easily e-mail, copy, distribute my photos without relying on f-spot, for example, in instances where the laptop (b) is busy doing other things and can't handle the processor load. >> 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? > > I suppose we could consider an option to skip the startup scan, though it > would > probably make an important performance difference for users who are storing > photos on network drives, which is not generally too useful given the > limitations above. I've nevertheless ticketd this here: > > http://redmine.yorba.org/issues/4754 Thanks. I think that would be nice to implement to skip searching for missing-files. I guess I could also imagine turning on my laptop without the network drive present and therefore having a bunch of missing photos. Turgut > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
