162 karma · joined November 29, 2024
Out of curiosity, what improvements in 3.0 RC are you skeptical of? If you're willing to share, it'd be helpful feedback for us. :)
Now that the API is stable for 3.0, we're hoping more people will feel comfortable updating to it.
I know that one of the behind-the-scenes things that Jehan (the maintainer) has been working on is establishing a foundation in partnership with GNOME. This will allow for easier methods of accepting donations, and developer grants to fund more sustained developer work. That obviously takes away from his coding time (and he's a much, much better programmer than I am!), but long term it will be very beneficial. Part of the GIMP 3.0 delay is due to those kinds of set-up work, where it's not immediately visible but will speed up future development.
For the shape tool, I think it'll be fairly quick once vector layers are implemented. At a high level, we'd just need to have some predefined vector layer shapes that users could manipulate. The functionality is there (one example: https://fosstodon.org/@CmykStudent/112063520232390856), the UI would be the sticking point.
I've worked on 21+ year old issues, so I'm well aware of longstanding requests. For instance, I helped to implement built-in editable text outline options - another commonly searched for question about GIMP. The time we spent on that could have been spent on a number of other issues, and fixing each of those issues would have saved time for some users and annoyed others who'd prefer we'd work on something else.
Feedback from more users is always good, and I have watched Photoshop users work with GIMP. The immediate sticking points from those people were multi-selection, NDE, and a full CMYK mode - the text tool wasn't as big of a deal to those particular users as it is for you. That doesn't mean we don't want to make the UX better there, just that certain features are not equally important to everyone.
We also load palettes (ASE, ACO, etc) in CMYK, CIE Lab, etc. It's true we don't have a dedicated CMYK/LAB mode yet, but 3.0's color management work laid the foundation to implement this much easier in a future release.
At the moment, new development is encouraged to follow the GTK3 -> GTK4 migration guidelines (e.g. use gtk_widget_set_visible () rather than gtk_widget_show (), don't use gtk_widget_destroy () since it's been removed, etc). I don't know a specific issue tracking GTK4 at the moment, but I can check.
And I can promise you, non-destructive editing was repeatedly requested by users, not just software developers. I have also seen a large number of users happy about the feature being implemented, as well as videos and screenshots of it being used effectively. It was a net positive in my opinion, even if there's more work to do in addition.
That's not to say your particular issue won't be addressed of course! You're just the first person I've seen to make that specific complaint, compared to the larger number of users asking for more CMYK support, shape tool, built-in Resynthesizer etc. What's been really nice about the RC1 release is that more members of the community are willing to try out 3.0 (compared to the various 2.99 releases) and give feedback. People use GIMP in lots of different ways, and if we don't use it in those ways then we don't see their specific problems.
Not to say that there isn't more work to be done, but I think there's a lot of good work done by volunteers already.
For instance, I worked on non-destructive editing because so many people said it was an essential missing feature that also needed to be there 20 years ago. Now that it's implemented, I've seen a lot of happy people who appreciate it and what it does for their workflow. At the same time, that means there are new requests for the next "essential missing feature". :)
But yes, please test and let us know - we'll be happy to look at it and fix as we can!
Now all pixel data is stored in GeglColor objects, which contain the color model, space, and profile information in addition to pixel values. So you can just request, say, the 8bit CIE LAB or 16bit CMYK version of the pixel and retrieve it from the object.
I made a proof-of-concept CMYK mode for GIMP before this conversion was done - it would be even easier now. I hope to return to it and implement in GIMP proper in a near future release.