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 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
	project file format
Message-ID: 
Content-Type: text/plain; charset=us-ascii

* Nicolas Robidoux  [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 
To: Nicolas Robidoux 
Cc: gimp-developer mailing list 
Subject: Re: [Gimp-developer] present xcf as what it is,	a gimp
	project file format
Message-ID:
	
Content-Type: text/plain; charset=UTF-8

On 16 June 2012 18:54, Nicolas Robidoux  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 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
	project file format
Message-ID: 
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 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
	project file format
Message-ID: 
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 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
	project file format
Message-ID: 
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 
To: gimp-developer-list@gnome.org
Subject: Re: [Gimp-developer] present xcf as what it is, a gimp
	project file format
Message-ID: 
Content-Type: text/plain; charset=us-ascii

Omissis:

On Sat, Jun 16, 2012 at 08:55:47PM +0200, Marco Ciampa wrote:
> 1) history 
^ undo