yahvuu wrote:
> This becomes clear in comparison with a database-driven, version-controlled 
> approach
> as e.g. sketched in the last mockup of [1]. A Save command is superfluous in 
> this
> scenario. When an image gets edited, it's reasonable to assume the user wants 
> to keep
> the changes. Otherwise she can undo, revert (= bulk undo) or simply delete 
> the image.

While this and the rest of your mail is true and I agree, one could 
argue that users of a high-end app still want to be in complete control 
of when an image composition is written to disk for whatever reason. Or 
perhaps I'm just too backwards... :)

 / Martin
Gimp-developer mailing list

Reply via email to