So basically, you could download plug-ins, themes, shortcut presets, etc, directly into GIMP. We have a lot of pieces done - we just need someone to focus on it to finish.
I can't speak for everyone, but as developers we are trying to emphasis UX/UI work more. We have a dedicated repo now for user feedback, designs, and proposed solutions: https://gitlab.gnome.org/Teams/GIMP/Design/gimp-ux/-/issues
We implement from there as we can, once consensus has been reached.
We also highlight UX/UI improvements in each new release post. Just like with coding, we rely on volunteers to help with this (you definitely don't want someone like me deciding on interfaces!)
We have a couple active designers assisting us, but we're always looking for more feedback!
It's funny to hear that, because we get a large number of complaints that we haven't changed GIMP's interface at all from 2.10 to 3.0 and that's why we're "failing".
We try to be respectful of existing users (and again, we get lots of complaints that doing so "holds GIMP back"). If you have some examples of massive changes you've dealt with (and from what version to what version), I'm happy to look into them further.
Please finally implement pie menus, like Blender has had for many years. There have been various pie menu implementations for GTK for decades, and it's always been easy to roll your own if you suffer from NIH so much that you refuse to look at or use anything anyone else has ever done.
I believe GIMP's deep seated NIH syndrome, and refusal to look at or acknowledge anything else, and lack of respect for users' requests and usability itself, are GIMP's actual deep seated problems (which the Blender project so successfully doesn't self-sabotage itself with), and I have no reason to believe it's ever going to change, because it's so deeply baked into the GIMP "culture", if you can call it that.
Photoshop doesn't have pie menus, so if you must, think of pie menus as a way to be even less like Photoshop, if that is what mission drives you instead of usability. But I think your design goals and motivations should focus more on usability and supporting users than simply spiting Photoshop.
But once you finally get tired of spiting Photoshop at the expense of usability, then why don't you finally declare Mission Accomplished, and move on to trying for once to be as good as Blender's user interface and responsiveness to user's needs?
>One example is that Blender embraced the use of pie menus, and Gimp ignored them. The Gimp team is just not open to outside ideas, and gets really annoyed when users of other tools request features from those tools that Gimp refuses to support, and reacts by digging in deeper and clinging to their bad design decisions out of frustration and spite. A really sad culture of NIH and 4Q2.
>In general and with many other things, Gimp could have been so much better and easier to use, but they systematically and spitefully ignored their user's needs and requests about so many things, while Blender did just the opposite, listened to users and improve the user interface and mouse bindings, instead of being stubborn and parochial about it. [...]
>[...] All of these ideas could be applied to Gimp too, of course, but I've found the Blender developers to be much more open to entertaining other people's ideas and contributions about user interface design than the Gimp developers, who have been historically NIH-limited and stubborn (especially about changing the name to something less offensive to the general public). At least Blender already supports pie menus well, and changed the default mouse bindings in response to user demand, and has made huge strides in usability lately. At this point I think it would be much easier to just add a great image editor to Blender, integrated with its video editor, than try to change the minds of the Gimp developers. [...]
Do you happen to have a reference to GTK implementations of pie menus? The challenge we've run into is that newer versions of GTK "streamline" and remove features, so we have to either discard things or build our own replacement (as one example, we've received many complaints about icons no longer appearing in menus in GIMP 3.0, but that was due to the feature being basically removed in GTK3).
We currently have over 13,000 user-requested issues resolved in our issue tracker, so I don't think we're opposed to user requests. :)
I think that's a holdover from an earlier group of developers (there's been a lot of people coming and going in the 30 years that GIMP's been around!). We're also just limited by how fast we can implement certain things due to the number of developers. For instance, I focused on vector layers for GIMP 3.2 - a feature requested by many users! But that meant that I wasn't working on other features requested by other users.
Our release posts now regularly feature a UX/UI section where we highlight the work being done. We've implemented a lot of low-hanging fruit and localized fixes, while we continue to grow our design volunteer group and build larger designs.
There's about 4 more from another event which I'll be working on between coding and other things. There's definitely some material that's a bit dated (for instance, the comment about non-destructive editing), but I think it's still interesting insight into development.
Macros are on the roadmap (https://developer.gimp.org/core/roadmap/#macros-script-recor...), and in fact we did a lot of prepwork for them during 3.0's development (internally, several features like filters and plug-ins now have configs that store settings, which will be used by macros in the future to repeat operations).
I can't speak for GNU Guile, but I wasn't even aware I was in the running for the "Outstanding New Free Software Contributor Award" when I got the email, and I didn't know anyone on the committee. So I don't think there was a conflict of interest.
There's definitely plenty of people out there who were equally deserving of the award!
We've implemented a number of items from the issue posts once consensus was reached, and we hope more people will participate and help improve GIMP further.
If I understand correctly, "omnisearch" would be pressing a button to pull up a box to search through all the menu options? If so, then yep, GIMP's had that for a long time by pressing "/".
Longterm, we have a roadmap item for an Extensions platform: https://developer.gimp.org/core/roadmap/#extensions
So basically, you could download plug-ins, themes, shortcut presets, etc, directly into GIMP. We have a lot of pieces done - we just need someone to focus on it to finish.
reply