Re: [Gimp-developer] Quick-edit workflow
guys + girls, it is a tricky thing, this overwrite vs. export. there is a difference, overwrite is for working ‘backward’ as I called it: doing some work on a non-gimp file and feeding this directly back to it. it is labelled brutally and frankly, with intent. export is for working ‘forward’, towards a new result. but as Richard comments, the difference is not that big. this is what I exploited in the design for repurposing the Export-to item for Overwrite. of course one can use Export... to set up to write over one of the source files of the composition one is working on. thus exporting is the general game, with one special case built in: hardwiring the initiating source file as export target and giving this a fearsome name (beware: burning bridges) Yes, Export-to and Export... mirror images of Save and Save-as... I think I can see what Akkana means: when there is no export target, the menu items are “Export to” and “Export...” that is not ideal. and it’s clear that it irritates people. note that the export-to item cannot be grayed out in this case. ctrl-E just has to work (leading to an Export..., yes, just as the first Save is a Save As...) reviewing the situation, I see that the straightforward solution is to relabel Export... -> Export As... (in all states) “Export to” -> Export (when no export target) you can see that this achieves perfect mirroring of Save and Save As... “Export to foo.xyz” and “Overwrite foo.xyz” stay as-is, they work well with Export As... (just in case you wonder, yes I am giving up on something by doing this: in so many other application the label on the export menu item is Export... ) --ps founder + principal interaction architect man + machine interface works http://blog.mmiworks.net: on interaction architecture ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] gimp-developer-list Digest, Vol 26, Issue 7
Hi people, I agree with Akkana. "Export..." and "Export to" have poor User Interface- clarity. They don't mentally distinguish very well, as I reported on the GIMP bugtracker it's easy & common to select the wrong one since the process to distinguish them involves too much mental negation. > For one thing, I'm still confused about the difference between Export... and Export to > -- they seem to do the same thing even though one has a ... and the other doesn't, they > have different shortcuts, and one of them isn't always available. Part of the problem is how the menu-items are labelled (especially when no file is selected, this is confusing), part of the problem may be how the menu-items are ordered. Cognitively it really doesn't seem to be good design. > And I can never remember in any given session which images can use > Overwrite versus which ones need an Export... or Export to, so I no > longer trust any save/export shortcut to be the right one, and > almost always end up going to the menus instead. My position (and I'm pretty sure I'm objective here) is that even looking at the menu, things are less than 100% obvious. -- On another note, having some working shortcuts in the "Close" dialog to Discard is great. Perhaps even better would be, to enable these to work *without* needing a Ctrl-modifier key.. Regards Thomas ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Quick-edit workflow
Richard Gitschlag (strata_ran...@hotmail.com) wrote: > And similar to you, one thing *I* don't get is why "Export" and > "Overwrite" need to be separate commands. Because without this distinction you'd accidentially overwrite your precious orignal file after accidentially doing an "Export" instead of an "Export To". Bye, Simon -- si...@budig.de http://simon.budig.de/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Quick-edit workflow
> Date: Fri, 8 Nov 2013 20:15:23 -0800 > From: akk...@shallowsky.com > To: gimp-developer-list@gnome.org > Subject: Re: [Gimp-developer] Quick-edit workflow > > I've found that the new model makes me stop and think every time > I save or export anything. For one thing, I'm still confused about > the difference between Export... and Export to -- they seem to do > the same thing even though one has a ... and the other doesn't, they > have different shortcuts, and one of them isn't always available. > And I can never remember in any given session which images can use > Overwrite versus which ones need an Export... or Export to, so I no > longer trust any save/export shortcut to be the right one, and > almost always end up going to the menus instead. It's just like the difference between "Save" and "Save As" in that, during the same session, "Export" uses the settings from the previous export (if any) while "Export to..." always prompts for a filename. Of course, if you don't export very often then the difference is moot because every export happens during a different session. And similar to you, one thing *I* don't get is why "Export" and "Overwrite" need to be separate commands. -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
