41–50 of 98 posts
The only way I ever use GIMP is through forked builds that let you save as whatever you want without the annoying save/export distinction, so they seem to making it tougher for people who are making good forks of their bad software to do their job.
Really not a fan of this. In a link he says he took the code for saving/exporting and split it apart: http://girinstud.io/news/2015/09/improving-the-export-proces... The only way I ever use GIMP is through forked builds that let you save as whatever you want without the annoying save/export distinction, so they seem to making it tougher for people who are making good forks of their bad software to do their job.
And by keeping them split, it makes some things more convenient. When I edit images, I save a .xcf and I also export a .png. Having to manually switch between these file-types and manually remember and reënter the (possibly differing) filenames when saving would be a pain. Keeping Export and Save as separate means I don't have to. It also means that Ctrl-S saves the project, rather than overwriting my last export. And as the part you linked to points out, this means you can do things like change the scale at export time.
Really not a fan of this. In a link he says he took the code for saving/exporting and split it apart: http://girinstud.io/news/2015/09/improving-the-export-proces... The only way I ever use GIMP is through forked builds that let you save as whatever you want without the annoying save/export distinction, so they seem to making it tougher for people who are making good forks of their bad software to do their job.
Saving and exporting are different tasks: the former saves the current work-in-progress project with no loss of data, the latter exports to a particular image format and is inherently lossy. If you combine them, you risk misleading users. And by keeping them split, it makes some things more convenient. When I edit images, I save a .xcf and I also export a .png. Having to manually switch between these file-types and m…
IMHO just keep things simple and use Save for saving in the same format as the original (possibly if a warning if it doesn't support some things you've done to the file), or Save As for saving in a different format.
Gimp 2.8 frustrated me: I could no longer open a .png, edit it and easily resave it back to .png. The Gimp developers knew better and made the UI strongly favor saving as .xcf, which makes sense in some use-cases, but not mine. 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.
> less painful for me 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 ar…
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.
Gimp 2.8 frustrated me: I could no longer open a .png, edit it and easily resave it back to .png. The Gimp developers knew better and made the UI strongly favor saving as .xcf, which makes sense in some use-cases, but not mine. 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.
Earlier quoted context omitted.
Saving and exporting are different tasks: the former saves the current work-in-progress project with no loss of data, the latter exports to a particular image format and is inherently lossy. If you combine them, you risk misleading users. And by keeping them split, it makes some things more convenient. When I edit images, I save a .xcf and I also export a .png. Having to manually switch between these file-types and m…
What's the difference, and why should it matter? I just want to persist my changes to a file. IMHO just keep things simple and use Save for saving in the same format as the original (possibly if a warning if it doesn't support some things you've done to the file), or Save As for saving in a different format.
See edits.
> IMHO just keep things simple and use Save for saving in the same format as the original (possibly if a warning if it doesn't support some things you've done to the file)
You'd have to warn on every single format except XCF.
> or Save As for saving in a different format.
But I don't want to change the save destination. The project and the export are separate for me.
If you just want to save a PNG or something, you have the option of using Export exclusively.
But I need the ability to Save.
Earlier quoted context omitted.
> less painful for me 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 ar…
Yes. Ctrl-O edit Ctrl-S doesn't work there are plugins to turn it back
GIMP is an icon of open-source software, but do any professional designers use it full-time over Photoshop? Compare with Sketch, which has taken scores of users from Illustrator.
IMO the main ideological difference is that Photoshop UI is targeting users who like to see things visually. Gimp has a more programmatic legacy. PS allows moving around a few sliders while looking at the screen to see how things change and nail it when the results look visually good. I bet that is critical for most PS users. It is for me. I paid for an (educational) PS license just so I can edit my photos before I p…
Gimp is just full of little annoyances that interrupt your flow and make it difficult to work efficiently.