Live data from Hacker News

GIMP 2.9.4 and our vision for the future

girinstud.io

81–90 of 98 posts

Re: GIMP 2.9.4 and our vision for the future

#81
post #77
post #37

Earlier quoted context omitted.

No it's not the same amount of clicking. From Gimp 2.7 to 2.8 something that used to be ctrl-s and close window went to ctrl-shift-e, and answering four dialog boxes before getting the image saved and the window closed. Around the time Gimp 2.8 came out, I wanted to edit and save around 50 images (in away that wasn't easy to automate). That (without the plugin that gives the old behavior) would be 200 dialog boxes to…

IIRC Ctrl shift e is export as, and ctrl e exports with no questions.

Ctrl-E is not available on newly opened .png files. You need to save at least once for it to work. (At least on Mac version of Gimp).

Re: GIMP 2.9.4 and our vision for the future

#82

Earlier quoted context omitted.

Yes. Ctrl-O edit Ctrl-S doesn't work there are plugins to turn it back

Just use Ctrl-E vs Ctrl-S, its a pretty common part of my workflow now

Ctrl-E is not available on newly opened .png files. You need to save at least once for it to work. (At least on Mac version of Gimp).

Re: GIMP 2.9.4 and our vision for the future

#83
post #22
post #20

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.

That was initially confusing to me as well, but it isn't that bad. If you open a .png (or similar) and edit it, there's a button in the File menu (I believe shortcut ctrl-shift-e) that exports directly to the original filename.

There isn't one. Ctrl-shift-e is "Export As" which opens a save dialog. Ctrl-e doesn't show up until you save the file manually at least once.

Re: GIMP 2.9.4 and our vision for the future

#84
post #27
post #26

Earlier quoted context omitted.

I liked the new behaviour personally

I totally see that it makes sense for some work flows, including the ones Gimp is probably most meant for. It was frustrating that for the people whose workflows were messed up, the developers were totally opposed to doing anything about it though. Kudos to the plugin author for rolling up her sleeves and providing a way out. Also kudos to the gimp developers for providing a plugin architecture that made such a custo…

If they made Ctrl-E work when you load the file for the first time, none of this would be the problem.

Re: GIMP 2.9.4 and our vision for the future

#85
post #20

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…

> I realize that this is common UX jargon, but is it literally "painful" to click "File->Export" rather than "File->Save"?

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.

Re: GIMP 2.9.4 and our vision for the future

#86
post #20

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…

> I realize that this is common UX jargon, but is it literally "painful" to click "File->Export" rather than "File->Save"?

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 ;)

Re: GIMP 2.9.4 and our vision for the future

#87

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.

I'm sure there are!

While I've been a Photoshop user since v5, I haven't always had it installed. There are even times I've done professional work on Linux where Photoshop doesn't run.

Currently I have Photoshop, but make use of the Gimp as well.

When there are so many free tools like there that can do a pro job - the question isn't "Gimp or Photoshop" but "Gimp, and Photoshop?" I could replace Illustrator with Inkscape and still get my job done, but I have bought Illustrator so I get my money's worth out of it. But that doesn't mean I not longer also have Inkscape. Of course I use Inkscape where it's better than Illustrator :D

Re: GIMP 2.9.4 and our vision for the future

#88
post #20

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.

Photoshop will save in the original format unless you do something to the image that isn't supported in that format (e.g. adding vectors, layers, layer filters, etc.) Then it will switch to .psd, although you still get the option of saving in the original format with Save As. I think that is a good design.

What would be better is having a dialog that says "You've used some additional features that can only be saved in .psd format: Save as PNG || Save as PSD || Save as something else" with the first being the default for when you press ENTER.

Re: GIMP 2.9.4 and our vision for the future

#89
post #88

Earlier quoted context omitted.

Photoshop will save in the original format unless you do something to the image that isn't supported in that format (e.g. adding vectors, layers, layer filters, etc.) Then it will switch to .psd, although you still get the option of saving in the original format with Save As. I think that is a good design.

What would be better is having a dialog that says "You've used some additional features that can only be saved in .psd format: Save as PNG || Save as PSD || Save as something else" with the first being the default for when you press ENTER.

I strongly disagree. You are arguing for a default that destroys work.

For example, if you open a .png, add a layer, and save, the default would merge the layers.

Re: GIMP 2.9.4 and our vision for the future

#90
post #89
post #88

Earlier quoted context omitted.

What would be better is having a dialog that says "You've used some additional features that can only be saved in .psd format: Save as PNG || Save as PSD || Save as something else" with the first being the default for when you press ENTER.

I strongly disagree. You are arguing for a default that destroys work. For example, if you open a .png, add a layer, and save, the default would merge the layers.

Default when you hit enter. You don't have to hit enter. Left then enter will get you your PSD.
Post reply on HN