I found this fix, which made quick uses of GIMP less painful for me: http://shallowsky.com/software/gimp-save/
I'm assuming the new save behavior persists in Gimp 2.9.x, but I don't know.
I realize that this is common UX jargon, but is it literally "painful" to click "File->Export" rather than "File->Save"?
I frequently hear front-end developer peers arguing that it's "painful" to read 10 or 20 lines of XML. Back-end peers retort that it's more "painful" to look at large complex structures in JSON.
There's a hundred other cases in which this comes up. Are people really walking around in crippling pain, due to various software having trivial differences from their ideal preference?
One can also make that statement to the person who decided the default save format should be different from the one the user opened. IMHO most people want to save in the format they started with and if they want to change it, something other than "save" is warranted.
"Open" would then more correctly called "Import" for most file formats. If you want Open and Save to work with all file formats, you'd then need to restrict the UI to operations that work with the file format you have open. Otherwise, you lose data when saving.
>> IMHO most people want to save in the format they started with and if they want to change it, something other than "save" is warranted.
Most people when they save a file expect everything to be there when they open it later. That's only possible when you save using that applications proprietary file format.
I understand your points, but it doesn't mean that there aren't pragmatic UX choices to be made here.
The main problem I have with it IS the fact that you have to use the mouse. There's no keyboard shortcut (at least on Mac version of Gimp). If you open a .png file, there's no keyboard shortcut to export it (overwrite). You can invoke the "export as" dialog which requires a couple more key presses and a context switch. Once you save it via menu, then the Command+E shortcut starts working, but for the first save not. As someone who works a lot with Gimp, this is the main usability problem I have.
If I open a .png, and done things to it, and I want to save it, it's because I just want to save a .png. If I wanted to have another format I would "import" the .png, not open it.
If I want to save something else, then I'll go to the save as... And will choose what I want to save.
Having a "save as..." that just gives me the proprietary format and hanging to go to the "export as..." to have other formats is even worst.
I found it mildly annoying at first but then I learnt that the luckily export function has a keyboard shortcut. I can accept that I have to press ctrl+shift+e to export an image ;)
there are plugins to turn it back
No it wasn't literally painful. But frustrating. Nearly as frustrating as people not accepting that people legitimately use software in different ways.
Anecdotally, this would often just outright segfault GIMP for me. I ended up having to use a different image editing program entirely until this was fixed.
"%s may contain features that are not compatible with %s. Do you want to save the document in this format?
To save, click Yes.
To preserve formatting, click No. Then save a copy in the %s format."
For example, if you open a .png, add a layer, and save, the default would merge the layers.
Well, remember, GTK originally stood for GIMP ToolKit. The GNOME DNA is strong within GIMP.
And make no mistake, that's a very GNOMEy thing to do.
some forget that GNOME started very far from where it is now. Look only to Sawfish for proof.
Here gimp devs has chosen to make the nondestructive action the default one - a sane choice given their development resources.
Worst case if you forget to export in the correct format you have to export again.
If it by default saved back to the same format by default then in a worst case you lose hours of work.
UX is about more than shiny, about more than copying Mac, about more than saving a keystroke here and there.
(Hardcore dev here, not UX, not UI.)
Even to make extra sure (though I already was), I have tested it on a GIMP 2.8 and on GIMP master just now. That works.
I tried with 2.8.14 and 2.8.18, both running on Mac OSX. As you can see the Command-E option only shows up after I do "Export as".
The whole idea around this and the way they decided it to work is a mess.