nice, that sounds really simple :)
what do you need to store in the database? is it just one bit `cached' or
`not cached' ? i guess that could be hidden in the flags field..
anyways, cool feature.
cheers,
-jo
On Tue, Jul 2, 2013 at 9:11 AM, Pascal Obry <pas...@obry.net> wrote:
> Some news about this work.
>
> *** The context:
>
> - this is mainly for netbook users I suppose. desktop should always
> have access to the original pictures.
>
> - having original pictures on the local hard drive of a notebook is
> dangerous given the lifetime of an hard drive!
>
> *** The goal:
>
> - make it possible to use *all* dt features even when an image on an
> external drive not connected
>
> - not meant to have a local copy of everything, just copy what needs
> some work.
>
> - to be able to work on a set of pictures (recent or not) on plane
> on train or during a meeting away from home.
>
> *** Some usage scenario (based on my needs):
>
> - you import a set of pictures from the camera. you get local copy
> of them before moving them in a RAID storage for safety. Moving away
> from home you can start editing the pictures.
>
> - you've taken a set of pictures from an event. you want to bring
> some of them with you on your photo club meeting for developing them
> with a friend.
>
> - you need to print some picture on a high-end printer in a photo
> club (some minor editing may be required), you get a local copy before
> moving away from home.
>
> *** How does it works:
>
> - two buttons are added into the lighttable "selected images"
> module. one to get a local copy and one to remove pictures from the
> local storage. this is working on the current selection (like all
> other buttons there).
>
> - local copy status is a white circle on the right of the current color
> labels
> => we probably need something better here, that's just to keep the
> ball rolling...
>
> - the local copies are stored into: ~/.cache/darktable
>
> naming is: img-<imgid>-<md5-full-path-name>.<ext>
>
> => <imgid> will be quite handy to debug if something goes wrong
>
> - when accessing a picture, if not found on the original storage we
> look into the cache.
>
> - when a picture is deleted, the cache file is deleted if any
>
> - when a picture is moved, the cache file is renamed if any
>
> I think that's all.
>
> You can try it on the "local-cache" branch in GitHub.
>
> Beware that this adds a field into the images table on the database.
> Probably better to test this feature on a copy of the database.
>
> Anyway, waiting for feedback.
>
> Thanks.
>
> --
> 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
>
------------------------------------------------------------------------------
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
