> Subject: Re: [Gimp-developer] Ditch the "Save a Copy" command (really)
> From: l...@holoweb.net
> To: strata_ran...@hotmail.com
> CC: gimp-developer-l...@gnome.org
> Date: Fri, 22 Jun 2012 18:59:51 -0400
> "save a copy" saves as xcf without changing the image filename
> It's not doing the same thing as "export a lossy copy you might or might
> not be able to re-open"
> Liam
Is this difference enough of a difference to even be a difference for the end 

Neither command takes action without a dialog prompt, neither one changes the 
file associated with the current image, neither one wipes the image state 
clean.  They are functionally identical, target file format (and consequences 
thereof) notwithstanding.

The way I see it, and reason for even posting such a radical suggestion in the 
first place, is that the Export command does not, necessarily, have to care 
whether the user selects a standard or XCF file format for the task, because 
either way it has no effect on the current image.  It doesn't change the target 
of subsequent Save commands, it doesn't un-dirty the image state (with possible 
loss of work when exiting GIMP).

-- Stratadrake
Numbers may not lie, but neither do they tell the whole truth.

> On Fri, 2012-06-22 at 14:46 -0700, Richard Gitschlag wrote:
> > Seriously -- I propose that the "Save a Copy..." command should be removed 
> > and its functionality merged into the "Export As..." command.
> -- 
> Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
> Pictures from old books: http://fromoldbooks.org/
> Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
> Take off your shoes. Now.
gimp-user-list mailing list

Reply via email to