GNOME Bugzilla – Bug 122934
saving backups for XCF
Last modified: 2018-05-24 10:54:58 UTC
A handy "save your day" feature is the possibility to store a history of an xcf file. A user preference would tell GIMP how many backup copies of a file to store. Each time I would use File>save, GIMP would move the last version of the file to a numbered backup file, and cycle all oledr version too, discarding the last backup. A preference setting of '3' would eventually give you foobar.xcf, .backup1-foobar.xcf,.backup2-foobar.xcf,.backup3-foobar.xcf or somesuch. Why to have this? ----------------- * Even though GIMP has become more stable, crashes occur. * Large projects tend to last longer than one session in GIMP. * Undo history is not stored in the xcf (and I would think this sort of solution is more clean). * This would also be handy for an autosave functionality.
Why don't you use a versioned image database instead? IIRC, HaruspeX integrates quite nicely with GIMP and supports this (only in a lot more sophisticated fashion).
I have not known about haruspex. Isn't a DBMS requirement a little overkill for this sort of functionality?
From the HaruspeX Homepage: Last change: 1999-08-21 Requirements: The GIMP 1.0.x or 1.1.x http://www.linux.it/ospiti/haruspex/ http://freshmeat.net/projects/haruspex/?topic_id=68
Well, porting this to gimp-1.3 shouldn't be a major undertaking. The API changes in GIMP are marginal.
If there's not much interest in this functionality I'm fine with using CVS for this, but it would be a shame imho.
One thing I've thought of is hooking gimp and subversion together. It wouldn't be very hard, since both gimp and subversion have nice python bindings. :) Subversion is also a hell of a lot easier to set up than a full blown SQL db. Plus you get binary diffs.
There is/was an xdelta plugin that does almost exactly what is requested.
See also bug 138373.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/51.