Tobias Ellinghaus <[email protected]> writes: > It shouldn't bee too hard to move general data like presets and > styles to its own database, however, some care has to be taken to find all > places in the code that try to access those tables.
I would love to see an equivalent of .xmp files for presets too, ie. a copy of the data that is easily accessible from the filesystem. Use-case: the other day, I clicked 'Update preset foobar' instead of 'Use preset foobar'. I just destroyed my preset. OK, no problem I thought: I have backups. snapper (http://snapper.io/) gives me a /home/.snapshots/$id/$login/.config/darktable). BUT, restoring the backup without restoring the complete database would be a surgical operation in the DB, I could not do it. I managed to restore my preset by finding an old image that used it, and restored the preset from the image. Had the same story happened to me with the history stack of an image, I would have grabbed the .xmp file in my backup, reloaded it, and got my changes back. On overall, darktable is very good when it comes to repairing mistakes. The non-destructive flow, history stack management & all are really cool for that. But there are still a few cases where a simple operation (without "are you sure?" confirmation) can lead to data-loss. Cheers, -- Matthieu Moy http://www-verimag.imag.fr/~moy/ ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
