News for hackers. Stuff that matters.
Re:GIMP 2.99.18: The last development preview before 3.0 by infotainment on Thursday February 22, 2024 @06:56AM (#39465848)
> Brush tools now have an additional “Expand Layers” option. When checked, painting past the layer boundaries will cause them to automatically expand so you don’t have to manage the layer size yourself. If you want to expand the layer beyond the current size of the canvas, you’ll need to also check the “Show All” option in the View menu.

Seriously GIMP devs, instead of this overengineered solution, just get rid of layer boundaries. There's a reason no other layer-based image editor has them: they make absolutely no sense and are terrible UX.

Re:GIMP 2.99.18: The last development preview before 3.0 by mort96 on Thursday February 22, 2024 @07:11AM (#39465984)
You say "just", but I imagine the idea that layers have boundaries is a deeply ingrained assumption throughout the code base at this point. I would love for layers to not have boundaries, but I think prioritizing it below shipping GIMP 3 with GTK 3 support is correct.
Re:GIMP 2.99.18: The last development preview before 3.0 by __s on Thursday February 22, 2024 @08:24AM (#39466687)
I think their "just" is saying this option should be on by default & mostly hidden
Re:GIMP 2.99.18: The last development preview before 3.0 by xyzzy_plugh on Thursday February 22, 2024 @10:07AM (#39468162)
Indeed, I am pretty sure this is how Photoshop has worked under the hood since forever. No point in persisting a sparse layer.
Re:GIMP 2.99.18: The last development preview before 3.0 by mort96 on Thursday February 22, 2024 @03:28PM (#39472709)
That's not how I read it. The fact that layers have boundaries shows up all over the place in GIMP, turning on "auto expand layers" in the brush tools by default wouldn't do that much to "get rid of layer boundaries".
Re:GIMP 2.99.18: The last development preview before 3.0 by 123yawaworht456 on Thursday February 22, 2024 @07:15AM (#39466027)
I also second this. I've been using GIMP on and off for occasional image editing for about 8 years now, and I still don't really grasp how do layers work in it.

I really wish it had Photoshop compatibility mode for hotkeys and behavior. The former is a very common tweak.

Re:GIMP 2.99.18: The last development preview before 3.0 by madog on Thursday February 22, 2024 @05:18PM (#39474101)
There is PhotoGIMP[1] that copies the hotkeys and tool layout. It doesn't replicate behaviour exactly obviously but it does make it actually usable for me as someone who used Photoshop a lot in the past, and was eternally confused by GIMP.

1: https://github.com/Diolinux/PhotoGIMP

Re:GIMP 2.99.18: The last development preview before 3.0 by tejohnso on Thursday February 22, 2024 @08:11AM (#39466532)
I've found the people who have the biggest problem with GIMP are the ones that have expectations that come from using other image editors.
Re:GIMP 2.99.18: The last development preview before 3.0 by spoiler on Thursday February 22, 2024 @08:24AM (#39466676)
What's wrong with learning from other software in the domain? Especially from ones that the whole industry endorses?

I don't mean to be rude to the work done to make Gimp, but the harsh truth is that Gimp's UX has been a joke for over a decade

Re:GIMP 2.99.18: The last development preview before 3.0 by tambourine_man on Thursday February 22, 2024 @08:42AM (#39466921)
Perhaps because there’s an editor that’s been the industry standard for 30+ years.
Re:GIMP 2.99.18: The last development preview before 3.0 by walteweiss on Friday February 23, 2024 @06:56AM (#39479494)
Who cares about 30+ years at this point? It could be great back then, but right now it’s awful, especially if compared to Pixelmator Pro.
Re:GIMP 2.99.18: The last development preview before 3.0 by tambourine_man on Friday February 23, 2024 @07:45AM (#39479868)
I like Pixelmator for multiple reasons, but it’s a toy next to Photoshop. And so is everything else. There’s simply no competition, unfortunately.
Re:GIMP 2.99.18: The last development preview before 3.0 by walteweiss on Friday February 23, 2024 @10:42AM (#39481952)
What do you mean? In which use case? I use Pixelmator Pro exclusively for years now, and I don’t need Photoshop, it’s just an abomination to me.
Re:GIMP 2.99.18: The last development preview before 3.0 by tambourine_man on Friday February 23, 2024 @11:29AM (#39482693)
For professional image editing. Printing, advanced retouching, photomontage, etc.

If you just need to crop, erase a pimple or a coke can on the floor, basically anything will do.

Pixelmator doesn’t even support CMYK editing, it only exports in it. It’s not even in the convention for serious image workflow.

Re:GIMP 2.99.18: The last development preview before 3.0 by kookamamie on Thursday February 22, 2024 @09:01AM (#39467163)
> expectations that come from using other image editors

Or have expectations that...make sense? The way GIMP represents layers is unintuitive, at best.

There are some de-facto tools (Adobe Photoshop, etc.) that have paved the way for intuitive UX in this space - no need to re-invent the wheel in areas that are well-established by now.

Re:GIMP 2.99.18: The last development preview before 3.0 by mmis1000 on Thursday February 22, 2024 @11:19AM (#39469306)
Even editor like photoimpact which appears about 20 years ago works almost the same way about the draw layer. You just draw anywhere on the whole canvas, that's it.

And if you want something that has specific size and resizable and can be placed out of canvas. Use object instead.

Why would gimp even resist to make draw layer that have specific size at first place?

Re:GIMP 2.99.18: The last development preview before 3.0 by i_am_jl on Thursday February 22, 2024 @09:03AM (#39467200)
Giving someone a nail gun makes them question why they've been banging nails into wood with their forehead for so long.
Re:GIMP 2.99.18: The last development preview before 3.0 by Joeboy on Thursday February 22, 2024 @09:04AM (#39467209)
Do you know people who do professional level image editing in GIMP and have never used another image editor?
Re:GIMP 2.99.18: The last development preview before 3.0 by brnaftr361 on Thursday February 22, 2024 @09:05AM (#39467219)
Homogenizing expected behavior is a pretty good idea, it allows open source software to compete at a commodity level instead of a principle or fundamentals level - which considering the open source position would make a pretty good deal of sense as quite a lot of it is free, e.g. GIMP, Inkscape...

Hypothetically if GIMP just copied the photoshop UI and expected behavior a lot of tutorials for PS translate directly making GIMP accessible, which ultimately plays to the favor of GIMP as it is more accessible in that it's open source, free, and doesn't require subscription or accounting.

Also since GIMP is decentralized and volunteer-ran it'd be interesting to see exactly what Adobe would do about it, if they could even do anything.

Something else that would be nice to see from the open source community would be standardization in the control schema across software. For instance I use Blender a lot, but I also use Inkscape, and jumping between the two is... Less than pleasant because there's a pretty significant amount of overlap, but none of it is able to be homogeneous as there is some hard coding that a keymap alone doesn't allow for convergence.

Re:GIMP 2.99.18: The last development preview before 3.0 by pennomi on Thursday February 22, 2024 @09:15AM (#39467343)
As a concrete example, when Blender finally made left click the default selection button (in harmony with virtually every other 3D software out there) it made the learning burden much, much easier for new users to shoulder. This, combined with many other UX improvements have made Blender possibly the most popular 3D software out there today, instead of the weird choice.
Re:GIMP 2.99.18: The last development preview before 3.0 by mixmastamyk on Thursday February 22, 2024 @11:52AM (#39469760)
Almost every program, not just 3D. In fact 3D apps are more likely to be custom instead of standards based.
Re:GIMP 2.99.18: The last development preview before 3.0 by Gormo on Thursday February 22, 2024 @09:44AM (#39467817)
> Homogenizing expected behavior is a pretty good idea, it allows open source software to compete at a commodity level instead of a principle or fundamentals level

That applies if your only goal is to create FOSS software that competes head-on with proprietary applications, so that being FOSS is the only differentiator.

But obviously, this isn't always applicable as a general principle. If you want to enable new functionality and support new use cases, where there are a variety of approaches or trade-offs, and conventions aren't well-established yet, you probably shouldn't presumptively conform to an a priori monoculture.

> Less than pleasant because there's a pretty significant amount of overlap, but none of it is able to be homogeneous as there is some hard coding that a keymap alone doesn't allow for convergence.

This is a great counter-example, where adhering to well-established conventions for problems that are already solved is advisable. There's been a lot of divergence in UI design recently, with lots of applications moving away from decades-old standards for purely aesthetic reasons, and creating huge usability regressions in the process.

Re:GIMP 2.99.18: The last development preview before 3.0 by drivingmenuts on Thursday February 22, 2024 @09:12AM (#39467295)
You want me to use a Unimog to haul groceries, when a Rabbit will do just fine?
Re:GIMP 2.99.18: The last development preview before 3.0 by rkachowski on Thursday February 22, 2024 @09:36AM (#39467679)
people who have experience using image editors will have the biggest problems with GIMP?
Re:GIMP 2.99.18: The last development preview before 3.0 by walteweiss on Friday February 23, 2024 @06:58AM (#39479507)
I can confirm, the first focus of Gimp must be the UX (which could be just cloned at this point), and the rest is not so bad to my liking. Right now Gimp is just unusable for anything serious.
Re:GIMP 2.99.18: The last development preview before 3.0 by bemusedthrow75 on Thursday February 22, 2024 @09:37AM (#39467699)
From using _all_ other image editors, you mean.

And that is the problem. People who have learned tools from what is now an established, multi-editor, digital medium, find they can't do what they wish to do.

I suspect very few even try to make this jump anymore.

GIMP still requires artists to think about and develop their workflow in the sequence that works best for GIMP.

Waving them away like this is a mind trick that the GIMP community should simply ban outright; it's devastating.

(Unless you mean this satirically and it's just gone over my head)

Re:GIMP 2.99.18: The last development preview before 3.0 by mixmastamyk on Thursday February 22, 2024 @11:50AM (#39469727)
I learned on paint shop pro and never had substantial problems with gimp.
Re:GIMP 2.99.18: The last development preview before 3.0 by kstrauser on Thursday February 22, 2024 @09:44AM (#39467815)
I’ve used Photoshop for like an hour total in my life. I have no ingrained love for it whatsoever. I’ve used GIMP quite a lot over the years, and I’m used to it.

Mac is blessed with several fantastic image apps. After using Pixelmator Pro for 5 minutes, I bought it. It does all the things I’ve wanted in GIMP, but I can figure out how to use it without hitting Google.

For example, can a mortal draw a circle with GIMP now? Up through the last time I used it, you had to select an ellipse (and hold down ctrl or something to constrain that ellipse to a circle), then stroke it as a path. In other apps, you choose the shape tool, and plop down a circle. While it could be that there was some esoteric case where GIMP’s weird process was nifty, it was markedly worse than everything else in the 99.9% of cases where you just wanted a circle.

For me, it was never that it wasn’t a Photoshop clone. I couldn’t care less about that. It’s that it was almost deliberately obtuse in ways that no alternatives were.

Re:GIMP 2.99.18: The last development preview before 3.0 by reddalo on Thursday February 22, 2024 @07:41AM (#39466231)
I still don't get it: what are layer boundaries?
Re:GIMP 2.99.18: The last development preview before 3.0 by rcxdude on Thursday February 22, 2024 @07:57AM (#39466400)
Layers in GIMP can be smaller than the image they are part of. So if you try to edit a layer outside of it's boundaries you don't get anything. Pretty much all editors do this as an optimisation (no point storing an entire layer if it's almost entirely empty transparent pixels), but GIMP is unusual in exposing this to the user and expecting them to increase the layer size manually. In other editors the layer is conceptually the full size of the image and these boundaries are managed automatically. (In fact, usually the layers are unbounded in size and can expand to be larger than the canvas. Very useful if e.g. you are importing a background image and want to be able to shift it around a bit)
Re:GIMP 2.99.18: The last development preview before 3.0 by simcop2387 on Thursday February 22, 2024 @08:25AM (#39466697)
Not just smaller, but you can even have them be larger than the image. Then you can move the layer around and have the image essentially acting as a cropping window into that layer. I most commonly experience that when I've imported/pasted in a larger image as a layer
Re:GIMP 2.99.18: The last development preview before 3.0 by beezlewax on Thursday February 22, 2024 @04:49PM (#39473763)
They can be larger than the image in photoshop etc too
Re:GIMP 2.99.18: The last development preview before 3.0 by timeon on Thursday February 22, 2024 @09:49AM (#39467888)
Nice solution would be having this boundary stretching automatically as proposed in this thread but also exposing 'bounded layers' as separate tool like frames in Indesign.
Re:GIMP 2.99.18: The last development preview before 3.0 by kookamamie on Thursday February 22, 2024 @09:02AM (#39467179)
Don't worry, no one gets them.
Re:GIMP 2.99.18: The last development preview before 3.0 by spoiler on Thursday February 22, 2024 @07:05AM (#39465926)
I second this. If someone really wants to add a boundary, they can use either a mask or selection
Re:GIMP 2.99.18: The last development preview before 3.0 by FreeFull on Thursday February 22, 2024 @07:24AM (#39466094)
How would that work for having a layer larger than the image?
Re:GIMP 2.99.18: The last development preview before 3.0 by beAbU on Thursday February 22, 2024 @07:28AM (#39466128)
The layer is automatically masked by the boundaries of the image. This is how it works in most other layer based tools that I've seen.
Re:GIMP 2.99.18: The last development preview before 3.0 by dijit on Thursday February 22, 2024 @07:35AM (#39466184)
Isn't this a severe limitation of rasterized image editors?

(Speaking from ignorance as someone who only did some mild graphics design work using fireworks in the mid-00's for forums).

Would it mean that anything that exists outside of the visible canvas would be cropped on save?

Re:GIMP 2.99.18: The last development preview before 3.0 by beAbU on Thursday February 22, 2024 @07:59AM (#39466406)
This depends on the image editor you use. I'm pretty sure that PS saves whatever is on the layer, even if it's extends past the boundaries of the image itself. At any time you can open the file, and move the layer and get access to whatever was masked off.

If you "flatten" the layer, then you might lose what's beyond the boundaries.

Re:GIMP 2.99.18: The last development preview before 3.0 by bennettbackward on Thursday February 22, 2024 @07:40AM (#39466227)
Not if you're saving to the GIMP project file format. You'd lose it if you saved to a raster image but you'd also lose layers, vectors, etc. too.
Re:GIMP 2.99.18: The last development preview before 3.0 by dijit on Thursday February 22, 2024 @08:01AM (#39466436)
Sorry, more stupid questions then.

> Not if you're saving to the GIMP project file format.

Ok, but if I understood correctly we're asking GIMP to remove code paths that have different layer boundaries, so that would surely affect GIMPs project file format?

Re:GIMP 2.99.18: The last development preview before 3.0 by blkhawk on Thursday February 22, 2024 @07:46AM (#39466301)
wait GIMP does vectors now? I hope you don't mean that stupid useless plugin that renders to a bitmap layer and you can't adjst again afterwards? Or has that improved while I wasn't looking?
Re:GIMP 2.99.18: The last development preview before 3.0 by woodrowbarlow on Thursday February 22, 2024 @08:06AM (#39466476)
curves and text are vectorized. most tools/effects can't be used on vector layers unless you rasterize them.
Re:GIMP 2.99.18: The last development preview before 3.0 by blkhawk on Thursday February 22, 2024 @08:10AM (#39466519)
going to try again when I get home - would be so nice to just click and adjust text when its not quite the right size or position. I hope I can draw vector line as well. that was actually something that drove me almost batty once before I installed an old PSP9 in wine and used that instead. I needed to adjust thesize and position of several lines in relation to each other and i was unable to do that even with that stupid plugin.Using 1 layer per line would have worked but I though that was a bridge too far at the time.
Re:GIMP 2.99.18: The last development preview before 3.0 by woodrowbarlow on Thursday February 22, 2024 @09:03AM (#39467195)
text has definitely gotten better. i remember when text could not be modified (as text) after initial creation -- but this has been fixed quite some time ago.

also, paths and text can be exported to svg format, but i still wouldn't call gimp a suitable editor for rich vector graphics. the vector features are more just a means to a (rasterized) end.

Re:GIMP 2.99.18: The last development preview before 3.0 by philsnow on Thursday February 22, 2024 @05:01PM (#39473920)
I was recently trying to make text along a path in Gimp and holy hell is it weird.. you create a text object, then create a path and with the path selected, right click the text object layer and choose “text along path”, and then you have to “stroke path”, IIRC.

But what that does is renders some kind of object (don’t recall if it’s rasterized or what). If you later notice a typo, or want to change the font, font size, or path a little bit, you have to throw away the rendered object, make your changes to the text object (hope you kept it as a hidden layer or something!), and then re-render and re-stroke it.

I’m glad I was working on something for fun (bottle label) and that I didn’t particularly care about the end result.

Re:GIMP 2.99.18: The last development preview before 3.0 by p0nce on Thursday February 22, 2024 @08:48AM (#39466996)
I could live with that.
Re:GIMP 2.99.18: The last development preview before 3.0 by garaetjjte on Thursday February 22, 2024 @08:43AM (#39466931)
When I paste other images as layers I don't want boundaries to be automatically lost.
Re:GIMP 2.99.18: The last development preview before 3.0 by Joeboy on Thursday February 22, 2024 @08:51AM (#39467036)
Not a fan of "this" comments but, very much this. The way layer boundaries work in Gimp is tremendously confusing and annoying.

Perhaps the existing code makes it difficult, and I get the impression the devs have been stuck dealing with other tech debt for a long time. But this should really be high on the list of things to address.

Re:GIMP 2.99.18: The last development preview before 3.0 by roelschroeven on Thursday February 22, 2024 @10:43AM (#39468743)
I honestly don't see the problem with layers that have boundaries that are independent from the image boundaries. Maybe it's because I learned my way around Gimp before I used any other image editor, but it makes perfect sense to me.

When I crop, resize, move, ... a layer, its boundary is cropped, resized, moved, ... accordingly. What happens if you move a layer without boundaries, like in Photoshop? That's probably intuitive to people who are used to Photoshop, but not to me. What happens to contents that now fall out of the image boundary?

To explain layers in raster image editors to novices, they are often compared to transparent slides. Well, layers with boundaries are simply such slides. If I move a slide, the slide moves, including its boundaries; same with other operations.

Re:GIMP 2.99.18: The last development preview before 3.0 by walteweiss on Friday February 23, 2024 @07:02AM (#39479532)
Yeah, except it’s not slides. It’s a virtual canvas and there is no reason in the whole world for it to behave like it’s something physical, when it’s not. It makes zero sense, there shouldn’t be any checkbox in the first place. Just make it how it should be and never ask me. There’s enough checkboxes already. How can you develop a tool for designers if you never ask them first?
Re:GIMP 2.99.18: The last development preview before 3.0 by aaroninsf on Thursday February 22, 2024 @12:34PM (#39470339)
I genuinely don't understand why the solution this layer-boundary BS is not to just default the layer boundary to the image boundary, or the contents of the layer, whichever is larger, always, done and done.

What am I missing?

I don't care if it's "efficient," we're talking about environments which have orders of magnitude more resources and efficient disk caches and god knows what else. It's nearly 2025.

Re:GIMP 2.99.18: The last development preview before 3.0 by philsnow on Thursday February 22, 2024 @05:02PM (#39473931)
I found myself just liberally doing “layer to image size” all over the place and was generally happier after doing it.
Re:GIMP 2.99.18: The last development preview before 3.0 by moomoo3000 on Thursday February 22, 2024 @12:53PM (#39470632)
One idea: Layer boundaries could be disabled by default. If you open an image that uses layer boundaries, they would be enabled for that image.
Re:GIMP 2.99.18: The last development preview before 3.0 by zdimension on Thursday February 22, 2024 @05:35PM (#39474279)
I've read the whole thread of comments and I'm really confused. For context I'm a long time GIMP user and used Photoshop a few times at a very basic level.

Layers having boundaries feels... obvious to me? Like, when I scale a layer, the boundaries are what I'll be scaling. When I crop a layer, I'm cropping the boundaries. If I have a large image and insert a small icon in the middle, should the icon's layer take the full size of the canvas? What exactly is supposed to happen if I insert an image that's larger than the canvas?

A layer in GIMP having boundaries is equivalent, to me, to a shape in Inkscape having a size.

Re:GIMP 2.99.18: The last development preview before 3.0 by Joeboy on Thursday February 22, 2024 @09:56PM (#39476425)
For example, does it not seem intuitive to you that it should be possible to take a brush tool and paint on the canvas? In GIMP, you can usually do that, but sometimes you can't, for reasons that are initially baffling. Once you figure out it's to do with layer boundaries it becomes merely annoying and frustrating. Once you get used to doing "Layer to image size" things get a bit easier, but needing to a) know that and b) constantly do that is not a useful feature.
Re:GIMP 2.99.18: The last development preview before 3.0 by zeroimpl on Saturday February 24, 2024 @12:38AM (#39489403)
There’s several things which break down if you eliminate layer boundaries.

Can you still have a layer that is bigger than the image boundary, or would pixels get cropped when they move outside?

What happens if you apply a noise filter? Does it generate an infinitely large layer with noise? Or only generates noise on the visible portions? Or some other arbitrary rect in between?

And how would you handle the case of a small layer with a weird blend mode like multiply/subtract? With no boundaries it now must apply to the entire image below.

I’m sure there are solutions to these individually but it’s clearly a very complex problem to solve all these kinds of cases in an intuitive way.