[prev in list] [next in list] [prev in thread] [next in thread]
List: gimp-developer
Subject: Re: [Gimp-developer] =?windows-1256?q?Merge_=22Save_a_Copy=22_with_?=
From: Richard Gitschlag <strata_ranger () hotmail ! com>
Date: 2012-06-24 16:53:33
Message-ID: SNT111-W25C15E36FDABD127DD38629CE20 () phx ! gbl
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Date: Sat, 23 Jun 2012 16:06:47 -0400
Subject: Re: [Gimp-developer] Ditch the "Save a Copy" command (really)
From: ccurtis0@gmail.com
To: peter@mmiworks.net
CC: strata_ranger@hotmail.com; gimp-developer-list@gnome.org
That "Save" does not lose information seems natural, but that "Export" must lose \
information seems contrived.
Chris-----------
I agree. To the end user, whether or not Export "loses" any information is different \
with each and every image. A single-layer image with no transparency and no metadata \
(paths, masks, EXIF, color profile, etc.) can be safely written to over a dozen \
assorted image formats with nothing of value lost. Yes, JPG is lossy and GIF is \
inherently indexed, but the target user knows that already, they'll pick a file \
format appropriate for what they need.
Out of curiosity, I tried typing an XCF file into the Export dialog yesterday and got \
that non-negotiable warning that GIMP won't let you do that. Um ... why? I see no \
practical reason why the Export command should be prohibited from outputting an XCF \
file to disk when it already outputs every other image format GIMP has any support \
for.
> Date: Sun, 24 Jun 2012 13:23:48 +0200
> From: tobias.oelgarte@googlemail.com
> To: gimp-developer-list@gnome.org
> Subject: Re: [Gimp-developer] Merge "Save a Copy" with "Export As" [was: Ditch the \
> "Save a Copy" command (really)]
> I personally never use "save a copy". I just use "save as" and append a
> new version number to the document. If i look at Blender then they did
> go even a step further. There are small nice buttons "+" and "-" to
> increase/decrease the version number without typing.
-----------
I am also the type to use a "versioned" file naming scheme (kinda), every time I \
would want to "Save a Copy" of my project I actually just hit "Save As" and increment \
my filename - the previous filename is never touched again and automatically becomes \
the "backup copy". So yes, reason number four would be that my personal workflow has \
no use for "Save a Copy" either.
-- Stratadrake
strata_ranger@hotmail.com
--------------------
Numbers may not lie, but neither do they tell the whole truth.
[Attachment #5 (text/html)]
<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Date: Sat, 23 Jun 2012 16:06:47 -0400<br><div>Subject: Re: [Gimp-developer] Ditch the \
"Save a Copy" command (really)<br>From: ccurtis0@gmail.com<br>To: \
peter@mmiworks.net<br>CC: strata_ranger@hotmail.com; \
gimp-developer-list@gnome.org<br><br><div class="ecxgmail_quote">That "Save" does not \
lose information seems natural, but that "Export" must lose information seems \
contrived. <div><br></div><div>Chris</div><div>-----------<br><br>I agree. To \
the end user, whether or not Export "loses" any information is different with each \
and every image. A single-layer image with no transparency and no metadata \
(paths, masks, EXIF, color profile, etc.) can be safely written to over a dozen \
assorted image formats with nothing <b>of value</b> lost. Yes, JPG is lossy and \
GIF is inherently indexed, but the target user knows that already, they'll pick a \
file format appropriate for what they need.<br><br>Out of curiosity, I tried typing \
an XCF file into the Export dialog yesterday and got that non-negotiable warning that \
GIMP won't let you do that. Um ... why? I see no practical reason why the \
Export command should be prohibited from outputting an XCF file to disk when it \
already outputs every other image format GIMP has any support for.<br><br><br>> \
Date: Sun, 24 Jun 2012 13:23:48 +0200<br>> From: \
tobias.oelgarte@googlemail.com<br> > To: gimp-developer-list@gnome.org<br>> \
Subject: Re: [Gimp-developer] Merge "Save a Copy" with "Export As" [was: Ditch the \
"Save a Copy" command (really)]<br>> <br>> I personally never use "save a \
copy". I just use "save as" and append a <br>> new version number to the document. \
If i look at Blender then they did <br>> go even a step further. There are small \
nice buttons "+" and "-" to <br>> increase/decrease the version number without \
typing.<br>----------- <br><br>I am also the type to use a "versioned" file naming \
scheme (kinda), every time I would want to "Save a Copy" of my project I actually \
just hit "Save As" and increment my filename - the previous filename is never touched \
again and automatically becomes the "backup copy". So yes, reason number four \
would be that my personal workflow has no use for "Save a Copy" either.<br><br><br>-- \
Stratadrake<br>strata_ranger@hotmail.com<br>--------------------<br>Numbers may not \
lie, but neither do th ey tell the whole truth.<br><br></div></div></div> \
</div></body> </html>
_______________________________________________
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic