Slashdot Mirror
The GIMP UI Redesign
sekra writes "The GIMP UI Redesign Team has created a blog to collect ideas for a new design of the most popular image manipulation program. Everyone is free to submit suggestions to be published in the blog. Will a new GUI finally get more users to choose The GIMP as their program of choice?"
I'd be risking more psycho mails in my inbox if I posted under any of my usual accounts, so I'm posting this anonymous, even at the risk of it being modded down as a troll.
GIMP people, the biggest, quickest thing you can do to get good people back in the project and working well together is to finally, please, finally get rid of Carol Spears. I know 80% of you agree with me and have demonstrated in private to me or in public that you want her out, but she's pushing more and more people out with her weird shit, her stalking behaviour, her willingness to criticize anyone contributing to the project for insane reasons like stealing her boyfriend or taking her life from her, or accuzing people of having sex with conference organisers to sway them and obtain cash. Whatever, too many good contributors are sick of it. Yes, she has mental health issues, but the project has suffered too much accomodating those. There is only so much you can do for her.
Taking this public because all the private talking has failed.
The market has spoken. Given that the GIMP does nearly everything that Photoshop does, and costs nothing, but hasn't managed to displace it, then just clone the damn Photoshop UI. It's not a difficult concept.
If you were blocking sigs, you wouldn't have to read this.
Yeah, considering the utter disregard for decent interface design on any level that the GIMP team has shown in the past, I'm not really holding out much hope for this one. Perhaps we'll get a new coat of paint on top of the old interface, but the whole thing will still be a horrid programmer-interface mess.
Or perhaps they will really create a competent design team and let them dictate every detail of the interface. But with the usual open source ego contests, that seems a tad unlikely.
GIMPShop supposedly copies the Photoshop UI. I still didn't like it. For Windows and Mac, I don't think it's competing against the pay version of Photoshop, GIMP is competing against the infringing copies ("free"/"pirated") version of Photoshop.
I don't even think it's about copying the UI. I don't think people mind different UIs, but I think they mind having to use less efficient UIs. I don't think the UI designers for GIMP really thought that one through. I counted the number of steps it took to perform an action for the actions I often use, and Photoshop beat it. That's not even counting the vertical menu thing in GIMP. I don't know how other people are, but for me, moving the mouse cursor side to side is more efficient than up and down, and the vertical menu has just been more irritating than the standard horizontal menu bar, even if the horizontal menu bar drops down to a short vertical menu.
Instead of opening up Photosho.. err, GIMP and cranking out a bunch of comps that are just mashups of existing UI concepts, why not talk to your users and design around their workflow and needs? Good UI is not born in a vacuum, good user experience doesn't happen without talking to users. For an app that seems to have the Rodney Dangerfield complaint, the team around it seems to do little to counter that. (You think Adobe doesn't test the hell out of its apps?)
So, I'll throw one out there, in the interest of PRACTICAL feedback:
Single window mode is a bad idea because it makes a photo retoucher's life much more difficult.
Here's an example why, an actual segment of a workflow and/or task, done in Photoshop to show the ease of this and why multi-window works well.
Grab a picture of a friend, ideally if they are drunk or have blotchy skin in the photo -- make it as unflattering as possible. Wedding pictures are ideal. Needs to be color.
Open it in Photoshop. Now, since I don't have another copy in front of me, this is the CS2 method:
Window>Arrange>Open New Window for [foo.jpg]
Window>Arrange>Tile Vertically
Now center both windows on the same area, ideally, said blotchy skin.
On ONE window, go to the layers/channels/paths palette. Switch to the Channels palette. Turn off all channels except green. Odds are, it looks pretty much like the color photo, just in B&W.
Now take the Clone tool and massage out some of the blotchiness in the green channel ("B&W") version. Ta-da, fixed in both. And you can see its effect immediately.
This is one way that your favorite babes are airbrushed to laughable non-human perfection for magazines. It's quick, it's got incredible feedback, and it's not possible in a tabbed or single window method.
Talking to your users, as opposed to a comp-off (or the cardinal sin, the designer assuming he knows everything), gives you all kinds of useful information like that.
Aimless brainstorming, bad. Brainstorming with a direction, productive.
I am not Herbert.
But doing something remotely practical like that would first require the GIMP developers having to admit they made a mistake; I pointed the mistake out to the developers over 2 years ago and even went so far as to draw mock ups of a new, better gui. I was quickly abused on the irc channel, kicked and then banned. If that is how the GIMP developers react to contributions then they can take their blog, roll it into a tiny roll and cram it.
This is, however, a symptom of a bigger issue; programmers failing to realise that they're programmers and failing to listen to usability people; let the usability experts design the interface - heck, there are tools to allow the separation between the two; then glue them together at the end. Let each team work on the area which they're good at. Admitting your weaknesses doesn't make you a bad person, it makes you an adult who understands what their limitations are.
That's simply not true. Retail versions of CS3 require activation, which discourages the casual pirate. A lot of businesses absolutely will not use pirated software.
If there were a free alternative to Photoshop that did everything Photoshop does as well as Photoshop does it, a lot of people would use it. Photoshop isn't cheap, and it doesn't "come with the computer" (which is how most people get Windows and Office).
There are a couple problems with GIMP. First, it's lacking some things like CMYK support. Also, it gives inferior quality in some cases. I've been in situations, for example, where I really needed to optimize JPEG quality for file size, and GIMP couldn't match the quality of Photoshop. Third, the name "GIMP" rubs professional users the wrong way. And finally, the interface isn't very good.
To anyone who works on the GIMP, I apologize if my post seems offensive. I think the GIMP is a very good program, but the reason professional graphic designers use Photoshop is that Photoshop really is a better program. Not everyone needs Photoshop, but if you do need Photoshop, GIMP might not be a good enough replacement.
QT has it all over GTK+ in nearly everything except programming language portability and the license.
It's far easier to program with and distribute on multiple platforms than GTK or wxWidgets, also.
wxWidget's API is reminiscent of the horrible old Windows API's -- it's just ugly and makes for hideous code, imho. QT is clean and elegant, and the signals/slots mechanism makes thread-safe gui code dead simple.
If moderation could change anything, it would be illegal.