Live data from Hacker News

GIMP 3.2 released

gimp.org

51–60 of 92 posts

Re: GIMP 3.2 released

#51
post #17

Earlier quoted context omitted.

Almost all programs treat the “Save” operation as something used with the native format, in this case XCF files. These preserve things like layers, etc. JPG and other formats are exports because after you close the file you can’t get all that stuff back when you reopen it.

Why is then opening a JPEG not an Import? I get it, and when Photoshop changed this default, GIMP followed with changing this workflow. It used to be different in older versions of Photoshop and Gimp. Advanced user usually know exactly what they're doing, and opening a PNG or JPEG file, changing a few pixels, and saving it, should require as few key presses as possible. I don't want the UI to get in my way when I ope…

'Opening a JPEG' is creating a new image and importing the JPEG to it. ctrl-e on first use will establish the export setting. It's two clicks if you really want to overwrite the original. I think it would be very easy to accidentally and destructively overwrite the original image file if it was different, when ctrl-e is in muscle memory.

Re: GIMP 3.2 released

#52
post #39

Earlier quoted context omitted.

If you mean the color icons, you can easily switch back to those in the Welcome Dialog that appears when you first open GIMP (look in the Personalize tab). It's the first thing I do when I install GIMP on a new machine. :)

Did you also manage to enable menu icons?

That was a feature in GTK2 (the GUI library we use) that was removed in GTK3. We could try to fight the library and reimplement it ourselves, but it'd take a developer dedicated to do it. I miss the menu icons too. :(

Re: GIMP 3.2 released

#53
post #47

Earlier quoted context omitted.

If you mean the color icons, you can easily switch back to those in the Welcome Dialog that appears when you first open GIMP (look in the Personalize tab). It's the first thing I do when I install GIMP on a new machine. :)

Thank you for this. Also small world, floating point JPEG person here.

Ah, hey! We've been busy with getting 3.2 finished, but I plan to go back and read over your latest message once we've recovered a bit. :)

Re: GIMP 3.2 released

#54
post #23

Earlier quoted context omitted.

I see you are getting downvoted but I don't blame you for this question. I've been curious about what developers of established products are doing with LLM assisted coding myself.

Like most of us, they're certainly using ai-assisted auto-complete and chat for thinking deep. I highly doubt they're vibe coding, which is how I interpret the parent's question and probably why they are being down voted.

I take it you also mean vibe coding to be one shot and go?

Re: GIMP 3.2 released

#55
post #4

Being able to scale an image without losing quality is going to be handy. I always found it odd that scaling down an image now and then scaling it back to its original size 2 seconds later with the same tool resulted in a loss of quality and having to delete the layer, then re-import the image to get the original quality back. This plugin https://github.com/LinuxBeaver/Gimp_Layer_Effects_Text_Style... also makes addi…

> I always found it odd that scaling down an image now and then scaling it back to its original size 2 seconds later with the same tool resulted in a loss of quality Maybe it's because I grew up with Paint Shop Pro 6 and such, but that seems completely normal and expected to me

I was using Photoshop, I don't remember when exactly but it's probably in the 15-20 year range when non-destructive scaling was available. I don't remember not having it. Glad to see GIMP is moving in this direction.

Re: GIMP 3.2 released

#56
post #7

I use Gimp pretty sporadically but the latest UI refresh (I’m guessing introduced in 3.0?) completely baffles me. It might just be that it’s better tailored for graphic designers, which I’m clearly not. But now I can’t even figure out how to draw a square on screen. Let along anything clever.

Don't worry, GIMP's UI never made any sense to anyone (Graphic Designer or otherwise), save for hardcore GIMP fans.

Re: GIMP 3.2 released

#57
post #25

Earlier quoted context omitted.

"When I was a kid, when we shrunk a 200x200 image down to 100x100 we lost information forever, and we liked it that way. It was a simple time. A predictable time."

That is generally my intention when downscaling an image.

Until you're a professional designer and they ask you to "scale up this part" or something. Then you realize that your actual intention is having the original layer currently rendered at that size and did not actually intend to permanently modify the original so you can't go back.

Once you export it is, of course, actually downscaled.

Same idea behind masks and modifiers and the like. Most modern creation tools try to give ample opportunity for non-destructive modification to simpler, immutable primitive layers.

Re: GIMP 3.2 released

#58
post #47

Earlier quoted context omitted.

Thank you for this. Also small world, floating point JPEG person here.

Ah, hey! We've been busy with getting 3.2 finished, but I plan to go back and read over your latest message once we've recovered a bit. :)

No rush - been busy over here too.

Re: GIMP 3.2 released

#60
post #17
post #12

Can I finally Ctrl+s jpeg image? And no, export is not enough because first time it will ask for for path and compression level which it already knows. I just want to Ctrl+s and be done.

Almost all programs treat the “Save” operation as something used with the native format, in this case XCF files. These preserve things like layers, etc. JPG and other formats are exports because after you close the file you can’t get all that stuff back when you reopen it.

This is not true with common applications people are familiar with. Excel and Word will happily "save" a PDF, and it behaves like exporting and doesn't change the document being edited.
Post reply on HN