On Wed, Jun 19, 2013 at 2:58 PM, Pascal Obry <pas...@obry.net> wrote: > > I have few time at the moment but I'm thinking about two new features > that I could try to implement at some point. > > 1. A way to call an external script after export > -> It would be possible to call The Gimp for example > -> Or call a script that would add an ICC profile to the image > and call the printing tool (eog or whatever). > > This feature will remove the need to open a console to do all those > things manually.
I think that way to do all this is through Lua. I don't know to what extent this can be implemented today, but it can be extended to do what you desire. > > 2. A way to keep a photo in a cache locally and be able to edit it even > when the master picture is not present (on an external drive not > connected). > > This is a new feature of Lr5 and I had this needs long ago, probably > a nice new feature that I could try to implement. > > If I come to it, I'll discuss the UI part before of course. I have no > idea how to integrate this nicely at the moment. On the implementation side, I think they are storing a cache file with dng files in it. Each dng has the smaller image (around 2400px for the larger border) and I guess the dng also contains the development history (and undo, snapshots, ...) synced with the db. Once you get again the file around, it will need to sync the development information back to the xmp. ------------------------------------------------------------------------------ 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
