Live data from Hacker News

GIMP – 2016 in review

gimp.org

111–120 of 188 posts

Re: GIMP – 2016 in review

#111
post #105
post #90

Earlier quoted context omitted.

> things like the focus always being in the wrong place so I have to use the mouse, or windows being placed over things I need to see But both of these are things that are fixed with Single Window Mode (which it's clear you know about). Complaining about a UI issue that has already been fixed does seem a bit ungrateful. > or having to reselect my font styling every time I retype something Ok, fair enough. That one is…

> But both of these are things that are fixed with Single Window Mode (which it's clear you know about). They aren't entirely gone though. Eg. if I find my chosen font in the font selector, click it or press enter to select it, and continue typing I'll end up with "Nimbus Sans Lsomerandomtext" in the font selection box. Another example - the default shortcut for "Show / hide docks" is Tab, which is also the shortcut…

> Another example - the default shortcut for "Show / hide docks" is Tab, which is also the shortcut to cycle between tools.

Not anymore.

https://git.gnome.org/browse/gimp/commit/?id=52ad5bb2a11e39f...

Re: GIMP – 2016 in review

#112
post #39

Earlier quoted context omitted.

> the GIMP has a more elegant UI GIMP must have come a long way for those words to form a sentence! Not that it was ever necessarily inelegant, but GIMP's reputation has always suffered from a big chunk of it's natural audience being experienced Photoshop users who find the transition jarring, and trash the UI for that reason. Hearing someone praise the interface is a bit unusual, still!

It's as if some of the core GIMP developers and evangelists wear the fact that they have never ever used or know anything about Photoshop and never will as a badge of pride, and they are fanatically dedicated to never sullying themselves by ever even looking at Photoshop or especially listening to any of the complaints from Photoshop users. Any changes to GIMP that make it more like Photoshop, or acknowledgement that…

> Any changes to GIMP that make it more like Photoshop, or acknowledgement that there's anything about Photoshop that GIMP should emulate, are considered anathema.

Not really, no. Whenever people ask us to do smth like what Photoshop does, all we ask back is to explain why it is better. Perhaps you should answer that question every once in a while?

Re: GIMP – 2016 in review

#113
post #39

Earlier quoted context omitted.

> the GIMP has a more elegant UI GIMP must have come a long way for those words to form a sentence! Not that it was ever necessarily inelegant, but GIMP's reputation has always suffered from a big chunk of it's natural audience being experienced Photoshop users who find the transition jarring, and trash the UI for that reason. Hearing someone praise the interface is a bit unusual, still!

Its because GIMP's UI is designed for users that have more traditional Linux style window managers(tiling, focus follows mouse etc.) Whereas most other programs, including the Adobe suite, are designed for the more underpowered window systems in osx and windows. That's why it is painful to use in those environments and environments like gnome which follow a similar design philosophy.

> Its because GIMP's UI is designed for users that have more traditional Linux style window managers(tiling, focus follows mouse etc.)

I think I can safely speak for the team here: no, we don't think much about tiling or f-f-m.

Re: GIMP – 2016 in review

#114
post #17

Why stick with such an old codebase? Wouldn't it just make sense to start a new Rust project with editable shaders. It could have an extensible, clean task-based interface, instead of the antiquated control room with lots of buttons and switches. Or maybe even a dispatcher/server with protocols to send graphic commands from UIs to different image processors.

Try it and find out :-)

Believe me, the stuff The Gimpnhave been doing for over a decade and a half now is not easy, and I can assure you full rewrites never quite go as expected.

Still, I suspect it would be fun for someone to try!

Re: GIMP – 2016 in review

#115
post #74
post #17

Why stick with such an old codebase? Wouldn't it just make sense to start a new Rust project with editable shaders. It could have an extensible, clean task-based interface, instead of the antiquated control room with lots of buttons and switches. Or maybe even a dispatcher/server with protocols to send graphic commands from UIs to different image processors.

I asked an honest question. But it seems a gobject codebase in C must be a delight to work with. And then you wonder why it takes long to implement new stuff.

It might have been an honest question, but so many of us here have seen this sort of thing and the disaster it entails that it's not at all surprising people were downvoting...

Re: GIMP – 2016 in review

#116

Three words why The Gimp isn't taken seriously by anyone who uses Photoshop: "Non-Destructive Editing" [Oh yes. The interface is awful, too]

> The interface is awful, too It's really a shame. As an example, it's been more than a decade and they still haven't fixed the utterly absurd "layer boundaries" system that it has. There's a reason no other image editor does that, and it's because it makes no sense . (To elaborate, every layer in GIMP has a defined "boundary rectangle" which cannot be drawn outside of.)

> they still haven't fixed the utterly absurd "layer boundaries" system that it has

Yes, it's is kinda absurd. And no, it doesn't magically happen. Someone should sit down and actually write the code. It could be you. Or maybe not.

Re: GIMP – 2016 in review

#117
post #105

Earlier quoted context omitted.

> But both of these are things that are fixed with Single Window Mode (which it's clear you know about). They aren't entirely gone though. Eg. if I find my chosen font in the font selector, click it or press enter to select it, and continue typing I'll end up with "Nimbus Sans Lsomerandomtext" in the font selection box. Another example - the default shortcut for "Show / hide docks" is Tab, which is also the shortcut…

> Another example - the default shortcut for "Show / hide docks" is Tab, which is also the shortcut to cycle between tools. Not anymore. https://git.gnome.org/browse/gimp/commit/?id=52ad5bb2a11e39f...

Cool! Despite my whining I really appreciate the past and future efforts to make it better.

Re: GIMP – 2016 in review

#119

Earlier quoted context omitted.

It's as if some of the core GIMP developers and evangelists wear the fact that they have never ever used or know anything about Photoshop and never will as a badge of pride, and they are fanatically dedicated to never sullying themselves by ever even looking at Photoshop or especially listening to any of the complaints from Photoshop users. Any changes to GIMP that make it more like Photoshop, or acknowledgement that…

Its certainly OK for a product to innovate, as GIMP has. But sometimes the differences are gratuitous. That doesn't help with GIMP adoption, because admit it, most folks have some exposure to Photoshop already. Further, GIMP suffers (as many mature products do) from a certain baroque-ness of feature. Its menus and features have grown from someplace less mature, to where they are. And it shows in the clumsy menus that…

> And it shows in the clumsy menus that make sense if you went along for the ride but for a 1st-timer are just confusing.

Would you mind being a wee bit more specific? :)

Re: GIMP – 2016 in review

#120

For those who are more interested in digital painting rather than image editing, I found Krita impressive in its capabilities and progress: https://krita.org I'm just an hobbyist, but I like having FOSS alternatives to Photoshop.

I paint for a living, and I much prefer Krita to Photoshop nowadays. It's really very good. For my purposes it matches Photoshop's features plus more, such as the guides (vanishing point, ellipses etc), symmetrical painting etc. That said, from reading the forums, the dev team seems chronically understaffed to the point that some of them are less than polite to users. This worries me a bit. If anyone has been looking…

> That said, from reading the forums, the dev team seems chronically understaffed to the point that some of them are less than polite to users.

Are referring to threads on BlenderArtists where users regularly give hell to Krita developers? :)

Post reply on HN