Hi Pascal, Hope you are fine with me adding my own opinion.
Am Mittwoch, 3. Juli 2013, 16:17:22 schrieb Pascal Obry: > > You are taking for granted that the user will further develop the > > image once the external drive is available. > > Right! > > > But it may not happening, even more in our implementation in which as > > we are store the full raw image the user can even have exported and > > delivered the final images from the local cache. > > Sure, this is indeed something to consider. Should we try at startup > time to sync xmp for all images for which a local copy exists? Will this > be enough or do you envision some complications? I think it's essential that the user is not required to touch every single picture again just to export it to the external storage. Imagine a film strip of let's say 200 images which you edited offline and now want to sync back. You really do not want to open each one in darktable mode just to sync. Syncing on startup could be an option, although I would prefer an extra button for this. Usually, for example, I attach an external harddrive holding all my images, and having to restart darktable just to initiate the sync is a bit unhandy, I think. Additionally, the sync of the xmp files should be independent of whether the local copy has already been removed before or not. So, when I select an image for local caching, do my offline editing, when finished remove the image from the cache and afterwards attach my harddisk, I want to have the xmp file being updated nevertheless. Hope this makes some sense... Regards, Roland ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
