Hi Roland, > Hope you are fine with me adding my own opinion.
Sure! > 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. I agree 100%. > 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. We could have both but I would really prefer not having another button for this. > 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... Right, this probably means that we want to forbid removing a local cached image if it has been edited and the original file is not present. When the original file is present we have the opportunity to sync back the xmp just before purging the image from the cache. Thinking about it this seems the safest option. Pascal. -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://v2p.fr.eu.org http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B ------------------------------------------------------------------------------ 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
