Writing a Gimp 3.0 Plugin
51–60 of 177 posts
Re: Writing a Gimp 3.0 Plugin
#52I really want Gimp to succeed. It's a software I've been trying to use since more than 20 years now but the UX is so clunky.... and different than Photoshop. Muscle Memory is a thing. I'm moving my main machine from macOS to Linux (which I also used partially since 20years), moving from a mac mini M1 to a lovely Lenovo M75Q-1 and so far the experience has been great. I'm a (enthusiast) photographer and I have big hop…
I would love Gimp to succeed but Gimp is made by coders for coders (as you might expect from a open source program) and not by visual artists for visual artists. I don’t have a lot of hope. For years I have been using Affinity and it’s been really good, haven’t looked back. Unfortunately it’s not on linux.
I remember CMYK being the most common complaint (after the UI) 20 years ago, too. And at the time the entire GIMP project insisted that you never needed it and RGB was good enough. By coders for coders, indeed.
Re: Writing a Gimp 3.0 Plugin
#53As is tradition, all threads about an open source project must be kicked off with non-contributers putting shit on it unconstructively.
I'd say that "if you don't like it just fork it" approach has dealt way more damage to the reputation of OSS outside of programmer circles than people repeatedly asking for features or improvements.
Re: Writing a Gimp 3.0 Plugin
#54Earlier quoted context omitted.
They could start with a name change.
> They could start with a name change. Yes. Peacock will be fine. It is a wonderful bird.
(It’s also pretty decent. My usual go to for stuff I can’t justify spinning up an Adobe VM for…)
Re: Writing a Gimp 3.0 Plugin
#55Earlier quoted context omitted.
Different focus. Krita is for free drawing, gimp is a photoshop replacement. I do agree they probably would benefit from trying Krita.
I often hear that Krita has a different focus, but does it lack anything that GIMP has? (disregarding obscure features like bell pepper brush)
Re: Writing a Gimp 3.0 Plugin
#56I really want Gimp to succeed. It's a software I've been trying to use since more than 20 years now but the UX is so clunky.... and different than Photoshop. Muscle Memory is a thing. I'm moving my main machine from macOS to Linux (which I also used partially since 20years), moving from a mac mini M1 to a lovely Lenovo M75Q-1 and so far the experience has been great. I'm a (enthusiast) photographer and I have big hop…
Re: Writing a Gimp 3.0 Plugin
#57It’s time for a new name. “gimp” may be semantically correct but it hardly prepares one for a “friendly and powerful graphics editing tool”.
Re: Writing a Gimp 3.0 Plugin
#58Isn’t it time to start providing wasm plugin support in most apps or too early?
Re: Writing a Gimp 3.0 Plugin
#59I really want Gimp to succeed. It's a software I've been trying to use since more than 20 years now but the UX is so clunky.... and different than Photoshop. Muscle Memory is a thing. I'm moving my main machine from macOS to Linux (which I also used partially since 20years), moving from a mac mini M1 to a lovely Lenovo M75Q-1 and so far the experience has been great. I'm a (enthusiast) photographer and I have big hop…
I just want to draw lines and geometric shapes, without having to deal with paths, like in any other sane graphical program. Has this been finally sorted out?
It's a fork of Paint.NET, which happens to be my favorite image editor on Windows. The Mono-based port is a bit flaky and crashes sometimes, but the Gimp UX is just unusable for me, so Pinta it is. I tried gimp many times, but I just end up reading forums and often the program either can't do the small stuff I want, or it takes 5 minutes of clicks.
Re: Writing a Gimp 3.0 Plugin
#60Side question : can an LLM which nas no idea of how to write plugins for Gimp ingest this page (and the links to the C api and Python api) and write code by itself ?