[prev in list] [next in list] [prev in thread] [next in thread]
List: gimp-developer
Subject: Re: [Gimp-developer] gimp-developer-list Digest, Vol 9, Issue 25
From: Mathew Oakes <mathew.oakes () memechine ! org>
Date: 2012-06-16 23:15:43
Message-ID: d69c528a-c992-4038-b641-c7fdf8affcbc () email ! android ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I'd like to just chime in with support for the new save export setup.
It is a lot clearer than how photoshop morphs the save and save as dialogues with 'as \
a copy' as well as arbitarily hiding other options.
I'm astonished at the ire many are expressing over modifying their behaviour \
slightly. Perhaps they should just stick with 2.6
If there is a break with convention in the interface, it might be 'save as' may have \
been a less radical choice.
When there are adjustment layers and higher bit depth editing. This arrangement will \
be even more valuable
--
Sent from my phone, excuse my brevity.
gimp-developer-list-request@gnome.org wrote:
Send gimp-developer-list mailing list submissions to
gimp-developer-list@gnome.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
or, via email, send a message with subject or body 'help' to
gimp-developer-list-request@gnome.org
You can reach the person managing the list at
gimp-developer-list-owner@gnome.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-developer-list digest..."
Today's Topics:
1. Re: present xcf as what it is, a gimp project file format (Paka)
2. Re: present xcf as what it is, a gimp project file format
(Jon Nordby)
3. Re: present xcf as what it is, a gimp project file format (gg)
4. Re: present xcf as what it is, a gimp project file format (gg)
5. Re: present xcf as what it is, a gimp project file format
(Marco Ciampa)
6. Re: present xcf as what it is, a gimp project file format
(Marco Ciampa)
7. Re: present xcf as what it is, a gimp project file format
(Christopher Curtis)
_____________________________________________
Message: 1
Date: Sat, 16 Jun 2012 13:46:12 -0400
From: Paka <ptilopteri@gmail.com>
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <20120616174612.GB30791@wahoo.no-ip.org>
Content-Type: text/plain; charset=us-ascii
* Nicolas Robidoux <nicolas.robidoux@gmail.com> [06-16-12 12:55]:
> > - to really Save the contents of the file has to match what is
> > on the screen (save, quit, restart, open file: no change--undo
> > history excepted). this is not just a good idea, this is the law.
> > breaking the law: usability blooper.
>
> Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, and
> something else has to be used to "save" to any other format.
Maybe "export to"
> Nonetheless, I can't help but think that few people would buy a gun
> that makes it hard to shoot yourself in the foot.
>
> No matter how sensical the feature.
>
> Because most of us like to shoot first and ask questions later.
Perhaps YOU are not the "target audience".
--
(paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
http://en.opensuse.org openSUSE Community Member
Registered Linux User #207535 @ http://linuxcounter.net
_____________________________________________
Message: 2
Date: Sat, 16 Jun 2012 19:58:02 +0200
From: Jon Nordby <jononor@gmail.com>
To: Nicolas Robidoux <nicolas.robidoux@gmail.com>
Cc: gimp-developer mailing list <gimp-developer-list@gnome.org>
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID:
<CAJeABUVvVjnEQhpj7ij=SeDCnT3Q8PvxnfDwgbLt-RRkR2hc8Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On 16 June 2012 18:54, Nicolas Robidoux <nicolas.robidoux@gmail.com> wrote:
> > - to really Save the contents of the file has to match what is
> > on the screen (save, quit, restart, open file: no change--undo
> > history excepted). this is not just a good idea, this is the law.
> > breaking the law: usability blooper.
>
> Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, and
> something else has to be used to "save" to any other format.
>
> Nonetheless, I can't help but think that few people would buy a gun
> that makes it hard to shoot yourself in the foot.
>
> No matter how sensical the feature.
Most guns I know have the very sensible feature of a safety switch. It
does make it harder to accidentally shoot oneself in the foot, but I
have not heard very many people complain about it.
Most guns also have a shield in front of the trigger, and require a
substantial force to actually trigger. The ease of shooting oneself in
the foot is severely hampered by this, but again I do not see many
complain about it.
> Because most of us like to shoot first and ask questions later.
I think that "better safe than sorry" is a more sensible approach. One
can in general not revive dead peop^Wdocuments.
--
Jon Nordby - www.jonnor.com
_____________________________________________
Message: 3
Date: Sat, 16 Jun 2012 20:16:40 +0200
From: gg <gg@catking.net>
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <4FDCCD88.4070902@catking.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 06/16/12 19:58, Jon Nordby wrote:
> One
> can in general not revive dead peop^Wdocuments.
Which is why the don't give guns to children but top-end can be trusted
to understand that jpeg is lossy and png does not store layers.
It seems the "target user" argument is often cited here but they still
need to be prevented form doing something "unsafe".
do professional top end uses really need idiot proof software?
Given the functionality and a GUI that is not obstructive to the job in
hand, I don't think many of the target audience will be shooting
ourselves in the foot.
And if that happens I expect they would be suitably embarrassed and
adult enough not to blame it on gimp.
/gg
_____________________________________________
Message: 4
Date: Sat, 16 Jun 2012 20:02:26 +0200
From: gg <gg@catking.net>
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <4FDCCA32.4070903@catking.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 06/16/12 16:23, peter sikking wrote:
> Nicolas wrote:
>
> > Peter:
> > I think you misunderstood what gg is suggesting:
>
> no I did not. I pointed out some facts that close many, many routes
> in this kind of reasoning. closed and done, yes.
I too thought you were misreading what I suggested.
>
> let me first make a statement:
>
> _every_ time (yes, that is around a hundred times now) that I
> see this kind of user feedback (that it is normal to open a
> non-GIMP file, do some edits, then save it to the same format)
> I start to think like interaction designers should:
>
> let?s assume he is right. make it ?just work.?
encouraging
>
> and every time I run into the same problems, that are giant
> usability bloopers.
>
> - to really Save the contents of the file has to match what is
> on the screen (save, quit, restart, open file: no change--undo
> history excepted). this is not just a good idea, this is the law.
> breaking the law: usability blooper.
So now you are completely ignoring what I suggested and going off
somewhere else.
I specifically said that saving the file should be separate from saving
the entire working state of the image. Quite clearly this will not
preserve layers alpha etc, your "top end" target users ought be able to
cope with out with too much difficultly
Where did this save , restart, open : no change come from? Certainly not
what I outlined..
On the contrary I was suggesting a clear demarcation between saving the
edit state and saving back to the original format , with all that that
implies. That that should be both clear and logical within the interface
and that the user retains the choice of task in hand and not be forced
into what someone else thinks they "should" be doing.
>
> - this means that either all users would have to have intimate
> knowledge of file formats to know why the option to save to them
> disappear as edits are done (usability blooper. bit of alpha is
> introduced? no more jpeg; any layers? no more png; paths and
> layers? tiff is still there???) or one is doing the whole export thing
> anyway, so what is the difference (exporting is not safe, remember?)
> where are the extra hoops?
>
> - the alternative would be to limit things:
Now you are deliberately constructing ridiculous scenarios that neither
I nor anyone else suggested in order to knock them down. This generally
known as a straw man argument.
>
> > - it is 100% impossible to arrange it for popular non-GIMP files
> > (png/jpeg/tiff) there would be a mode where one could Open one,
> > make edits within the limits of the file format, and write the
> > bits straight back to a file in the same format.
>
> a multi-personality application: complete usability disaster.
>
> and that is where it stops.
I agree, functionality "modes" are definitely to be avoided. You will
also note that I did not suggest any modal functionality to limit what
can be done with gimp.
Another straw man.
Perhaps before dismissing my suggestion, you could actually comment on
what I suggested rather than something else. It follows what Nicholas
suggested recently and seems to make sense to a number of others.
An image manipulation program ought to have a simple way to handle std
formats as someone said. I think this is what the gripes are about.
I have no preference as to actual name, whether it gets called "work" or
"project" is immaterial , it is the function that is important.
/gg
_____________________________________________
Message: 5
Date: Sat, 16 Jun 2012 20:55:47 +0200
From: Marco Ciampa <ciampix@libero.it>
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <20120616185547.GA12368@ciampix-lap2>
Content-Type: text/plain; charset=us-ascii
On Sat, Jun 16, 2012 at 08:02:26PM +0200, gg wrote:
[...]
> I have no preference as to actual name, whether it gets called
> "work" or "project" is immaterial , it is the function that is
> important.
To add gasoline/petrol to fire: :-)
Thougth "work file" for xcf could be more precise than "project file"
since in a "project" I think could be involved more than one file,
instead (I think, correct me if I am wrong) that xcf will always be a
one file "project".
so be "workfile"! :-)
Import->insert into GIMP xcf workfile
Open->open GIMP xcf workfile (now also create a workfile without saving it and import \
the image in it immediatly) Export->extract info depending on format into the format \
chosen, eventually discarding some data/info Save->save GIMP workfile
I expect in a project file to save (more than in a workfile)
1) history
2) multiple work files
Peace ... :-)
bye
--
Marco Ciampa
+--------------------+
> Linux User #78271 |
> FSFE fellow #364 |
+--------------------+
_____________________________________________
Message: 6
Date: Sat, 16 Jun 2012 20:58:13 +0200
From: Marco Ciampa <ciampix@libero.it>
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID: <20120616185812.GA12477@ciampix-lap2>
Content-Type: text/plain; charset=us-ascii
Omissis:
On Sat, Jun 16, 2012 at 08:55:47PM +0200, Marco Ciampa wrote:
> 1) history
^ undo
--
Marco Ciampa
+--------------------+
> Linux User #78271 |
> FSFE fellow #364 |
+--------------------+
_____________________________________________
Message: 7
Date: Sat, 16 Jun 2012 15:28:35 -0400
From: Christopher Curtis <ccurtis0@gmail.com>
To: peter sikking <peter@mmiworks.net>
Cc: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
project file format
Message-ID:
<CAPPMeE=0bAZfrvk2-XBQMAtTaKJ0yc4-bizRBxrNfw4J9iYpYA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
On Sat, Jun 16, 2012 at 12:33 PM, peter sikking <peter@mmiworks.net> wrote:
I think you are very selective there what conventions surround Import.
> simply importing a an excel sheet into a non-ms program (open office,
> apple?s numbers) comes with a host of fears and promises.
>
And GIMP unnecessarily continues this tradition. If you open/import an
indexed image, GIMP goes into this weird "Indexed" mode that makes editing
all but impossible. This is very inconsistent with the asserted mental
model.
And while I prefer having Export, one workflow is broken rather severely by
this model: it is no longer possible to Import->Edit->Close->Export. The
flow Import->Edit->Close-Save is available, but this is a fast flow that
likely does not need to Save at all.
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.gnome.org/archives/gimp-developer-list/attachments/20120616/58dc605b/attachment.html>;
_____________________________________________
_____________________________________________
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
End of gimp-developer-list Digest, Vol 9, Issue 25
**************************************************
[Attachment #5 (text/html)]
<html><head></head><body>I'd like to just chime in with support for the new save \
export setup. <br> <br>
It is a lot clearer than how photoshop morphs the save and save as dialogues with \
'as a copy' as well as arbitarily hiding other options.<br> <br>
I'm astonished at the ire many are expressing over modifying their behaviour \
slightly. Perhaps they should just stick with 2.6<br> <br>
If there is a break with convention in the interface, it might be 'save as' \
may have been a less radical choice.<br> <br>
When there are adjustment layers and higher bit depth editing. This arrangement will \
be even more valuable<br>
-- <br>
Sent from my phone, excuse my brevity.<br><br><div \
class="gmail_quote">gimp-developer-list-request@gnome.org wrote:<blockquote \
class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, \
204, 204); padding-left: 1ex;"> <pre style="white-space: pre-wrap; \
word-wrap:break-word; font-family: sans-serif">Send gimp-developer-list mailing list \
submissions to<br /> gimp-developer-list@gnome.org<br /><br />To subscribe or \
unsubscribe via the World Wide Web, visit<br /> <a \
href="https://mail.gnome.org/mailman/listinfo/gimp-developer-list">https://mail.gnome.org/mailman/listinfo/gimp-developer-list</a><br \
/>or, via email, send a message with subject or body 'help' to<br \
/> gimp-developer-list-request@gnome.org<br /><br />You can reach the person managing \
the list at<br /> gimp-developer-list-owner@gnome.org<br /><br />When replying, \
please edit your Subject line so it is more specific<br />than "Re: Contents of \
gimp-developer-list digest..."<br /><br /><br />Today's Topics:<br /><br /> 1. Re: \
present xcf as what it is, a gimp project file format (Paka)<br /> 2. Re: present \
xcf as what it is, a gimp project file format<br /> (Jon Nordby)<br /> 3. Re: \
present xcf as what it is, a gimp proj ect
file format (gg)<br /> 4. Re: present xcf as what it is, a gimp project file \
format (gg)<br /> 5. Re: present xcf as what it is, a gimp project file format<br \
/> (Marco Ciampa)<br /> 6. Re: present xcf as what it is, a gimp project file \
format<br /> (Marco Ciampa)<br /> 7. Re: present xcf as what it is, a gimp \
project file format<br /> (Christopher Curtis)<br /><br /><br /><hr /><br /><br \
/>Message: 1<br />Date: Sat, 16 Jun 2012 13:46:12 -0400<br />From: Paka \
<ptilopteri@gmail.com><br />To: gimp-developer-list@gnome.org<br />Subject: Re: \
[Gimp-developer] present xcf as what it is, a gimp<br /> project file format<br \
/>Message-ID: <20120616174612.GB30791@wahoo.no-ip.org><br />Content-Type: \
text/plain; charset=us-ascii<br /><br />* Nicolas Robidoux \
<nicolas.robidoux@gmail.com> [06-16-12 12:55]:<br />> > - to really Save \
the contents of the file has to match what is<br />> > on the screen (save, \
quit, restart, open file: n o
change--undo<br />> > history excepted). this is not just a good idea, this is \
the law.<br />> > breaking the law: usability blooper.<br />> <br />> \
Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, and<br />> \
something else has to be used to "save" to any other format.<br /><br />Maybe "export \
to"<br /> <br />> Nonetheless, I can't help but think that few people would buy a \
gun<br />> that makes it hard to shoot yourself in the foot.<br />> <br />> \
No matter how sensical the feature.<br />> <br />> Because most of us like to \
shoot first and ask questions later.<br /><br />Perhaps YOU are not the "target \
audience".<br /><br />-- <br />(paka)Patrick Shanahan Plainfield, Indiana, USA \
HOG # US1244711<br /><a href="http://wahoo.no-ip.org">http://wahoo.no-ip.org</a> \
Photo Album: <a href="http://wahoo.no-ip.org/gallery2">http://wahoo.no-ip.org/gallery2</a><br \
/><a href="http://en.opensuse.org">http://en.opensuse.org</a> \
openSUSE Community Member<br />Registered Linux User #207535 @ <a \
href="http://linuxcounter.net">http://linuxcounter.net</a><br /><br /><br /><hr /><br \
/><br />Message: 2<br />Date: Sat, 16 Jun 2012 19:58:02 +0200<br />From: Jon Nordby \
<jononor@gmail.com><br />To: Nicolas Robidoux \
<nicolas.robidoux@gmail.com><br />Cc: gimp-developer mailing list \
<gimp-developer-list@gnome.org><br />Subject: Re: [Gimp-developer] present xcf \
as what it is, a gimp<br /> project file format<br />Message-ID:<br \
/> <CAJeABUVvVjnEQhpj7ij=SeDCnT3Q8PvxnfDwgbLt-RRkR2hc8Q@mail.gmail.com><br \
/>Content-Type: text/plain; charset=UTF-8<br /><br />On 16 June 2012 18:54, Nicolas \
Robidoux <nicolas.robidoux@gmail.com> wrote:<br />>> - to really Save the \
contents of the file has to match what is<br />>> on the screen (save, quit, \
restart, open file: no change--undo<br />>> history excepted). this is not just \
a good idea, this is the law.<br />>> breaking the law: usability blooper.<br \
/>><br />> Indeed, if "Save is lossless" is a law, "Save" has to be to XCF, \
and<br />> something else has to be used to "save" to any other format.<br \
/>><br />> Nonetheless, I can't help but think that few people would buy a \
gun<br />> that makes it hard to shoot yourself in the foot.<br />><br />> \
No matter how sensical the feature.<br />Most guns I know have the very sensible \
feature of a safety switch. It<br />does make it harder to accidentally shoot oneself \
in the foot, but I<br />have not heard very many people complain about it.<br /><br \
/>Most guns also have a shield in front of the trigger, and require a<br \
/>substantial force to actually trigger. The ease of shooting oneself in<br />the \
foot is severely hampered by this, but again I do not see many<br />complain about \
it.<br /><br />> Because most of us like t o shoot
first and ask questions later.<br />I think that "better safe than sorry" is a more \
sensible approach. One<br />can in general not revive dead peop^Wdocuments.<br /><br \
/><br />-- <br />Jon Nordby - <a href="http://www.jonnor.com">www.jonnor.com</a><br \
/><br /><br /><hr /><br /><br />Message: 3<br />Date: Sat, 16 Jun 2012 20:16:40 \
+0200<br />From: gg <gg@catking.net><br />To: gimp-developer-list@gnome.org<br \
/>Subject: Re: [Gimp-developer] present xcf as what it is, a gimp<br /> project file \
format<br />Message-ID: <4FDCCD88.4070902@catking.net><br />Content-Type: \
text/plain; charset=ISO-8859-1; format=flowed<br /><br />On 06/16/12 19:58, Jon \
Nordby wrote:<br />> One<br />> can in general not revive dead \
peop^Wdocuments.<br /><br />Which is why the don't give guns to children but top-end \
can be trusted <br />to understand that jpeg is lossy and png does not store \
layers.<br /><br />It seems the "target user" argument is often cited here but they \
still <br /> need to
be prevented form doing something "unsafe".<br /><br />do professional top end uses \
really need idiot proof software?<br /><br />Given the functionality and a GUI that \
is not obstructive to the job in <br />hand, I don't think many of the target \
audience will be shooting <br />ourselves in the foot.<br /><br />And if that happens \
I expect they would be suitably embarrassed and <br />adult enough not to blame it on \
gimp.<br /><br />/gg<br /><br /><br /><hr /><br /><br />Message: 4<br />Date: Sat, 16 \
Jun 2012 20:02:26 +0200<br />From: gg <gg@catking.net><br />To: \
gimp-developer-list@gnome.org<br />Subject: Re: [Gimp-developer] present xcf as what \
it is, a gimp<br /> project file format<br />Message-ID: \
<4FDCCA32.4070903@catking.net><br />Content-Type: text/plain; \
charset=windows-1252; format=flowed<br /><br />On 06/16/12 16:23, peter sikking \
wrote:<br />> Nicolas wrote:<br />><br />>> Peter:<br />>> I think \
you misunderstood what gg is suggesting:< br
/>><br />> no I did not. I pointed out some facts that close many, many \
routes<br />> in this kind of reasoning. closed and done, yes.<br /><br />I too \
thought you were misreading what I suggested.<br /><br />><br />> let me first \
make a statement:<br />><br />> _every_ time (yes, that is around a hundred \
times now) that I<br />> see this kind of user feedback (that it is normal to open \
a<br />> non-GIMP file, do some edits, then save it to the same format)<br />> \
I start to think like interaction designers should:<br />><br />> let?s assume \
he is right. make it ?just work.?<br /><br />encouraging<br /><br />><br />> \
and every time I run into the same problems, that are giant<br />> usability \
bloopers.<br />><br />> - to really Save the contents of the file has to match \
what is<br />> on the screen (save, quit, restart, open file: no change--undo<br \
/>> history excepted). this is not just a good idea, this is the law.<b r
/>> breaking the law: usability blooper.<br /><br />So now you are completely \
ignoring what I suggested and going off <br />somewhere else.<br /><br />I \
specifically said that saving the file should be separate from saving <br />the \
entire working state of the image. Quite clearly this will not <br />preserve layers \
alpha etc, your "top end" target users ought be able to <br />cope with out with too \
much difficultly<br /><br />Where did this save , restart, open : no change come \
from? Certainly not <br />what I outlined..<br /><br />On the contrary I was \
suggesting a clear demarcation between saving the <br />edit state and saving back to \
the original format , with all that that <br />implies. That that should be both \
clear and logical within the interface <br />and that the user retains the choice of \
task in hand and not be forced <br />into what someone else thinks they "should" be \
doing.<br /><br />><br />> - this means that either all users would have to \
have intimate<br />> knowledge of file formats to know why the option to save to \
them<br />> disappear as edits are done (usability blooper. bit of alpha is<br \
/>> introduced? no more jpeg; any layers? no more png; paths and<br />> layers? \
tiff is still there???) or one is doing the whole export thing<br />> anyway, so \
what is the difference (exporting is not safe, remember?)<br />> where are the \
extra hoops?<br />><br />> - the alternative would be to limit things:<br /><br \
/>Now you are deliberately constructing ridiculous scenarios that neither <br />I nor \
anyone else suggested in order to knock them down. This generally <br />known as a \
straw man argument.<br /><br />><br />>> - it is 100% impossible to arrange \
it for popular non-GIMP files<br />>> (png/jpeg/tiff) there would be a mode \
where one could Open one,<br />>> make edits within the limits of the file \
format, and write the<br />>> bits straight back to a file in the sa me
format.<br />><br />> a multi-personality application: complete usability \
disaster.<br />><br />> and that is where it stops.<br /><br />I agree, \
functionality "modes" are definitely to be avoided. You will <br />also note that I \
did not suggest any modal functionality to limit what <br />can be done with gimp.<br \
/><br />Another straw man.<br /><br /><br />Perhaps before dismissing my suggestion, \
you could actually comment on <br />what I suggested rather than something else. It \
follows what Nicholas <br />suggested recently and seems to make sense to a number of \
others.<br /><br />An image manipulation program ought to have a simple way to handle \
std <br />formats as someone said. I think this is what the gripes are about.<br \
/><br />I have no preference as to actual name, whether it gets called "work" or <br \
/>"project" is immaterial , it is the function that is important.<br /><br />/gg<br \
/><br /><br /><br /><br /><br /><br /><br /><hr /><br /><br />Message: 5<br
/>Date: Sat, 16 Jun 2012 20:55:47 +0200<br />From: Marco Ciampa \
<ciampix@libero.it><br />To: gimp-developer-list@gnome.org<br />Subject: Re: \
[Gimp-developer] present xcf as what it is, a gimp<br /> project file format<br \
/>Message-ID: <20120616185547.GA12368@ciampix-lap2><br />Content-Type: \
text/plain; charset=us-ascii<br /><br />On Sat, Jun 16, 2012 at 08:02:26PM +0200, gg \
wrote:<br />[...]<br />> I have no preference as to actual name, whether it gets \
called<br />> "work" or "project" is immaterial , it is the function that is<br \
/>> important.<br /><br />To add gasoline/petrol to fire: :-)<br /><br />Thougth \
"work file" for xcf could be more precise than "project file"<br />since in a \
"project" I think could be involved more than one file,<br />instead (I think, \
correct me if I am wrong) that xcf will always be a<br />one file "project".<br /><br \
/>so be "workfile"! :-)<br /><br />Import->insert into GIMP xcf workfile<br \
/>Open->open GIMP xcf wor kfile
(now also create a workfile without saving it and import the image in it \
immediatly)<br />Export->extract info depending on format into the format chosen, \
eventually discarding some data/info<br />Save->save GIMP workfile<br /><br />I \
expect in a project file to save (more than in a workfile)<br /><br />1) history <br \
/>2) multiple work files<br /><br />Peace ... :-)<br /><br />bye<br /><br />-- <br \
/><br /><br />Marco Ciampa<br /><br />+--------------------+<br />| Linux User \
#78271 |<br />| FSFE fellow #364 |<br />+--------------------+<br /><br /><br /><hr \
/><br /><br />Message: 6<br />Date: Sat, 16 Jun 2012 20:58:13 +0200<br />From: Marco \
Ciampa <ciampix@libero.it><br />To: gimp-developer-list@gnome.org<br />Subject: \
Re: [Gimp-developer] present xcf as what it is, a gimp<br /> project file format<br \
/>Message-ID: <20120616185812.GA12477@ciampix-lap2><br />Content-Type: \
text/plain; charset=us-ascii<br /><br />Omissis:<br /><br />On Sat, Jun 16, 2012 at \
08:55:47PM +0200, Marco Ciampa wrote:<br />> 1) history <br /> ^ \
undo<br />-- <br /><br /><br />Marco Ciampa<br /><br />+--------------------+<br />| \
Linux User #78271 |<br />| FSFE fellow #364 |<br />+--------------------+<br /><br \
/><br /><hr /><br /><br />Message: 7<br />Date: Sat, 16 Jun 2012 15:28:35 -0400<br \
/>From: Christopher Curtis <ccurtis0@gmail.com><br />To: peter sikking \
<peter@mmiworks.net><br />Cc: gimp-developer-list@gnome.org<br />Subject: Re: \
[Gimp-developer] present xcf as what it is, a gimp<br /> project file format<br \
/>Message-ID:<br /> <CAPPMeE=0bAZfrvk2-XBQMAtTaKJ0yc4-bizRBxrNfw4J9iYpYA@mail.gmail.com><br \
/>Content-Type: text/plain; charset="windows-1252"<br /><br />On Sat, Jun 16, 2012 at \
12:33 PM, peter sikking <peter@mmiworks.net> wrote:<br /><br />I think you are \
very selective there what conventions surround Import.<br />> simply importing a \
an excel sheet into a non-ms program (open office,<br />> ap ple?s
numbers) comes with a host of fears and promises.<br />><br /><br />And GIMP \
unnecessarily continues this tradition. If you open/import an<br />indexed image, \
GIMP goes into this weird "Indexed" mode that makes editing<br />all but impossible. \
This is very inconsistent with the asserted mental<br />model.<br /><br />And while I \
prefer having Export, one workflow is broken rather severely by<br />this model: it \
is no longer possible to Import->Edit->Close->Export. The<br />flow \
Import->Edit->Close-Save is available, but this is a fast flow that<br />likely \
does not need to Save at all.<br /><br />Chris<br />-------------- next part \
--------------<br />An HTML attachment was scrubbed...<br />URL: <<a \
href="https://mail.gnome.org/archives/gimp-developer-list/attachments/20120616/58dc605 \
b/attachment.html>">https://mail.gnome.org/archives/gimp-developer-list/attachments/20120616/58dc605b/attachment.html></a>;<br \
/><br /><hr /><br /><br /><hr /><br />gimp-developer-list mailing list<br \
/>gimp-developer-list@gnome.org<br /><a \
href="https://mail.gnome.org/mailman/listinfo/gimp-developer-list">https://mail.gnome.org/mailman/listinfo/gimp-developer-list</a><br \
/><br /><br />End of gimp-developer-list Digest, Vol 9, Issue 25<br \
/>**************************************************<br \
/></pre></blockquote></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