Earlier quoted context omitted.
> But offending people with prudish attitudes or without a sense of humor… Some folks who are neither prudish or humorless want to see the project and its contributors succeed to the degree that alternatives like Photopea has, or as Blender has in the 3D space. The project will continue to limp along until the name is changed to something without negative connotations in English-speaking populations.
You can fork it, rename to something like "Glimpse" and see the adoption skyrocket. Surely the success is just around the corner. Oh wait a minute
Writing a Gimp 3.0 Plugin
141–150 of 177 posts
Re: Writing a Gimp 3.0 Plugin
#142Serious question: Has anyone proficient in Photoshop given GIMP a proper go and come out the other side wanting to use it?
I worked in prepress, so pretty good an Photoshop, and vastly prefer GIMP. The problems with GIMP are technical, there are some necessary things for some jobs that it simply hasn't been able to do, but I'm seeing a lot of work being done on them. The problem with GIMP in industry is 1) that .psd is a standard, and 2) that Photoshop has a bad UI that takes a lot of work to understand well enough to do the very fine wo…
The article is about losing features due to incompatibility of plugins. Perhaps you refer to some more abstract open source concept?
Re: Writing a Gimp 3.0 Plugin
#143I'm patiently waiting for resynthesizer to be ported. Then I will make the move to 3.0. I've used GIMP exclusively as my image editor for the past two decades and it has fulfilled my needs for web development. I really don't get all the gripe around it. It's one of the most valuable free programs on my PC. Sure, it does take time and possibly customization to get yourself a comfortable workflow. But once you get it d…
Re: Writing a Gimp 3.0 Plugin
#144Earlier quoted context omitted.
I worked in prepress, so pretty good an Photoshop, and vastly prefer GIMP. The problems with GIMP are technical, there are some necessary things for some jobs that it simply hasn't been able to do, but I'm seeing a lot of work being done on them. The problem with GIMP in industry is 1) that .psd is a standard, and 2) that Photoshop has a bad UI that takes a lot of work to understand well enough to do the very fine wo…
> it only gains features, never loses them The article is about losing features due to incompatibility of plugins. Perhaps you refer to some more abstract open source concept?
Now that the API is stable for 3.0, we're hoping more people will feel comfortable updating to it.
Re: Writing a Gimp 3.0 Plugin
#145Serious question: Has anyone proficient in Photoshop given GIMP a proper go and come out the other side wanting to use it?
That was my experience 20 years ago. Photoshop wasn't the photoshop of today but neither was gimp.
Re: Writing a Gimp 3.0 Plugin
#146Earlier quoted context omitted.
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.
The few people I know doing visual design still balk at a program that lacks native CMYK editing. Honestly I'm still skeptical about the significant improvements made for 3.0 due to the project's history. 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.
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. :)
Re: Writing a Gimp 3.0 Plugin
#147Earlier quoted context omitted.
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.
It's not made for coders, it's made for the benefit of whomever uses it, and many people use and bundle it as well. I do understand the issues that people are experiencing with it UX-wise, but the answer to that is not that it's being made for coders, it's that it's an open source project, and as such, it has other incentives, than giving the best UX possible. Also, since it's open source and not for-profit, it has o…
Re: Writing a Gimp 3.0 Plugin
#148I 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…
In a recent attempt to use Gimp for a small project, a few features I found were lacking: 1. Viewing the layer boundaries of all layers. Very helpful in seeing the total layout of the project. 2. Select multiple layers and do operations like move/align.
Re: Writing a Gimp 3.0 Plugin
#149I tried 3.0 RC2 the other day and discovered that the new UI is much less space efficient. It imported my panel layout from 2.10 (which I spent a long time getting just right), and I had to completely rearrange it to get it to fit on a 1080px tall monitor. Very frustrating. Also, it doesn't detect my drawing tablet.
Are there specific areas of the UI that are less space efficient? One of the big changes was switching our GUI library to GTK3, which is suppose to scale better on HiDPI screens. But we had to recreate our theming system as a result, so if we need to tweak something we can try.
Re: Writing a Gimp 3.0 Plugin
#150Earlier quoted context omitted.
gimp became way less annoying once i discovered the command pallette (the forward slash key), you can pretty much do everything with it. i even use it to switch tools sometimes sinces its easier than trying to look through all the tool icons or having to long press them
It was easier when the icons had color and were not grouped into multiple tools behind one icon.
In 3.0 it's even easier, as both options are available in the Personalize tab of the Welcome Dialogue. I'm hoping this will help make that feature more discoverable. :)