On Wed, Jun 19, 2013 at 3:05 PM, Jose Carlos Garcia Sogo
<jcs...@gmail.com>wrote:
> 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.
>
what would be relatively simple is to just include modules after colorin
for example, and store a downsized, compressed, demosaiced image in linear
rgb or Lab directly, so all the changes you're doing after that module are
a good approximation of what would happen to the full raw. our pipeline
from there should be resolution independent and operate in a nice
standardized color space.
to do some experiments before coding, i'd export an image to Lab or linear
rgb without any processing applied to it otherwise, and re-import that.
copy-pasting history stacks with post-colorin modules should give about the
same result as it does on the original image.
-jo
------------------------------------------------------------------------------
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
