On Tue, 20 Nov 2012 14:42:05 +0400, Alexandre Prokoudine wrote: > On Tue, Nov 20, 2012 at 5:02 AM, Robert Krawitz wrote: > >>> This may change in future versions - where maybe you won't even have >>> the choice not to save, because saving has become so cheap that it can >>> be done any time, and the program just does it for you. >> >> This can become really annoying, really fast... >> >> Applications that helpfully save their constantly can cause a lot of >> grief if I change something I really, really didn't want to change that >> causes something very strange to happen. Yes, I know about the undo >> stack and all that, but... > > Are you familiar with the concept of saving history stack into project files? I presume you mean appending journal entries to the file? Yes, and that's a lot safer than other ways of doing it. But make sure that you handle situations of high latency (NFS/Samba) and low disk space well. Also, there needs to be a way to remove particular entries from the project file. Say I accidentally add a layer from a file that I *really* don't want to be in there (a scan of my credit card, for example). I want to be able to completely purge it. -- Robert Krawitz <rlk@xxxxxxxxxxxx> MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four! Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton _______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
