Slashdot Mirror


Instrumented GIMP To Identify Usability Flaws

Mike writes "New users of the GIMP often become frustrated at the application's unwieldy user interface. Now Prof. Michael Terry and a group of researchers at the University of Waterloo have created ingimp, a modified version of the GIMP that collects real-time usability data in order to help the GIMP developers find and fix its usability problems. Terry recently gave a lecture about ingimp and the data it collects. During each session, ingimp records events such as document creation, window manipulation, and tool use. A log of these events is sent to the ingimp server for analysis. The project hopes to answer questions such as 'What is the typical monitor resolution of a GIMP user?' and 'Is the GIMP used primarily for photo editing or drawing?'"

416 comments

  1. representative ? by tregetour · · Score: 4, Insightful

    I like the idea, but will the folks who use ingimp be at all representative of the user population at large? ... Especially of the user population that would complain about accessibility / usability. Is it worth it or is anyone talking about making such a thing an integral part of any project?

    --
    take it easy, but take it.
    1. Re:representative ? by NumaNuma · · Score: 4, Interesting

      This poses interesting questions. Those who are integrated enough to be willing to engage in the ingimp project are very likely to have differing behaviors or preferences. Additionally, one of the chief complaints people tend to have about usability is the inability to do something. By looking at the behavior of actions rather than desired actions, those actions which are easy to do in the current iteration will be seen as more desired, rather than simply more accessible. Meanwhile, those actions which are difficult to preform due to actual problems with the interface will be more likely to be overlooked.

    2. Re:representative ? by jeevesbond · · Score: 5, Interesting

      I like the idea, but will the folks who use ingimp be at all representative of the user population at large? ... Especially of the user population that would complain about accessibility / usability.

      My wife does Web design for University of Waterloo and she's always moaning about the usability of the GIMP. I too am more into design than development these days, so that makes two people who're--more or less--ideal for the task.

      Not to mention we have both customised our GIMP's to look and behave more like Photoshop (the missus was fiddling with the keyboard-shortcuts for ages). It seems this data should be collected in this project, as I doubt we're the only ones who've changed everything to our tastes, the developers should finally realise what people want in an image editor.

      On a related, by tangential, note: GIMP's new core (GEGL) seems to be nearing completion, with that comes all the things people have been clamouring for. Such as non-destructable layer effects, CMYK etc. If they fix the usability and shift to GEGL as the core of GIMP it might finally become the Photoshop killer we've all been waiting for! Failing that Krita is coming along very well as an image editor, it lacks a few features, but is far more usable than the GIMP.

      Overall, I don't think anyone should be saying: 'year of the Linux desktop!' just yet. But this is definitely a step in the right direction. :)

      --
      I'm going to transform myself into a mighty hawk. Either that or I'll just go and work at Dixons, haven't decided yet.
    3. Re:representative ? by Soulfry · · Score: 5, Informative

      Because involvement in human-subjects research is voluntary, there will always be a self-selection bias. However, we can still estimate the representativeness of the population by understanding the types of people likely to download and install ingimp, and those who are not. If you fall in the latter camp -- you'd never want to use ingimp -- we really want to talk to you. Send us an email at the email address given on the site: http://www.ingimp.org/contact.

      In any case, having some data is better than having no data at all. Currently, there is a very active and vibrant group of individuals working on GIMP usability issues (see http://gui.gimp.org/ ). ingimp's data complements this other data to help quantify the ubiquity of behavior/activity/computer hardware setups in the wild.

      Michael Terry

    4. Re:representative ? by jddj · · Score: 1

      Maybe a bigger problem will be that you can't instrument what GIMP doesn't do: CMYK, Color Management, look/work just like the industry standard...

      I'm delighted to hear they're trying, but many well-funded programs have become yet-another "not Photoshop". Don't hold your breath for world GIMP-domination.

    5. Re:representative ? by tknd · · Score: 3, Informative

      Anything is better than nothing.

      But even just by examining a few users, you will learn a lot. We went through this exercise in an HCI course I took. We were divided into groups of 4 students and we were required to observe 4 students (no in the class) while they used predetermined website they had never seen before (usually small online stores selling furniture). The total man-hours in the assignment would have been 1 hour pre-user * 4 * 4 observers = 16 hours. The operations were simple: find a bed and matching night stand, find 4 chairs and add them to the cart, etc.

      With only 16 hours of work and 4 subjects it was immediately obvious that there were significant flaws and things that could easily be fixed. For example, there were many times where the user sat there and stared at the screen because they were trying to figure out how to do what they wanted to do.

      I imagine with this GIMP project you could do two things: collect data about users of gimp (distributing the tool to anyone) and hand selecting users of the tool and examining the results on a case by case basis. That should provide a wealth of information.

    6. Re:representative ? by jedidiah · · Score: 1

      Not everyone is interested in a free copy of Photoshop.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:representative ? by Rei · · Score: 4, Interesting

      As someone who began using GIMP before using Photoshop, I find Photoshop's interface to be awkward and GIMP's to be natural.

      Given that a significant majority of people who use GIMP probably used Photoshop first, I wonder what percentage of "moaning about the usability of the GIMP" comes from simple acclimation to a different way of doing things? I'd be interested in seeing the results of introducing one group of people who haven't done any digital graphics work before to Photoshop, another group to GIMP, and seeing how long it takes them to feel comfortable and learn the ropes. Then, you'd have them switch tools and see how well they adapt.

      As it stands, I think we're seeing a lot of selection bias.

      --
      South Park pokes fun at sacred cows to make a point. Family guy pokes cows to hear them moo.
    8. Re:representative ? by Lumpy · · Score: 4, Insightful

      As a person that uses both daily the ONLY part of gimp I dont like is the same crap that all other software pulls.

      From version to version ,dont change where a function or item is. They moved the lighting effects all over the fricking place. and every new version seems like it's a damned easter egg hunt.

      Photoshop does NOT change locations of things very often. (V4.0 compared to V8.0(cs) does have some different locations but not many)

      it's what pisses off every windows user when a new release comes out. "where did they hide function "XXXXX" this time!

      After using a new version of gimp for a few days, it's as usable as Photoshop. Some people lose their mind when they have to do different things in similar apps, I dont. It's like my wife who cant drive the Ford because the wiper controls are different from the GM. I find it entertaining.

      --
      Do not look at laser with remaining good eye.
    9. Re:representative ? by giorgiofr · · Score: 3, Insightful

      Not really. GIMP does everything differently than any other app I've ever used. It doesn't take long to understand that THIS is GIMP's main UI-related problem. All they need to do to fix that mess is design the UI so that it is similar to every other app out there - single window, one menu with all the commands and a few toolbar, you know the drill. Dump GTK while they're at it.
      So no, I don't think this is a case of selection bias - it's pretty clear to anyone who's used it that GIMP is simply the odd one out. I have quite a few other peeves with GIMP but those *do* stem from my own habits rather than the app's design flaws, so I won't comment on them.

      --
      Global warming is a cube.
    10. Re:representative ? by jeevesbond · · Score: 2, Insightful

      As it stands, I think we're seeing a lot of selection bias.

      Agreed, to an extent. There are several things very wrong with the GIMP, such as layer sizes, the multiple windows, the vast amount of screen real-estate (unless you put everything into one panel like I have), the number of tools that should be merged into one, the brush sizes, needing to go through 10 dialogues just to save a png (or some format other than xcf), the transformation tools mess the image up if used more than once, the obfuscated way to add the alpha channel.

      Those are just things that come to mind after just a cursory glance around the GIMP, am sure there are many more. Most of these are not problems if you know how to deal with them, but for a new user (or someone coming from Photoshop) they're annoying and counter-intuitive. That's not to say Photoshop isn't counter-intuitive in many ways, but using Photoshop as an excuse is a little like saying you didn't do your homework at school because your friend didn't: it's not going to wash with the teacher and, in the world of software, it isn't going to grow your market share (granted this is secondary, but what's the point of creating FLOSS software if no-one uses it?)

      --
      I'm going to transform myself into a mighty hawk. Either that or I'll just go and work at Dixons, haven't decided yet.
    11. Re:representative ? by Solra+Bizna · · Score: 4, Informative

      The 'G' in GTK stands for "gimp," FYI.

      -:sigma.SB

      --
      WARN
      THERE IS ANOTHER SYSTEM
    12. Re:representative ? by Ucklak · · Score: 1

      Hear hear!

      Those who wouldn't pay for Photoshop(TM), wouldn't use CMYK therefore have no need for Photoshop(TM).
      GIMP would do just fine.

      --
      if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
    13. Re:representative ? by LinuxRulz · · Score: 1

      I totally agree with you. I use Gimp since I have a computer and I've seen it evolve. I can say I absolutely hate when they move functions in menus. Add to that the fact that I sometimes have to use a translated version of gimp and that the functions translated names are anything but what I would expect. So when I'm on another system than mine I end up not only searching for a function, but also trying them one by one to see the fun name they decided to give it. So maybe that study in quest for a better GUI is done with the intent of making it easier to use.

      Please, to all gimp developers, stop mixing all the menus and giving them strange unintuitive names.

    14. Re:representative ? by YnR · · Score: 1

      I agree with you. I also doubt GIMP users are in general your standart user. I also doubt Slashdoter are also in that category (which does not mean they wouldn't like a well designed GUI). That being said, I have seen my little sister use GIMP quite easily and being totally unable to use Photoshop. I, on the opposite, find Photoshop easy to use and its shortcuts and interface coherent with the current interface paradigms. I have tried a couple of times to switch to GIMP but ended up in tears of frustrations. Maybe there is not a better GUI, but just different paradigms, and that's pretty good if you ask me, keeps each other on their toes (Though I doubt Adobe feels very threatend by GIMP). That being said, loggers of interfaces are not particularly new. Usabilty studies and research have been using them for years. The question is really not about the log, but about how to use the data. I am sure they have more tricky questions than just finding what resolution people use (which could be more easily found that using a dedicated logger). I am wondering how a tool like WMTrace could also help them see the broader picture, like how GIMP works in collaboration with other software, but also windows layouts, pointing load on interfaces, etc.

    15. Re:representative ? by aztracker1 · · Score: 1

      I started out with Photoshop, but then I started using Paint Shop Pro fairly early on... I didn't like the v10 release (post-corel buyout) and haven't tried v11 yet... just the same, I tried gimp around the same time, and a few times since, and to be honest, of the three i find psp the most usable (v9 that is)... this is just my opinion though... I tend to try different things, and use the one I like, or that suits my needs the best...

      To be honest, of the three imho gimp is the worst, and photoshop is a bit overloaded as well.. I still need to try the latest release of ps though... And haven't tried elements version at all... I am just hoping that it moves in the right direction... If you have access to a windows pc with .net installed Paint .Net is actually moving in a pretty usable and innovative direction, and much faster than GIMP has taken to get where it is...

      --
      Michael J. Ryan - tracker1.info
    16. Re:representative ? by humansize · · Score: 1

      But even just by examining a few users, you will learn a lot. We went through this exercise in an HCI course I took. We were divided into groups of 4 students and we were required to observe 4 students (no in the class) while they used predetermined website they had never seen before (usually small online stores selling furniture). The total man-hours in the assignment would have been 1 hour pre-user * 4 * 4 observers = 16 hours. The operations were simple: find a bed and matching night stand, find 4 chairs and add them to the cart, etc.


      The key to what you said was "...observed 4 students..." by reporting back all the clicks, movements, etc, you are not observing, you are interpreting data.

      Intent of the user is key to usability. You can not get intent from this data. What you can get is what the user actually did. Maybe they did not intend to cancel the dialog box but they did since they where expecting the buttons to be reversed.

      The only way to get at intent in through observations. You can learn a lot from observations and usability testing a lot faster and cheaper then trying to instrument up an entire application.

    17. Re:representative ? by PitaBred · · Score: 1

      1) Just because it's the way Photoshop does it doesn't mean it's right. I hate MDI applications with a passion. They're a bad design, period.

      2) The point of creating FLOSS is to scratch the developer's itch, and hopefully help other people along the way. Notice the order I put those priorities in. I don't want market share for my apps, I want them to do what I expect them to do, and solve my problems for me.

    18. Re:representative ? by Celeron1point2ghz · · Score: 2, Informative

      I thought the 'G' in GIMP stood for "GNU".

    19. Re:representative ? by NMerriam · · Score: 3, Insightful

      As it stands, I think we're seeing a lot of selection bias.


      Well, selection bias against anyone who has ever used other computer programs, not just image editors. I don't know of many computer users who are accustomed to having a program with 12 different windows that doesn't even have a single document open.

      If they want to create a new, more intuitive UI from scratch, then do it. Don't steal icons, toolbars, and palettes from Photoshop and then cry that it is unfair when people are baffled that it doesn't behave even remotely like Photoshop. There have been lots of successful image editors in the past 20 years that used different metaphors and tools and layouts and methods than Photoshop does. People don't universally complain about the horrible UI of Paint Shop Pro or iPhoto or MS Photo Editor or Lightroom or Aperture (or Photostyler or Live Picture or...).

      People complain about the GIMP UI because it is a horrific example of what happens when programmers design interfaces, not because they're trained monkeys who can't operate anything but Photoshop.
      --
      Recursive: Adj. See Recursive.
    20. Re:representative ? by eternalnyte · · Score: 3, Interesting

      I really can't be the only one that absolutely loves GIMP's UI.. can I? Everyone that seems to have a problem with it is always saying the same thing.. "It should look like Photoshop", "It should feel like Photoshop", heck "It should be Photoshop". Personally I hate applications with one big monolithic window.. they always tend to then have encosed sub-windows that you cannot pull out of the main window, this drives me crazy when using a multi-monitor display. GIMP is a godsend for allowing me the flexibility to place all my tool dialogs on one monitor, in the locations I prefer (and it remembers them between sessions!), then have a maximized editor window on another (which saves sooo much "zoom in" "zoom out" time due to the more efficient real-estate usage).

    21. Re:representative ? by Anonymous Coward · · Score: 0

      Windows user?

      The multiple window approach is not really a problem on a Linux machine. It's actually even better on a Mac - the Mac version of PhotoShop uses the exact same layout. The only reason the Windows version of PhotoShop uses MDI is that Windows has absolutely terrible window management, while X has pretty good window managers, and MacOS has great window management.

      It may be an odd approach on a Windows machine, where every application assumes it's the most important of the system, and that it's always going to be running in a single window taking up the entire screen, because managing smaller windows on Windows is too bloody hard (again, easy on Linux or MacOS). Lots of Linux and Mac applications behave in a similar way.

      Similarly, GTK is only an issue on Windows. On Linux, where the GIMP originates and where the majority of it's developer and user base are, GTK is one of the two standard toolkits.

    22. Re:representative ? by eternalnyte · · Score: 3, Informative

      It does, GNU="GNU's Not UNIX", GIMP="GNU Image Manipulation Program", GTK="GIMP Tool Kit". IE, they can't really "drop GTK", GTK was created for GIMP!

    23. Re:representative ? by kiddygrinder · · Score: 1

      I'd say at least 80% of the moaning about gimp usability is ex-photoshoppers. I'd say it's just a symptom of an actual real life problem with gimp; it's not easy to configure. Imagine how much better it would be if there was a menu option somewhere that basically said "imitate photoshop" (for the ex-photoshoppers) and a couple other layouts that are more like other application styles. I don't even know what all this arguing is about really, people struggle with different things, why not give a couple of choices?

      --
      This is a joke. I am joking. Joke joke joke.
    24. Re:representative ? by Azuma+Hazuki · · Score: 1

      "Dump GTK?" You *do* know what GTK stands for don't you...?

      --
      ~Eien no Inori wo Sasagete~ Searching for my Hatsumi...
    25. Re:representative ? by evanbd · · Score: 2, Insightful

      So? Are you arguing in favor of Not Invented Here? I have no idea whether there are other widget toolkits out there that are enough better than GTK to warrant switching, but if there are, the fact that GIMP created GTK in the past when those toolkits weren't around is not an argument in favor of keeping it.

    26. Re:representative ? by Skye16 · · Score: 4, Insightful

      But when you're NOT using a multimonitor display, it's a fucking nightmare trying to arrange things in a useable, friendly manner.

      My main "this is fucking stupid" remark is the irritation at having menus for each of the little sub windows. I can handle saying "File->New" on the tool palette, if I absolutely must, but everything fucking else is just wrong, wrong, wrong. Gimp is the ONLY application that EVER does things this way; the only reason I want "Gimp to be like Photoshop" is because at least Photoshop follows the same fucking UI paradigm as the rest of the god damned operating system (or desktop environment). From my novice->intermediate usage of Linux over the years (i.e. I feel comfortable I can install and get Linux to do whatever I want, but it still takes a while sometimes), I haven't found a single fucking program that does similar things to Gimp. I'm not saying they don't exist - I'd be astonished if they didn't, but I am saying the fact that MOST don't work that way is an utterly confusing lack of consistency. If Gimp is so tightly coupled with GTK, and one would assume, Gnome is pretty tightly related to GTK, then you would THINK that consistency across Gnome applications (at least those that come bundled with the vanilla Gnome release) would be pretty in tune with each other. I've not yet seen that to be the case.

      That is what irritates me. Gimp will always be an easter egg hunt for me; I only use it at work since I don't have a ripped off version of Photoshop there. I would be okay with that if the UI were at least similar to other UIs on the Gnome DE. But they're not. Not even close.

      This is exacerbated even more when you consider the fact that I primarily use GIMP on Windows. I realize the GIMP is targeted primarily for Linux distributions, but to expect people to be happy with a UI paradigm that is utterly foreign to their OS of choice (whether Windows or OSX) is at best silly and ignorant.

    27. Re:representative ? by yotto · · Score: 2, Informative

      So GTK is "GNU's Not UNIX Image Manipulation Program Tool Kit" ?

    28. Re:representative ? by eternalnyte · · Score: 2, Interesting

      Maybe this is just my view, as I've been a pretty heavy GIMP user and a pretty light Photoshop user.. but to me Photoshop is also a lot of little sub-windows, just encased in a larger window that you can't take them out of. I can't stand hitting maximize on the image I'm working on in Photoshop just to see half of my image is now behind said boxes. With GIMP this is left up to the Window Manager which can be configured (for most of them, anyway) to maximize without overlapping the sub-windows of the same program (such as the tools window). My point is that, from my perspective, GIMP gives me more flexibility to setup my environment the way I want it, even on a single monitor display, though it may take a bit of time dinking around with it and actually using it before you find out exactly how it would work best for you. That's the same with any application, however.

      Multi-window applications have been around for quite some time in the UNIX world.. XEphem & GRASS come to mind. In the telco world there are several more commercial applications using this paradigm still today (even on Windows) such as Spirent's React or Anritsu's Tapestry. In other words, this isn't an entirely new idea, and GTK has been designed to flexible enough to allow for many, many types of applications to be built. GTK has grown from a widget set only for GIMP to be (dare I say?) the most used toolkit for UI development on Linux, so it gives developers the option to create applications however they desire and doesn't *force* anyone to any particular UI strategy.

      GIMP meshes pretty well with other GTK apps in my opinion, the GNOME window manager is excellent at placing windows for apps like GIMP (whereas on Windows, it really is horrible), consistent theming, window style, widget look and feel, etc..

      Who knows.. but judging from your language you are obviously pretty upset about the way GIMP has been managed.. just maybe one day it'll push you to fork it and work towards realizing your vision of the future. just make sure you remember you're comments when I post derogatory comments about *your* UI.

    29. Re:representative ? by syousef · · Score: 1

      Have you tried gimpshop? Basically gimp recompiled to make the defaults and windowing more like Photoshop.

      http://gimpshopdotnet.blogspot.com/
      http://gimpshop.blogspot.com/

      --
      These posts express my own personal views, not those of my employer
    30. Re:representative ? by Anonymous Coward · · Score: 0

      Have you used Inkscape much? I find that Gimp is to Photoshop as Illustrator is to Inkscape. There are still a few things that are still annoying about GTK in Inkscape, but they pale in comparison to the usability problems that Illustrator has.

    31. Re:representative ? by Skye16 · · Score: 1

      I have no problem with the look and feel, the widgets themselves are fine, and I also have no major problem with the floating windows. I'd prefer that I could toggle between floating and something on the side *in* the canvas window, yes, but it's hardly anything I'd stop using the application for. Complain about, yes, but if it never got changed, it'd be one of those "I wish it were different, but oh well" sorts of things. Like how I wish my washing machine gets blech stuff around the top and I have to scrub it. I complain, yes, but I'm not going to stop washing my clothes because of it.

      The UI I'm talking about is not the way it looks, per se. It's the way it is laid out. It is the fact that the tool palette is considered the "main window". It spawns, and it is the key of all the world. It would be like having floating formatting toolbars in a word processor opening, closing, and exporting documents, rather than the window the document appears in. That one tiny, seemingly insignificant thing is huge. It feels wrong. It feels like a binary abomination.

      There's something to be said for "doing your own thing". There are legitimate reasons to sometimes "buck the trend", flip off standards, and do it how it makes sense. I'll be honest with you; logically speaking, from a developers' standpoint, putting image manipulation functions (menubar) on the image window makes perfect sense. Allowing your tool palette to free-float makes sense. Making the tool palette the center of the GIMPs existence also makes sense from one perspective (i.e. what's the point in opening an image or some canvas if you're not going to use some tools on it to make it different in some way?) However, if that is the case, why are not ALL image manipulation functions (from the image window menubar) on the tool palette toolbar? What's good for the goose is good for the gander, after all. Unless the image window is open, there is absolutely no reason for you to be selecting tools. What are you going to do with them, draw on your application launcher? That would be appropriate if it worked, but, well, that sort of functionality isn't there (nor am I saying it should be).

      It's something so small, but so fundamentally wrong (to me) that it makes everything else feel... off-kilter. Again, I want to make it clear: it's not the look and feel, or theme, or widgets (buttons and the like), or even the dialogs (though I think the file dialogs are a bit too "click happy" to get anything meaningful done, but again, that is minor) - including button placement. It's the menubar layout, and which window is considered the primary one that bugs the shit out of me.

      (Offtopic: Also, I swear alot in general; you can't really judge my demeanor (online) by my language. As Lewis Black says, "Fuck isn't even a word to me, it's a comma". Depending on the setting, I may cut it out, or I may not, depending on a: the maturity of the audience and b: said audience's bearing on my life. I don't say it to offend, I don't say it because I think it's cool, nor do I say it because I lack a deeper vocabulary. I say it because it flows. I say it because, in the giant scheme of things, it means nothing more to me than the words "the" or "it". Obviously it *does* mean something when I use it, but just using it (or other words that some consider dirty) does not necessarily mean I'm really, really, really distraught/pissed off about something. It just means I wanted to use it, just like one moment I may decide to say "distraught" instead of "upset". That's all it means to me. :) )

    32. Re:representative ? by eternalnyte · · Score: 1

      Well, a relatively simple solution (or so I'm guessing, its been a while since I delved into the GIMP source (pre 2.0)) would probably be to allow the floating windows to dock to the canvas window in much the same way as they can currently dock with each other, this sounds like it would satisfy both UI camps. The toolbox being the main window, though, that seems kind of a given to me, since you can have multiple images open, there still must be a "main" window to keep the app alive, and having the toolbox there seemed more natural than having nothing there at all.

      But ah well.. as for the swearing, I could give a fuck :) but it's really all you can go by when online, you're post certainly seemed to be at a frantic pace to me when I read it.. but I can see it either way now.. so it goes with text-based communication.

    33. Re:representative ? by Anonymous Coward · · Score: 0

      I've basically never used Photoshop, and the Gimp's UI still frustrates me. Just one user's anecdote.

    34. Re:representative ? by Large+Green+Mallard · · Score: 1

      Looks interesting Mike :-)

      (PS: Hi!)

    35. Re:representative ? by Anonymous Coward · · Score: 0

      "Dump GTK?" You *do* know what GTK stands for don't you...? Gfucking_ugly ToolKit?
    36. Re:representative ? by dangitman · · Score: 1

      Personally I hate applications with one big monolithic window..

      Photoshop has "one big monolithic window? Since when? It has a ton of different tool palletes that you can put on any monitor you like. I am left wondering if you have even used Photoshop, because it doesn't sound like you have ever even looked at it.

      --
      ... and then they built the supercollider.
    37. Re:representative ? by renoX · · Score: 1

      I've never used Photoshop, but while I really have a hard time using Gimp even for very simple manipulations(an old gimp version) at work, at home I had much better luck using Paint.NET.

      So Gimp is really harder to use for beginners (does ingimp record the swearing of the users frustrated by Gimp), probably because it does things its own way..

    38. Re:representative ? by Draek · · Score: 1

      agreed. My personal pet peeves with TheGIMP are all of a technical nature, and almost all solved by GEGL. And I seriously can't understand the "it must feel like Photoshop!" crowd, I've used PSP from 6 to X, Krita, TheGIMP ever since v1.2, Photoshop since v5.5 and many other special-purpose graphic programs such as openCanvas, Corel Painter, LightZone and such. And out of them, Photoshop's UI is the only one I truly, truly despise. You know something is very wrong with an app, when it tries to be the end-all-be-all for graphic designers, web designers, painters, vector artists *and* photographers...

      --
      No problem is insoluble in all conceivable circumstances.
    39. Re:representative ? by Charles+W+Griswold · · Score: 1

      Failing that Krita is coming along very well as an image editor, it lacks a few features, but is far more usable than the GIMP.

      One of the features that it's lacking (as of version 1.6.0) is the ability to edit text. Until it gets that, I will continue using the Gimp.

      --
      "Those who are too smart to engage in politics are punished by being governed by those who are dumber" -- Plato
    40. Re:representative ? by Stormmind · · Score: 1

      The problem I see is that they'll be collecting stats about what people are doing with gimp already, while I'm more interested what could be changed in gimp to make people do more stuff with it. They'll probably find that most people do simple photo-manipulation for the web and decide that gimp doesn't need color-management. Meself, I've been waiting for that feature since I started using gimp.

    41. Re:representative ? by Anonymous Coward · · Score: 0

      As someone who began using GIMP before using Photoshop, I find Photoshop's interface to be awkward and GIMP's to be natural.
      Liar.
    42. Re:representative ? by Anonymous Coward · · Score: 0

      We got that fixed in 2.0 -- which should be out in a few months. A really nice text shape feature. In 1.6 you could try embedding a kword document, but that's a bit of a paint.

      Boudewijn Rempt,
      Krita maintainer

    43. Re:representative ? by aichpvee · · Score: 1

      Probably a lot, but not all. In general I think GIMP's interface is superior to Photoshop but Photoshop works better. There are also a lot of inconsistencies, bugs, and stupid choices in GIMP. Most of which aren't going to get fixed. I've been saying for years that GIMP is just a little ways away from being able to take on Photoshop seriously and beat it, but that little bit seems less and less like it will ever happen. Three or four years ago I would have said it would take a year to make GIMP really competitive, but not anymore. We're more likely to see a brand new open source graphics editor get to that point before GIMP even gets close. The people who develop it just don't have a clue, which is really too bad because no one is willing to challenge them.

      Also, this ingimp better have a bug/crash reporting tool to go along with all the stats, because it crashes on startup. Something being unable to register existing types with some glib thing.

      --
      The Farewell Tour II
    44. Re:representative ? by Anonymous Coward · · Score: 0

      >>You know something is very wrong with an app, when it tries to be the end-all-be-all for Since when did Adobe claim it was the 'be, web designers, painters, vector artists *and* photographers...

      Obviously you have never heard of...

      - Adobe Illustrator (for Graphic Designers, vector artists and illustrators)
      - Adobe Lightroom (for Photographers)
      - Adobe (nee Macromedia) Dreamweaver and HomeSite (for web designers)

    45. Re:representative ? by gkhan1 · · Score: 2, Funny

      Actually, it's "GNU's Not UNIX's Not UNIX Image Manipulation Program Tool Kit"

    46. Re:representative ? by Rei · · Score: 1

      You're right. I'm lying; you caught me. I'm part of an evil conspiracy to trick people into using GIMP.

      Drat. My wicked schemes have been foiled. I would have gotten away with it, too, if it weren't for you snooping ACs!

      --
      South Park pokes fun at sacred cows to make a point. Family guy pokes cows to hear them moo.
    47. Re:representative ? by Explo · · Score: 1

      My main "this is fucking stupid" remark is the irritation at having menus for each of the little sub windows. I can handle saying "File->New" on the tool palette, if I absolutely must, but everything fucking else is just wrong, wrong, wrong.


      Hmm, do you mean the menubar at the top of the individual image windows, or something else? In case you're talking about that particular menubar, it can be turned off from the preferences: Preferences->Image Windows->Appearance and remove the tick from the "Show Menubar" checkboxes for both normal and fullscreen mode. If you mean something different, then I have no idea though.

      --
      Everyone who makes generalizations should be shot.
    48. Re:representative ? by Charles+W+Griswold · · Score: 1

      We got that fixed in 2.0 -- which should be out in a few months. A really nice text shape feature. In 1.6 you could try embedding a kword document, but that's a bit of a paint.

      Boudewijn Rempt,
      Krita maintainer

      Awesome, I'm looking forward to it. Thanks for the reply.

      --
      "Those who are too smart to engage in politics are punished by being governed by those who are dumber" -- Plato
    49. Re:representative ? by rolando2424 · · Score: 1

      This is also my case.

      I tried to use Photoshop once, but I just couldn't get around it.

      However, I believe that on Windows machine (at least XP, I haven't really looked into Vista), since there is no multiple desktops, it can get hard to make the search of the windows in the taskbar, when it's all mixed up with IE / Firefox / other browsers windows, Windows Explorer window, etc.

      I think that this doesn't happen very often in a multi desktop environment. If you start gimp, and then find yourself with a taskbar full of windows, just send the Gimp windows to another desktop and work from there.

      And if you even take the time to learn the keyboard shortcuts, and always use the same settings for several tools, you can even try and leave the control window on a desktop, and the image window on another, and work directly on the image window

      Another idea would be to use a windows-manager that has non-overlapping windows. I believe that Ion does that. However, it's interface is more keyboard oriented, so it might not be for everyone.

      On other note, I don't think that Gimp will be able to beat Photoshop. On your in school, what is the program that teachers usually use to teach more "advanced" image manipulation (for example, for photographers). It's usually Photoshop (at least, I've been in some weeding, and the photographers always were editing the photos and printing them in Photoshop.

      Of course, for more simple manipulation, like changing color levels, contrast, etc. Gimp can be used as a teaching program (my school used it, when I recommend it, since they didn't had the money to buy Photoshop licences), however, I saw the look of desperation on my classmates' faces (some of them I think were pseudo-photoshoper, as in, they mostly dis some tutorials and that was about it. Not that I have anything against tutorials of course :D). I tried to teach them how to move around, and them I noticed something in them. Since it was different from the usual it was automatically labeled as "crap", and much "weeping" happened during those classes (But that also happened when they started learning Flash, so I don't know if I should consider it a Gimp problem).

      So I think the Gimp / Photoshop relation is a bit like Linux / Microsoft relation, in the way that while one is learned in schools, most people wont even use the other.

      Just my two cents anyway...

      --
      Okay seriously I've just run out of pointless things to say.
  2. GIMP and Photoshop by callistra.moonshadow · · Score: 1

    I use Gimp on a regular basis for photo editing as well as some artwork I do. Yes, it's UI is a bit clunky but it's free and works. It takes a bit to get used to but it's not that more difficult than Photoshop. Another key to remember is that it's free. That goes miles in my book.

    --
    --Cally
    1. Re:GIMP and Photoshop by Anonymous Coward · · Score: 0

      For a significant amount of people, the cost isn't the issue as they'll pirate or their business will pay - it's the quality of the product above anything.

      It'd be generally nicer to have a non-clunky application though.

    2. Re:GIMP and Photoshop by croddy · · Score: 5, Informative

      For a while, I actually believed the folks that repeated ad nauseum the mantra that GIMP's user interface was difficult compared to their beloved Photoshop. Then one day I sat down to try to do some quick photo edits on a Photoshop box. Two hours later, I gave up on its bizarre layer model and just installed the GIMP so I could get some work done.

      The ease-of-use of a graphic user interface, in general, correlates far more with the user's pre-existing familiarity with the interface than it does with any design decisions of the interface itself. There are certainly areas where GIMP's user interface could be improved, but let's not pretend like it's some kind of embarrassment -- because it's not.

    3. Re:GIMP and Photoshop by Anonymous Coward · · Score: 0

      Your time is free as well?

    4. Re:GIMP and Photoshop by Applekid · · Score: 1

      Given a free application with a lousy interface and a free application with a great interface, all features and functionality equal, having my cake and eating it too goes miles in my book.

      --
      More Twoson than Cupertino
    5. Re:GIMP and Photoshop by Anonymous Coward · · Score: 1, Insightful

      And how do you define quality here?

      From the looks of it, it seems you are implying that GIMP is not as good in 'quality' as PS. Of course, by quality, if you meant UI, menubars, you win. If you are talking about some good mathematical algorithms applied to my pixels to modify them the way I want, I am not sure how GIMP is inferior to PS. In fact, I find it better technically then PS. And add availability of lots of scripts and plugins people are developing.

      And, I have used both of it. PS at work, GIMP at home.

    6. Re:GIMP and Photoshop by Anonymous Coward · · Score: 0

      It was an embarrassment, but since GIMP 2.0 (with the massive UI overhaul) I think it's been pretty usable, and actually somewhat similar to older versions of Photoshop.

    7. Re:GIMP and Photoshop by jellomizer · · Score: 1

      Free Softare Value Cost=((Time to do job in Free App per year) - (Time to do job in expensive app per year)) * (Your Hourly Rate (or your salary/(40*50))*25%)

      Comerical Software Value Cost = ((Time to do job in expensive app per year) - (Time to do job in Free App per year)) * (Your Hourly Rate (or your salary/(40*50))*25%) + (Application Cost depreated over a year)

      The Lowest number has the better value over the other. Now sometimes Freesoftware wins other time comerical software wins.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    8. Re:GIMP and Photoshop by springbox · · Score: 1

      Especially with version 2 GIMP has become a lot more usable. I use it sometimes and have found that it takes a little while to get used to (like all environments) but overall there's nothing complicated about it. (The file dialog needs to be fixed though.) Also, Ingimp might be more successful if they release Windows binaries. It seems very Linux centric at the moment.

    9. Re:GIMP and Photoshop by XenoPhage · · Score: 1

      I have to agree with this... I am not, by any means, an artist. I don't want anyone to get the impression that anything more complicated than a stick figure comes naturally to me.

      That said, I don't find the GiMP to be *that* incredibly difficult. I can usually open it up and create/modify what I need within a reasonable amount of time.

      The last time I used Photoshop (admittedly, a long time ago.. Pre version 6 days I think..), I spent a lot of time banging around in the interface trying to figure out simple stuff.. I think the GiMP interface is fine, and I don't see the usability issue... But then again, I'm not an artist ...

      --
      XenoPhage
      Technological Musings
    10. Re:GIMP and Photoshop by autophile · · Score: 1

      Maybe there's just no one, single satisfying interface for photo editing. Personally, I'm very much at home with Photoshop's layers. I understood it intuitively right away. I never could get used to the GIMP.

      That said, maybe the opposite is true -- that some people take intuitively to the GIMP's UI but not to Photoshop.

      --Rob

      --
      Towards the Singularity.
    11. Re:GIMP and Photoshop by springbox · · Score: 1

      oops. They have a Win32 version thankfully. Hiding at the top of the downloads page.

    12. Re:GIMP and Photoshop by FooBarWidget · · Score: 1

      Huh? This is the first time I hear anybody saying that GIMP 2 is more usable. Even years after the release of GIMP 2 (which was indeed a major UI overhaul) I keep hearing people saying that GIMP is totally unusable.

    13. Re:GIMP and Photoshop by FooBarWidget · · Score: 1

      I don't understand what is so difficult about it.
      GIMP: click 'New layer' in the layers pane.
      Photoshop: click 'New layer' in the layers pane.

      What is it about GIMP's layer model that confuses you?

    14. Re:GIMP and Photoshop by VJ42 · · Score: 1

      I kinda agree. I find GIMP easier to use than Photoshop as well; I'm only a casual user, so havn't ever put any effort into learning Photoshop, but I find that I can use GIMP without having to do much learning. That said, I find that when I had Paint Shop Pro installed, it beat them both hands down, and is proof that GIMP could do a lot more in terms of usability. Photoshop don't have too, it's not aimed at casual users it's aimed at Professionals. The GIMP doesn't have that luxury, and seems to be aimed at a similar market to Paint Shop Pro, so IMO it should aim to be as usable as Paint Shop Pro, not as complex as Photoshop.

      --
      If I have nothing to hide, you have no reason to search me
    15. Re:GIMP and Photoshop by ajs · · Score: 3, Informative
      The GIMP tries to do so much that it's quite hard to make it anything less than daunting for new users. The number of windows and dialogs needed for just the simplest edit are a horror.

      That said, there are some basic problems that surpass the complexity.
      • The arbitrary split between "filters" and "script-fu" which places important items randomly (from the user perspective) into one of the two areas.
      • The number of dialogs needed to save a file (in some cases: filename dialog, replacement confirmation, export confirmation, and finally format settings).
      • The selection of color in multiple places (many plugins and tools do not use the default FG/BG)
      • The role of channels in the UI is not at all intuitively clear


      However, most of this pales to the limitations that are inherent in the functionality. One of my biggest gripes is that the anti-aliasing code is sloppy in non-uniformly implemented. Try this: select a circle, and then use Edit->Stroke Selection. Select a 2 pixel stroke line and go. You will get absolutely HORRID aliasing. The same thing happens (though not quite as bad) with the paint tool stroking.

      Overall, the GIMP is an amazing and powerful tool, but it has some serious warts.
    16. Re:GIMP and Photoshop by Brigadier · · Score: 1


      I agree, I used to work for a software developer who had a propriatory niche time program designed to work with some high end printing hardware. For years customers would complain and wine. Never satisfied with the changes. Some woudl lvoe it the other half would hate it, there was no way to appease the masses. Until finally the word came down from corprate ..."just make it look like corel" They did this and the customers were extatic. It's not so much about ease of use as it is about familiarity. all the professional letterheads, and graphic designers know photoshop, painter, quark. so if gimp wishes to appeal to said market they must become like adobe.

    17. Re:GIMP and Photoshop by arodland · · Score: 1

      And with the 2.3 devel releases, they've reorganized the menus in a way that takes a little getting used to, but corrects a lot of the original sources of confusion in the UI (like putting things that actually affect the whole image in the "Layer" menu). They've also made a number of the tools easier to use (compare for instance the old and new behaviors of the crop box). Unfortunately at the same time, they've replaced the wonderful old tool icons with the stupid indistinct pastel blobs that all of the GNOME retards seem to love these days.

    18. Re:GIMP and Photoshop by Miguel+de+Icaza · · Score: 0

      I don't understand what is so difficult about it.
      GIMP: click 'New layer' in the layers pane.
      Photoshop: click 'New layer' in the layers pane.

      Perhaps it would be a good idea that instead of/aswell as collecting real-time usability data in order to help the GIMP developers find and fix its usability problems, the instrumented gimp could include its own simple anaylisis software layer outfited with several hundred hueristics, so that if the user was repeatedly clicking in the layers menu a baloon (or something) could appear nearby and present a relevent excert from the gimp man(ual) pages. Even better would be to analyse the instrumentation data in real time and somehow reduce the unarguably high (because of its power and wealth of tools) complexity of gimps interface by presenting a simplified interface tailered to the infered task at hand.
      --
      Before adopting WHATWG, read the moonlight.NET EULA [http://www.microsoft.com/interop/msnovellcollab/moonlight.mspx]
    19. Re:GIMP and Photoshop by DogDude · · Score: 2, Insightful

      Maybe there's a really good reason that Photoshop does things the way it does. It's designed for professionals, and hasn't changed a whole lot in at least a decade, so I gotta figure that for professionals, Photoshop is made to work the way most graphics professionals need it to work. The layer thing IS complicated, but from what little I know about graphic design, all of that stuff is very useful (necessary?).

      --
      I don't respond to AC's.
    20. Re:GIMP and Photoshop by Fred_A · · Score: 2, Insightful

      Because those people as usual either don't need a complex graphics applications nd therefore won't learn how to use it or have used unlicensed copies of PhotoShop for years and hate Gimp because it's interface isn't the same ("waaah, it's not the same menu, I have to use the second button of the mouse, the horror")...

      The last time I used PhotoShop was on a MacII, before porting it to Windows was even considered. I've been using Gimp since the first release and never found its interface to be unusable. The Gimp is well documented and fairly easy to learn. I currently use it for my photo correction and retouching needs and it works just fine.

      Like a poster mentioned above, I'm fairly sure I never could do as much with PhotoShop without spending a significant amount of time learning a new complicated piece of software. Which I'll never do because PS costs around 1000 €s in Europe and because it doesn't run in Linux anyway (which is what I happen to do my work in).

      So Gimp and Krita suit me just fine (along with BibblePro and digiKam).

      --

      May contain traces of nut.
      Made from the freshest electrons.
    21. Re:GIMP and Photoshop by Perl-Pusher · · Score: 1

      For me its quit usable. People who complain about it grew up with Photoshop. What they want is Photoshop for free on whatever OS they use. Every college graphics course teaches Photoshop. That is hard to over come. The gimp is not photo shop, get over it. Photoshop is a lot more powerful. When you sit down and maybe use a book like "Grokking the Gimp" or one of the other books I've seen at Barnes & Noble. It works, its free, and after using it a while it becomes second nature. Any program is foreign at first. Try using POV ray when all you've ever used is Bryce. For me Gimp does what I used to do in Paint Shop Pro, image editing, creating web graphics etc. Fireworks is closer to Gimp in features than Photoshop. If I were a photo journalist or doing magazine layouts. I wouldn't choose Gimp and the UI is not the reason.

    22. Re:GIMP and Photoshop by downhole · · Score: 1

      I have to agree - I'm far from being an artist or anything, but I've found GIMP to be reasonably easy to use for the tasks I've used it for. It has its quirks, but so does every other program I've ever used, and you don't really notice it once you get used to them. I don't need all that many features, and I'm not real interested in shelling out $500 or whatever for Photoshop.

      I can't figure out why people are complaining about cropping. Click the crop tool, drag a rectangle, the part to be cropped is helpfully shaded and you can drag the crop area around or adjust the numbers in a dialog, and then you click once to crop. How could this be done easier?

      --
      I don't reply to ACs
    23. Re:GIMP and Photoshop by MobyDisk · · Score: 2, Insightful

      Two hours later, I gave up on its bizarre layer model and just installed the GIMP so I could get some work done. GIMP and Photoshop have essentially the same layer model as far as I can tell. Can you explain what was hard to use about Photoshop's layer model? Also, since you like to use GIMP, can you answer some of the complaints about the UI that other people have posted? For example: (plagiarized from another post)

      1. for some reason GIMP developers decided every single thing needs its own window and its own menu bar. It's weird as f*ck: put the entire layout in a single window with integrated panel layout (similar to how Eclipse does it, for example).

      2. each plugin is its own modeless exe dialog that takes arbitrary amount to start after it was called (at which time you can modify the processed image.. sometimes, and sometimes GIMP crashes because of it): create a proper lean plugin API and modal plugin dialog.

      3. the menus and options are all over the place: there seems to be no strategy at all about what goes where

      I find these issues to make GIMP nearly unusable. I'm always fighting with it. How do you get around these problems?
    24. Re:GIMP and Photoshop by Rei · · Score: 1, Informative

      Don't want sharp edges, is that what you're saying? Then stroke using a smooth paintbrush. It looks great to me. I've never used that tool before, and I figured that out in about five seconds.

      --
      South Park pokes fun at sacred cows to make a point. Family guy pokes cows to hear them moo.
    25. Re:GIMP and Photoshop by crabbz · · Score: 1

      1. for some reason GIMP developers decided every single thing needs its own window and its own menu bar. It's weird as f*ck: put the entire layout in a single window with integrated panel layout (similar to how Eclipse does it, for example).

      You can dock windows together (except I don't think the image windows). When I use gimp I typically have 2 windows open, one for the image and one containing all of the toolbox, layers and current tool options. It works fine for me. Perhaps they should have a better default setup though.

    26. Re:GIMP and Photoshop by Anonymous Coward · · Score: 0

      Never put it into an equation, it just seemed like common sense. But that's why Photoshop Elements is so awesome: $79.99. It payed for itself in setup time alone for getting my digitizer pad running correctly.

    27. Re:GIMP and Photoshop by EvanED · · Score: 2, Informative

      ("waaah, it's not the same menu, I have to use the second button of the mouse, the horror")...

      My main complaint about the Gimp UI is the multiple windows. It's cliche, but it's still true.

      2.0 helped a great deal because they group things together so there are less, but it's still a pain. Now instead of raising just one window (Photoshop) I have to raise three (the photo, the toolkit, and the navigator/layers/other stuff panel). On Linux this isn't horrible because I can dedicate a virtual desktop to it, but (1) on Windows it's a downright pain in the ass and (2) I shouldn't have to dedicate a virtual desktop to a program to make it usable!

    28. Re:GIMP and Photoshop by Eric+Pierce · · Score: 1

      You nailed it.

      Love live GIMP!
      EP

    29. Re:GIMP and Photoshop by KDR_11k · · Score: 1

      Floating selection "layers" were one thing that confused me. I don't recall what it was but I think you couldn't paint on a floating selection or something so you'd have to anchor it first (why isn't it treated like a regular layer or anchored when I hit deselect?)

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    30. Re:GIMP and Photoshop by imbaczek · · Score: 1

      That's so true it hurts. Multiple windows model doesn't work on MS Windows, period. Mod parent up.

    31. Re:GIMP and Photoshop by FooBarWidget · · Score: 1

      Hm? I just tested, and I *can* paint on a floating selection. I can also anchor it by clicking outside the selection area with the selection tool.

    32. Re:GIMP and Photoshop by KDR_11k · · Score: 1

      I've always wondered: What are the differences between regular photoshop and Elements? Elements seems more like a consumer level application so I expect it's geared more for photo editing and album compilation? I use PS mainly for painting stuff, rarely working with existing images so especially the painting tools would be important (and related elements like the layers and channels, don't care much about filters though).

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    33. Re:GIMP and Photoshop by FooBarWidget · · Score: 1

      Don't you mean Clippy? :)

    34. Re:GIMP and Photoshop by Caesar+Tjalbo · · Score: 0

      1. I have 3 windows open at least. The main GIMP window with the tools and their properties, a window with layers, channels and paths and a window for the image I'm working on. The only way I can deal with it is by having all three open on my screen unless I really need to maximize the image but then I usually don't need to switch tool or layer. Also, with the normal shortcut for switching apps, I can call another part of the program. Every additional image is another window, some tools come in their own window and I definitely organize my workflow to have never more than 5 windows open for long, but it's not something I'd call a problem. I lost Photoshop when I moved to Linux and I had to get used to the GIMP with all the windows but with virtual desktops, I keep the GIMP out of the way of other applications and it's very manageable.

      2. No comment really, I think it's about accepting the order of things. I wait for a dialog to start before I use it but delays haven't been particularly noticeable. GIMP hasn't crashed yet, despite some of the operations and image sizes being 'challenging' for my system. Haven't tried making my own plugins so far.

      3. "no strategy at all". Now I'm really curious what's so confusing about the menus and options. Let's assume you know what a pixel is and what can be done with it, how long would it take you to find your way in the menus? 1 hour? A day? "nearly unusable"... I'm all for UI improvements but at some point the fault's with the user and not fixable with software anymore. We're not talking about a simple editor but about a powerful graphics tool, the complexity of the UI is far less than the possibilities of the tool and after a week or so, my thinking was completely on the image and not on the tool anymore.

      --
      "I'm not much interested in interoperability. I want substitutability. I want to be able to throw your software out."
    35. Re:GIMP and Photoshop by fastest+fascist · · Score: 1

      Who cares about the interface, the performance sucks. Try painting long strokes with a brush over 100 pixels in size. I hope you enjoy waiting for strokes to finish rendering. At 200 pixels and above it gets really ridiculous. I filed a bug report on this some time ago, and the response was that if they could make it faster, they would have done so already. Promising.

    36. Re:GIMP and Photoshop by Fred_A · · Score: 1

      On Linux this isn't horrible because I can dedicate a virtual desktop to it, but (1) on Windows it's a downright pain in the ass and (2) I shouldn't have to dedicate a virtual desktop to a program to make it usable!
      Or you can set your window manager properly so that it recognizes that all the windows are part of the same application (well not in Windows obviously, but in Linux it's possible with most of them)...
      --

      May contain traces of nut.
      Made from the freshest electrons.
    37. Re:GIMP and Photoshop by ticklemeozmo · · Score: 1

      Stop being all "we're awesome, it's open source MAAAAAHN.. we know the way to do it!" I'm pretty sure the billion-dollar giant software company that designs programs that designers use for their designs for a living knows a thing or two about a thing or two..

      I've given up on GIMP for Windows and moved to Paint.NET. It's not as glamourous and the GIMP fanboys will complain it can't render the solar system in real-time, but for simple to intermediate edits and a majority of tools that PS has, it works for the amateur.

      --
      When modding "Informative", please make sure it both has a source and IS actually informative.
    38. Re:GIMP and Photoshop by yuda · · Score: 1

      It really depends where you previous training lies. I've spent around 7 years using photoshop to a fairly advanced level, when exclusivly switched over to linux around 18 months ago I forced myself to learn gimp, first off I found the very simple procedure of resizing and cropping images for web production very difficult but I got there eventually.

      The Photoshop vs GIMP argument is very similar to the Windows vs Linux argument, most people are very familar the product they are using and need a very compelling reason to switch and price doesn't usually cut it (how many people do you know have got a "free version" of photoshop compared to people who paid for it)?

    39. Re:GIMP and Photoshop by ajs · · Score: 1

      No, you're incorrect for several reasons (keep in mind here that I've developed software plugins for the gimp since before version 2.0). Mostly, it just doesn't work. Try it. You'll get a badly aliased stroke that's fuzzy.

      Second, having to select a brush rather than a specific line width is an even worse burden on the user. When you're drawing pictures, that might suffice, but when you're doing any kind of serious photo editing, you need specific, fine-grained control.

      This is simply a huge limitation in the GIMP that should have been resolved before 2.0 was released, but for some reason has remained all this time.

    40. Re:GIMP and Photoshop by Anonymous Coward · · Score: 0

      Then one day I sat down to try to do some quick photo edits on a Photoshop box. Two hours later, I gave up on its bizarre layer model and just installed the GIMP so I could get some work done.

      One data point = statistically significant!

      The ease-of-use of a graphic user interface, in general, correlates far more with the user's pre-existing familiarity with the interface than it does with any design decisions of the interface itself.

      I disagree. As a longtime Gimp user, I finally one day broke down and bought Photoshop, and immediately found it far easier to use.

      I have found one big difference between Adobe's tools and open-source graphics tools. Adobe's tools sometimes seem just a little bit off, and then I read the manual, which explains why it makes sense to do have done it that way. With open-source tools, it feels wonky, and reading the manual doesn't help explain why it's wonky.

    41. Re:GIMP and Photoshop by Rei · · Score: 1

      Try it.

      Could you explain to me how you think I "figured that out in about five seconds" after having "never used that tool before" and decided that it "looks great to me" without trying it? I've been scratching my head over here trying to figure out how you thought I pulled that off.

      Mostly, it just doesn't work

      Do you have some huge brush spacing or something? I'm assuming that you know what brush spacing is for, and that you're not faulting Gimp for doing something that you told it to do.

      Second, having to select a brush rather than a specific line width is an even worse burden on the user.

      Picking a brush is worse than typing a number?

      When you're drawing pictures, that might suffice, but when you're doing any kind of serious photo editing, you need specific, fine-grained control.

      Brushes, which you can customize down to the last detail, even using a bitmap if you so choose, aren't fine grained, but a single "width" value is? I'm really not following you here.

      --
      South Park pokes fun at sacred cows to make a point. Family guy pokes cows to hear them moo.
    42. Re:GIMP and Photoshop by Trogre · · Score: 1

      I've noticed that with the GIMP proper too. Under Linux one can select File->Print and get a beautiful Gutenprint dialog that lets you select parameters for your printer as well as orientation, scaling, etc.

      Under Windows you get, well, nothing.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    43. Re:GIMP and Photoshop by Trogre · · Score: 1

      That looks like a bug. No antialiasing is being performed. There is an antialiasing checkbox in the Line Style area but it has no effect.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    44. Re:GIMP and Photoshop by tepples · · Score: 1

      They have a Win32 version thankfully. Hiding at the top of the downloads page. What justifies the 98 MB download size?
    45. Re:GIMP and Photoshop by tepples · · Score: 1

      Your Hourly Rate (or your salary/(40*50))*25% But what about those whose hourly rate is low because they work in countries outside North America and Europe? And what about children still in school, who by child labor laws have an hourly rate of 0? That tilts the scale in favor of the Free application.
    46. Re:GIMP and Photoshop by Azul · · Score: 1

      Could you explain to me how you think I "figured that out in about five seconds" after having "never used that tool before" and decided that it "looks great to me" without trying it? I've been scratching my head over here trying to figure out how you thought I pulled that off.


      Well, I think GP is right in claiming that you don't get a nice aliased circle but "you'll get a badly aliased stroke that's fuzzy" instead. It really looks bad, even though it is aliased.

      But then again, I'll give you that his "keep in mind here that I've developed software plugins for the gimp since before version 2.0" is entirely irrelevant.

      GP: What about "Select > Border" (optionally followed by "Select > Feather") and then just Bucket Fill?
    47. Re:GIMP and Photoshop by Ferzelic · · Score: 1

      One of my biggest gripes is that the anti-aliasing code is sloppy in non-uniformly implemented. Try this: select a circle, and then use Edit->Stroke Selection. Select a 2 pixel stroke line and go. You will get absolutely HORRID aliasing. The same thing happens (though not quite as bad) with the paint tool stroking.

      That's more a side-effect of the operation you're doing, than a limitation of the Gimp.
      What Stroke Selection does, is literally draw along the edge of the selection boundary. Selection is a pixel-based function, so the Gimp can't (and shouldn't) make any guesses about the intended shape of the selection; it can only trace exactly what is defined. Hence, it can't reliably eliminate antialiasing, because it doesn't "know" you've selected a smooth circle -- just that there's a bunch of pixels, and it has to draw the boundary.

      That's the technical reason for your problem.
      Now, to achieve what you want to achieve, you can use a slightly different operation.

      Select -> To Path
      Select -> None (so the selection doesn't affect the stroke)
      Edit -> Stroke Path

      Because the path defines a curved shape, the Gimp knows you're trying to trace a smooth line, and so can antialias properly.
      It's kind of elegant, because all smooth-curve operations in the Gimp are done with Paths, and you can freely switch between Paths and Selections. I use this combination all the time doing speech bubbles in my comic.

      I agree with every other one of your complaints, though! :)
    48. Re:GIMP and Photoshop by ajs · · Score: 1

      Try it.

      Could you explain to me how you think I "figured that out in about five seconds" after having "never used that tool before" and decided that it "looks great to me" without trying it? I've been scratching my head over here trying to figure out how you thought I pulled that off. I simply cannot reconcile that with the facts. It leaves me wondering what application you're using.

      Since you claim that you can get a smooth, well-aliased circle/ellipse, I guess I'm just left to ask you to demonstrate it. Upload an image that you create somewhere in XCF format.

      Mostly, it just doesn't work

      Do you have some huge brush spacing or something? I'm assuming that you know what brush spacing is for, and that you're not faulting Gimp for doing something that you told it to do. Again, I've used the gimp and written plugin software for it for a number of years. I'm well familiar with its workings. With a brush spacing of the default 20 or set to 1, the result is the same: a pooly aliased, fuzzy line. The problem isn't with the brush, it's with the selection. Even with "antialiasing" selected, the selection is fundamentally a pixel-by-pixel outline which stroking outlines. Choosing a fuzzy brush will simply blur that alaised outline, not anti-alias it.

      The solution is for the selection itself to be sub-pixel. That's a big change, but in the years that the GIMP has been around and this need has been obvious, it's a bit shocking that it wasn't made.

      I'm also curious as to what you think of the other concerns that I noted.

      Second, having to select a brush rather than a specific line width is an even worse burden on the user.

      Picking a brush is worse than typing a number? Absolutely. I want to trace a 2-pixel wide outline that I have as a selection, not sort through all of the brushes to find the 2-pixel wide one, and THEN have to select a fuzzy version of the same brush after trial-and-error. This is where the GIMP sadly seems to have taken a "it's the user's problem" attitude.
    49. Re:GIMP and Photoshop by JoshJ · · Score: 1

      Probably because it has to be bundled in with GTK for windows.

    50. Re:GIMP and Photoshop by 5of0 · · Score: 1

      It amazes me that I haven't yet found one mention of DeWeirdifyer. I personally like the way GIMP works, but hey, for those that want them all in one window (which is annoying to me), Deweirdifyer is your ticket on Windows (assuming it's still compatible, I haven't used it in a while personally). For Linux, a quick google of "gimp one window" will find directions on how to do it with things like xnest.

      Seriously, stop whining and do a bit of googling. I like the GIMP interface like it is, and I'd be upset if they all of a sudden switched it to a single-window system, and I'd need a de-deweirdifyer, which I'm guessing would be a lot harder to come by.

      If you don't like it, this is open-source - there's usually a way to make it just like your little heart desires, probably two or three ways.

      I can't help but think of Blender, which, once I spent a few days running through some tutorials that pulled me up the steep learning slope, is far and away the most intuitive user interface I have ever had the pleasure of using. It gets all kinds of guff becasue it's different, but it's really very easy once you get past the "Aah it's different and I hate it" stage.

      --
      You all have Oo.o and Firefox, so get World Wind.
    51. Re:GIMP and Photoshop by bloobloo · · Score: 1

      So you're suggesting that if you have problems with the GIMP, you get a schoolchild to write your patches?

    52. Re:GIMP and Photoshop by BigSven · · Score: 1

      The arbitrary split between "filters" and "script-fu" which places important items randomly (from the user perspective) into one of the two areas.

      Right. That's why the developers got rid of that arbitrary split in the 2.3 series. Now plug-ins and scripts are organised by functionality instead of categorizing them by the programming language they are implemented in.

      The role of channels in the UI is not at all intuitively clear

      I am not sure if channels can be intuitively clear at all. But there's a user manual that explains the concepts. Perhaps you could elaborate what's wrong with channels or how they behave differently than what you would expect?

    53. Re:GIMP and Photoshop by tepples · · Score: 1

      Probably because it has to be bundled in with GTK for windows. The ordinary version of GIMP has an 8 MB GIMP, a 6 MB GTK+, and a 40 MB help file in 13 languages. True, the help file is huge, but ingimp without help is 45 MB, while plain GIMP without help is only 14 MB. Why does the instrumentation take 31 MB, and if English-only help would be smaller, then why isn't English-only help available separately?
    54. Re:GIMP and Photoshop by sckeener · · Score: 1

      GIMP is great. Admittedly I only use it for modifying Dilbert comics to match work politics before sending them out to co-workers. ;)

      --
      "Only one thing, is impossible for god: to find any sense in any copyright law on the planet." Mark Twain
    55. Re:GIMP and Photoshop by callistra.moonshadow · · Score: 1

      I don't wait. I have a good system. It is admittedly a gaming system but it also works fine with GIMP. I used to use it on an old laptop and it was a bit slow there, but it is quite fine on a good pc.

      --
      --Cally
    56. Re:GIMP and Photoshop by jellomizer · · Score: 1

      But what about those whose hourly rate is low because they work in countries outside North America and Europe? They still get paid. Convert to what ever currancy they use. If they get paid a small amount per hour then Using a more difficult to use but cheaper program may be worth it, the calculation still holds true.

      Of or people with a rate of 0.

      Yes it does tilt in the favor of the Free Application. I never said that Using the GIMP has no value, it is just for a lot of people Photoshop is a better overall value. You can make a simular calculation comparing a Mac Truck vs. a Prius. The Mac Truck costs more Less fuel efficent then the Prius. But Because the Mac Truck can carry a larger amount of good (Includings Multable Priuses) overall a person who needs to move these goods will save money with the Mac Truck... But for other people who do not need to move so much stuff on a daily basis may be better off with the Prius, because it will be more afordable for them.

      The point of the calculation is to show that for many Open Source Zealots is that there is good logical well thought out reasons for using speding Hundreds or Thousands of dollars on non Open Source Applications.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    57. Re:GIMP and Photoshop by ajs · · Score: 1

      What Stroke Selection does, is literally draw along the edge of the selection boundary. Selection is a pixel-based function, so the Gimp can't (and shouldn't) make any guesses about the intended shape of the selection That would track just fine if the ellipse selection tool didn't have an "antialiasing" checkbox....
    58. Re:GIMP and Photoshop by ajs · · Score: 1

      That's why the developers got rid of that arbitrary split in the 2.3 series. Now plug-ins and scripts are organised by functionality instead of categorizing them by the programming language they are implemented in. That's great news! Thanks for the update (still working with 2.2, here).

      The role of channels in the UI is not at all intuitively clear

      I am not sure if channels can be intuitively clear at all. This is a fair point, and easily the weakest of my concerns. It's just a hurdle that I had to deal with. I think there is room for improvement in how intuitive channel use can be, but it's not an entry-level feature.
    59. Re:GIMP and Photoshop by croddy · · Score: 1

      Well, I'll have to take your word for it. I've not used the GIMP extensively on Windows, but I use it frequently on my GNOME systems, where I rely heavily on virtual desktops. I'd be pretty pissed if they started shipping a GIMP that crammed itself inside an old-school MDI window.

      I've heard that they revamped the window manager for Vista, though, so perhaps a fork won't be necessary after all.

    60. Re:GIMP and Photoshop by Fred_A · · Score: 1

      The Gimp was written for a modern Unix/X11 window manager so it's probably horrible to use as it is in Windows or on Mac OS which have a single desktop / single application mindset.

      IMO having the Windows (and possibly Mac, if there's one) version of Gimp using an MDI window would make a lot of sense. It would make it much more usable in those environments and would help *a lot* in making the program acceptable to the masses.

      I'm currently having a discussion on my photo group with people who insist that for photo retouching, Photoshop in unavoidable, citing among other things the Gimp UI problems. Of course those people run it in Windows or Mac OS... (this is not to be taken as an argument that Gimp is the same as Photoshop which it isn't, just to point out that the current ports of the Gimp don't seem to be very good).

      --

      May contain traces of nut.
      Made from the freshest electrons.
    61. Re:GIMP and Photoshop by Ferzelic · · Score: 1

      The selection itself is antialiased -- if you fill the ellipse selection, you'll get a nice smooth solid-filled ellipse.

      The selection boundary, the marquee that highlights what is selected (which is based on an 50% alpha threshold of the selection), is not antialiased, because it is by definition a boundary between two pixels.

      Select a rectangle. Now use the selection mask function, and fill that rectangle with a gradient. You should end up with a box containing a selected alpha gradient from 0% to 100%. (If you Fill the selection, you should get a box that blends from white to black.)

      Now you decide to Stroke Selection on that box. What do you think that operation should result in?
      Antialiasing uses the alpha value of adjacent pixels to smooth the shape... what behavior should be defined for this example?

      Gimp sets the rule that the 50% alpha threshold defines the selection marquee; then it strokes the pixels under that marquee. In this example, it outlines the 'darker' half of the box. If it tried to guess antialiasing, you'd probably get one arbitrarily blurry edge on the gradient side. How blurry? It's not exactly a stroke any more...

      A selection can end up being any pattern of pixels. It could be a single ellipse, or an ellipse overlapping a rectangle with a big airbrushed stripe through the whole lot. It doesn't actually have a shape, unless you tell the Gimp to turn it into one with Selection to Path.

      I don't use the Stroke Selection tool, I always Stroke Path instead; but it works for what it does. The only real problem I have with the Stroke Selection operation is they left the "antialias" checkbox there, as both tools use the same dialog. Antialias should be greyed out for Stroke Selection, as it's irrelevant.

    62. Re:GIMP and Photoshop by fastest+fascist · · Score: 1

      Hmh, I have a system that operates Photoshop very well (dual-core Athlon 64@ 1.8ghz, 2 gigabytes of ram), but Gimp paint tools crawl on it. Same on other computers with perfectly reasonable specs I've tried it with. I never tried the windows version though, so I can't say how well that performs.

  3. It's not that bad by saibot834 · · Score: 2, Interesting

    At the beginning it is hard - just like many programs. But my experience is, that you get used to it pretty fast.

    1. Re:It's not that bad by jellomizer · · Score: 2, Insightful

      I though so too. Until I started to use Photoshop, after that I know how to use GIMP a little better because I know of more things to find... But sience I have Photoshop now I rairly need to use the GIMP. GIMPs usability is its major flaw, it has many of the useful feature of photoshop but it is so clunky (and photoshop isn't a good interface) that I probably have made more money from using photoshop then the GIMP even after paying the high cost of photoshop because doing work take so much less time, that I could put it towards billable jobs.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:It's not that bad by saibot834 · · Score: 1

      It's not only a matter of price. It's also a matter of your freedom. I prefer GIMP, not only because it can handle everything a non-professional can possibly want, but also because it is free software (under the GNU General Public License).

    3. Re:It's not that bad by jellomizer · · Score: 2, Insightful

      With the extra money in the pocket I can afford extra freedoms, Like being able to go to a movie, with my wife, having better food, nicer riding car... GNU is not free as in freedom is it free as RMS Tells you it is free. Life in a free society requires you to make choices, some of these choices are sacrificing one type of freedom for an other. If I chose free software all the time even if it is less of an overall value then I choose to loose the ability to use other forms of freedom. There is nothing stopping me from having GIMP and Photoshop on my same computer. So overall with Photoshop and the ability to use the GIMP on my system I have not loss any freedom. I support and applaud people who Make GPL software, they are doing a good thing... But if their tool doesn't work for me I don't want to feel trapped and not able to use non GPL alternatives.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    4. Re:It's not that bad by springbox · · Score: 1

      The interface is more intuitive than Blender. Maybe that interface needs to be fixed instead. (Of course I've only used it for 15 minutes and tried one of the "how to use Blender's unique interface" tutorials before giving up.)

    5. Re:It's not that bad by Blakey+Rat · · Score: 1

      My major gripe about the GIMP is that the filters that ship with the software are "destructive."

      What I mean is that if you have your layers arranged a certain way, and a certain selection before running the filters, God only knows whether your layers will be the same, or what your selection is when it finishes. (IIRC, some of them would even move windows, change tool settings, etc) Would it have killed them to save that information and restore it when done?

    6. Re:It's not that bad by Knuckles · · Score: 1

      The Blender interface is geared towards people who will spend thousands of hours in front of it and need to get stuff done fast. How well you understand it in the first 15 minutes is completely irrelevant. Unfortunately, Microsoft has followed your model and created software that is easy to learn, but will frustrate for years afterwards.

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    7. Re:It's not that bad by GeckoX · · Score: 1

      Yep, we should all drive Lada's.

      Ok, not free in any sense really, but hopefully you'll get why I used that as an example.

      Gimp's relative 'freeness' has absolutely ZERO relation to it's inherent usability. This is one of the reasons why the Gimp is STILL such a usability abomination...because so many people argue it's 'freeness' as the trump for all. "But it's ui sucks!", "Yeah, but it's FREE and therefor better!"

      There is an argument that non-free software evolves better UI's because since people have to PAY for that software, they are much less willing to sacrifice usability in said product. Thus developers of non-free software have a much higher motivation to produce more usable UI's.

      Personally, I don't think it has to be either way myself. Bottom line is, the Gimp's UI is atrocious, and has been since it's inception. I've tried to make the switch myself at least a dozen times over the years, and it's just not worth the pain involved. Glad to see some people are indeed working on this.

      --
      No Comment.
    8. Re:It's not that bad by CastrTroy · · Score: 1

      This concept is called expert user interfaces. Basically your UI can be complicated with lots of options and weird key shortcuts, provided the users are experts and will have the time to learn all this stuff. Photoshop is extremely daunting for someone who's never used it before. But for someone who is a graphic designer and spending 8 hours a day using it, they find it very usable. Personally I find GIMP easier to use than Photoshop, just because it isn't geared towards professional graphic designers. Blender is another great example. If you just want to throw together a quick 3D scene, and use it once a month, then it's probably not the tool for you. However, if you spend all your time rendering complex 3D scenes then you will probably find it quite useful.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    9. Re:It's not that bad by theJML · · Score: 1

      I'm going to have to agree, the GIMP is superior to Photoshop. At least compared to CS2. I haven't had a reason to try CS3. I mean, I guess I fit in the non-pro category, but I do use it quite a bit for web design at work and home, along with lots of work with digital photos. I really kinda just fell into it and never had to "learn" much.

      I think your view comes from your background. I've been a Linux user for 15 years or so now and it just seems to make complete sense. The multi-window layout, the right click menus, the shortcuts, the placement of menu items, it was just like "hmm, I wonder if I could do this, it has to do with layers, [click on layers menu], oh look, it's right there!".

      Now on the other hand, I'm going to have to say that this comparison that everyone automatically makes between Photoshop and GIMP is sort of like comparing VI and Nano and Emacs. They all edit (and besides the religious followers that I'm sure will fight this one out again on here) they work well and stand on their own as individual editors. They're all tools and using the right tool at the right time does help one work smarter and not harder.

      Really at this point in time I hope the GIMP doesn't change anything. Sure they can polish some stuff, but really that's all Photoshop has been doing as of late. The GIMP has already got a good thing in it's UI, stick with it. Spend the time on some cool filters and reducing memory usage and ignore these crazy ingimp people.

      --
      -=JML=-
    10. Re:It's not that bad by Gen.Anti · · Score: 1

      With a better car and more movies we are as trapped as without. What kind of a free society is this, if you are forced (not free) to choose between being "forced to A and not forced to B", and vice versa? Actually later you say you don't lose any freedom. Where's this sacrificing then? Maybe things are entirely different.

      You are not free to chose something of less overall value. You are only free to have your nicer car "freedom". Actually, there's a lot pushing you into having this Photoshop. Even if it was an unlicensed copy, good for Adobe. By having it, you make it a bit harder for me not to use Photoshop.

      You don't support people who make GPLed software when you are using Photoshop. You don't support those people when you say GNU is not free. You don't support them when you buy a nicer car.

  4. Re:GIMP will always be a gimp by Aminion · · Score: 3, Informative

    Or they could just call it GIMPshop....

  5. About that name... by R2.0 · · Score: 3, Insightful

    So, if I invent a version that gives data on why the name sucks (the otehr main problem with the program), will the developers pay attention to that too?

    --
    "As God is my witness, I thought turkeys could fly." A. Carlson
  6. Bring out the Gimp by a-zarkon! · · Score: 0, Offtopic

    Zed: Bring out the Gimp

    Maynard: The Gimp's sleeping

    Zed: Well I guess you're going to have to wake him up

    I'm sorry, I'm a Gimp user but every time I hear, see, or use the application I flash to that scene. Go ahead, I'm off topic and I accept my due.

  7. But I am scared of change. by woodchip · · Score: 3, Insightful

    I don't remember ever having a problem figuring out GIMP. But it would drive me insane if they start changing things around on me.

    1. Re:But I am scared of change. by griffjon · · Score: 2, Insightful

      Importantly, does ingimp track crashes?

      --
      Returned Peace Corps IT Volunteer
    2. Re:But I am scared of change. by Zantetsuken · · Score: 1

      So if they did change things, all it would really mean is they give a few options the first time you fire up the new version with major changes to the UI (presumably so Photoshop people would be more comfortable) - act like the old GIMP, or the new one.

  8. Representative? by McDutchie · · Score: 4, Interesting

    I already see one potential problem with this approach, and that is that it collects usability statistics from ingimp users, not GIMP users. How would it be guaranteed that the two groups are statistically equivalent?

    (No, I have not RTFA yet.)

    1. Re:Representative? by Soulfry · · Score: 2, Informative

      Because involvement in human-subjects research is voluntary, there will always be a self-selection bias. (That is, we cannot force people to use this software any more than we can force people to come into a usability lab to participate in a usability study.) However, we can still estimate the representativeness of the population by understanding the types of people likely to download and install ingimp, and those who are not. If you fall in the latter camp -- you'd never want to use ingimp -- we really want to talk to you. Send us an email at the email address given on the site: http://www.ingimp.org/contact.

      Michael Terry

  9. Gimp needs to be surpassed by junglee_iitk · · Score: 4, Insightful

    There are far too many anomalies of usability, lack of features and intricacies required for Gimp. Today, Photoshop is the industry leader, and anyone doing serious editing is using it. To be successful, Gimp must surpass it in more than one way (the one way being free). Kind of like what Firefox did to IE. Unfortunately, Gimp is no where ready for that. And I get a feeling that it is (heading to) nowhere.

    I have been using Gimp for a long time. When I first installed Linux it was the only program everyone used to talk about. KDE's kolourpaint was not yet there for general purpose paint-brush replacement. I have used it for years under the hood of open-source fanboyism. And I think that is the reason why it has suffered. It had no competition, and now it is just a software which you don't want to open, again.

    Now, I know it is not a paint-brush replacement. But it is neither a Photoshop replacement... and the middle land is already full of other utilities. Inkscape, Krita, ... may be even Blender. The problem is that no one wants to be in the middle. Utilities need to rise to the top, or they face the fate of XMMS. I hope there will be a replacement in GTK too, just to show Gimp how to use the toolkit :)

    PS: posted this on journal before... this is shameless re-posting.

    1. Re:Gimp needs to be surpassed by immcintosh · · Score: 1

      Just out of curiosity, and this coming from a long time Windows user who has recently completely switched over to Linux, I can say I've used Photoshop extensively but have yet to spend much time in GIMP, although I intend to. At first blush however, I didn't really notice any major disparities between GIMP's feature set and Photoshop's. Would you care to point out what you feel its actual technical, rather than aesthetic, shortcomings are so I can familiarize myself better with its limits?

    2. Re:Gimp needs to be surpassed by mpapet · · Score: 1

      Today, Photoshop is the industry leader...

      I don't think the GIMP project primary goals include world domination.

      To be successful, Gimp must surpass it in more than one way
      There is a huge entertainment industry segment using FilmGimp and GIMP so, it already surpasses whatever else is out there right now in some segments. I would argue that it is quite successful anyway.

      But it is neither a Photoshop replacement
      There will never be a day when Photoshop is the equivalent of GIMP and vice versa. GIMP is excellent and stands on it's own merits. The print shop natives are getting quite restless now anyway considering Adobe put a hard link to Kinkos in Acrobat Reader. http://www.printondemand.com/MT/archives/011197.ht ml Scribus, Inkscape and GIMP on a Linux desktop, I'd say they have some good Free alternatives out there to promote to their customers. GNU Preflight software anyone???

      I don't need adobe products and there are many people throwing money away on proprietary products when the GIMP has way more tools than they can possibly use.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    3. Re:Gimp needs to be surpassed by Bill+Barth · · Score: 1

      Higher bit-depths (like 16-bit per pixel TIFFs, HDR, etc.). PS does at least 16-bit per pixel images, and I think is starting to develop some HDR capabilities as well. Yes, there's CinePaint, but it's on an ancient Gimp tree and is really just a stopgap.

      --
      Yes...I am a rocket scientist.
    4. Re:Gimp needs to be surpassed by Hijacked+Public · · Score: 1

      Organizational tools are a 'middle ground' of digital imaging software that needs serious attention. Especially with consumer grade SLRs becoming more popular and probably bringing RAW formats with them, considering that no popular OSs natively organize RAW images in any useful way.

      Photoshop Lightroom is quite good from a number of standpoints (UI being one of them). It provides reasonable editing tools, I'm a pro and I can do a good chunk of what I need without switching to Photoshop. Even when I do need to doing so is seamless. Of course it is worthless for handling large libraries of images because it falls apart completely.

      iView Media Pro was nice but Microsoft bought them and I'm not sure where they plan to take it. Most likely they intend to intergrate a bunch of garbage that no one wants.

      Darkroom is good but really intended for pro studios. All of the apps I have seen that come bundled with digital cameras are complete garbage.

      --
      "Sacrifice for the good of The State" - The State
    5. Re:Gimp needs to be surpassed by Achromatic1978 · · Score: 1

      Darkroom? URL? Searching for Darkroom and photography app leads to a rather large volume of results, unsurprisingly. ;)

    6. Re:Gimp needs to be surpassed by Hijacked+Public · · Score: 1

      http://www.expressdigital.com/products/darkroom.sh tm

      It has a lot of integration with printing houses. Big with wedding photographers, school pictures outfits, etc.

      --
      "Sacrifice for the good of The State" - The State
    7. Re:Gimp needs to be surpassed by fyngyrz · · Score: 2, Interesting
      Would you care to point out what you feel its actual technical, rather than aesthetic, shortcomings are so I can familiarize myself better with its limits?

      Gimp is often called to task as compared to Photoshop for:

      • Being 8 bit only
      • No CMYK editing
      • No layer styles
      • UI - things are in different places, use different keystrokes
      • Antialiasing quality problems (there's even a post here today about that)
      • Platform (no current OSX native version, though there may be a X version somewhere)
      • The old X/Mac version has some issues with which window is active that are inconvenient

      Aside from those issues — which frankly don't mean much to non-pro users with the exception of anti-aliasing (they should really fix that) and layer styles (very, very convenient) — Gimp is extraordinarily capable and certainly worth the time to learn. Personally, I have occasion to use Photoshop, Gimp, PSP, and some others most workdays; I don't have any trouble at all with functionality being over here in one program and it being over there in another. But I'm not your average user; graphics are my thing on every level from programming to amusement to my job. Frankly, the people who cry "I'm a professional" and are manifestly unable to learn a new UI... I have a lot of trouble taking them seriously. I listen to them because that's my job, and I craft solutions to problems as they describe them (such as giving them a UI that acts like the UI they are used to), but I have not found any need for those solutions myself.

      --
      I've fallen off your lawn, and I can't get up.
    8. Re:Gimp needs to be surpassed by soupdevil · · Score: 1

      GIMP's text tools are rudimentary compared to Photoshop's. That's another reason I haven't made the switch.

    9. Re:Gimp needs to be surpassed by Anonymous Coward · · Score: 0

      Funny you mention kolourpaint...

      I can get things done far faster and easier with kolourpaint than I can with GIMP. Not only is kolourpaint 100% adequate for my needs, it's _more_ adequate than GIMP.

      Granted, kolourpaint isn't a Photoshop replacement, but neither is GIMP.

    10. Re:Gimp needs to be surpassed by fyngyrz · · Score: 1
      GIMP's text tools are rudimentary compared to Photoshop's.

      Is there a rendering / quality problem? Or are you talking about editable placement, that sort of thing?

      I tend to put text on layers; you can do more with a layer than you can with anything else, so I'm not looking for anything but good fonts from the program's font engine.

      --
      I've fallen off your lawn, and I can't get up.
    11. Re:Gimp needs to be surpassed by Glytch · · Score: 1

      One additional thing Gimp lacks and Photoshop has is adjustment layers. It's not a dealbreaker for me, but they're awfully convenient. I'm an amateur photographer, and the lack of 16 bit is a much bigger problem for me. It means I have to be much more careful in the raw converter, and leave as little as possible to do in Gimp (cropping, unsharp mask, and some minor dodging/burning, mainly).

      I agree about those Photoshop users who complain about Gimp's UI. What does it say about a person who refuses or is incapable of adapting to new software? I know both interfaces, and can switch between them at will. (I prefer Gimp's because MDI is a horrible, horrible kludge that deserved to die in a fire in the 90's.) If a new program comes along, I'll learn that as well and judge it on its' own merits.

    12. Re:Gimp needs to be surpassed by junglee_iitk · · Score: 1
      I am no professional. But being blind to the reality is not a wise choice. My question is, where is Gimp heading? Non-pro users get things done using lot less sophisticated tools. Using GIMP is a overkill for people like me.

      Frankly, the people who cry "I'm a professional" and are manifestly unable to learn a new UI... I have a lot of trouble taking them seriously.

      Funny how "standard" is a forgotten word when it comes to Gimp.

      One cannot deny that at the end, it is all about UI learning. What is debatable is how much of it is worthwhile. People also complain about Blender, but after learning it, it is beneficial, which makes people learn it. Unfortunately, GIMP is not so worth-while, as I said, since now it has better competitors.
  10. The main usability flaw I find by LM741N · · Score: 5, Insightful

    is in getting others to use the program because of its name. Lets have a contest to rename the GIMP.

    1. Re:The main usability flaw I find by sqrt(2) · · Score: 1

      I do think they should rename it, if for no other reason than to eliminate it as a point of criticism.

      Although, it's entirely possible they could pick a name that's worse.

      --
      If you build it, nerds will come. Soylentnews.org
    2. Re:The main usability flaw I find by jellomizer · · Score: 1

      We need to do that with a lot of open source applications. Newbe Question how do I do this simple task that was really easy in Windows or OS X, Linux user answer "oh come on it is just as easy as windows you run the program konflabjixxiaidjf v.3.99 it is just like windows". The program may be the easiest to use program in the world but if it has a Supid name that people will not connect the name to the function of the application they will not use it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:The main usability flaw I find by FooBarWidget · · Score: 1

      Then who defines what is "stupid" and what is not? Why are "Skype" and "Adium" better names than "Pidgin"? Why is "Excel" a better name than "OpenOffice Spreadsheet"? (I dare to say that the latter is better!) Why is "mIRC" a better name than "X-Chat"? Why is "Outlook" better than "Evolution"?

    4. Re:The main usability flaw I find by the_humeister · · Score: 1

      I agree. I once brought it up in a meeting where the idea of bringing in an image manipulation program was discussed. I made the mistake of calling it "the gimp." People laughed and didn't give it a second thought. Take the example of CinePaint. It used to be called Film Gimp. Which one sounds more professional?

    5. Re:The main usability flaw I find by doshell · · Score: 1

      So how do Windows users figure out that:

      • Excel is a spreadsheet application?
      • Outlook is an e-mail client?
      • Firefox is a web browser?
      • Winamp is a media player?
      • Adobe Reader displays PDF documents?
      • Skype is a VoIP application?

      All of these are quite popular in Windows land. By your logic, since none of them have names that correlate to their function, no one would be willing to use them...

      Counter-examples aside, KDE does something useful to help users with this: the K Menu (analogous to Start menu in Windows) can be configured to show the program function alongside its name. So for example Amarok shows up as "Audio Player (Amarok)", or even just "Audio Player".

      --
      Score: i, Imaginary
    6. Re:The main usability flaw I find by Threni · · Score: 0, Troll

      > is in getting others to use the program because of its name.

      No, the main problem is that it's a piece of shit to use. I'm sure you get used to it eventually, just like using the mouse with the wrong hand. I've tried Gimp on a few occasions (when other I used other PCs, or before I determined to never again use any software illegally) and I always found it completely counter-intuitive. For me, at least, it's well worth the money to use a cheap alternative (Photoshop or Paint Shop Pro). I can just do without the hassle. I'm sure the quality of the effects/processing/tools are fine, but I don't understand why the developers don't take a step back, look at what's been happening to the rest of the market and start again on the UI.

    7. Re:The main usability flaw I find by Nasarius · · Score: 1

      Have you used a Linux desktop in the past few years? The freedesktop.org specs require a certain amount of metadata for application "shortcuts", which are used by KDE and Gnome to categorize and describe nearly every application in the menu. If you're willing to spend five seconds looking at your options, you'll have no difficulty finding a Linux equivalent for any common task.

      --
      LOAD "SIG",8,1
    8. Re:The main usability flaw I find by Telvin_3d · · Score: 1

      All things are judged in relation to the competition. GIMP is a stupid name, at least in relation to Photoshop. At least 'Photoshop' hints that photos and images in general might be involved. For all but a small subset of the population, the biggest association the word 'gimp' has is physically disabled people. And before it gets mentioned, 'GNU Image Manipulation Program" is a fine (if long) name, but no one, not even the official web site calls it that.

    9. Re:The main usability flaw I find by jellomizer · · Score: 1

      Well Skype, Adium and Pidgin are all stupid names (I only have heard of Skype myself, and others know Skype because it is packaged and advertised quite well). Excel is not not a better name then OpenOffice Spreadsheet, most people who see OpenOffice Spreadsheet will know it will be a program like Excel (Excel only being know because its wide use, and forced training from schools and companies), mIRC is better then X-Chat for people who chat on the IRC (And know what the IRC is). X-Chat looks kinda R+ Rated (And tells nothing on what it is chatting on). Outlook and Evolution are both stupid names as well but just like Excel Schools and Companies train people to know what OutLook is. It is not a Rule that an Open Source App needs to given a stupid name it is just a lot of them have stupid names. And popular apps can have stupid names as well but they are wide known because money and media went into advertising it, so people have a brand name connecnted to it that they understand. Good names are a first start to making a user friendly app, so the person know what to do to go in the application.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    10. Re:The main usability flaw I find by doshell · · Score: 1

      I will add something else: most users have their first contact with a program when they click on a file that opens with that program. For example, I don't think anyone runs Adobe Reader directly and uses the File|Open dialog; instead they click on the icon for a PDF file. This way they learn Adobe Reader is a program that reads PDFs.

      While this can't be said of some applications that don't have "files to open" (e.g. an IM client), it is certainly true of many of the more common computer operations (e.g. edit a Word document, see an image, listen to an audio file, ...). And both Windows and Linux distributions come with default programs for the most common file types, and indeed register those defaults when installing new software.

      For the rest, a well-designed "Start menu" equivalent will suffice ;)

      --
      Score: i, Imaginary
    11. Re:The main usability flaw I find by Culture20 · · Score: 0

      I always refer to it as the GNU Image Manipulation Program, and let others figure out the acronym for themselves. For brevity, I like to call it GNU IMP. Its official acronym has been the reason why it hasn't been adopted in two design departments I worked closely with (no, it wasn't usability, they never even tried it because "the GIMP" didn't sound like the kind of software a serious graphics designer should be associated with, despite the fact that they wouldn't have used half of the features available).

      The GNU Image Manipulation Program (GNU IMP) isn't handicapped, nor does it have a strange leather fetish. IMP sounds better, but it's still less business-like.

    12. Re:The main usability flaw I find by mjeffers · · Score: 1

      You have a very good point and while there's probably not much point arguing about if Skype or Pidgin better encapsulates VOIP it seems pretty clear that calling image editing software something that calls to mind either a cruel name used to torment the physically handicapped or a sex-slave in Pulp Fiction is a terrible idea. It's really embarrassing that they've let it linger on this long. My only fear is that it could end up worse.

    13. Re:The main usability flaw I find by Anonymous Coward · · Score: 0

      And before it gets mentioned, 'GNU Image Manipulation Program" is a fine (if long) name, but no one, not even the official web site calls it that.

      The very first sentence on gimp.org is: "GIMP is the GNU Image Manipulation Program."

    14. Re:The main usability flaw I find by FooBarWidget · · Score: 1

      Let us call it Open Image Studio. Does that really sound like a better name to you?

    15. Re:The main usability flaw I find by FooBarWidget · · Score: 2, Interesting

      Would it really solve your frustrations if each and every open source app have names like these?
      - Linux Image Studio
      - EasyMail Professional
      - Open Vector Drawer
      - Web Navigator
      - Open Developer Environment
      - TextEdit Pro

    16. Re:The main usability flaw I find by Laur · · Score: 5, Insightful

      Then who defines what is "stupid" and what is not?
      While I see what you are saying, naming your software with the same name (or acronym) as a derogatory term is pretty stupid by any criteria. Ask yourself, would you use the New and Improved Graphics Generation and Enhancement pRogram? Would you tell your friends about it? Would you suggest it to your boss?
      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
    17. Re:The main usability flaw I find by Knuckles · · Score: 1

      You mean, more or less just like the Ubuntu menu? ;)

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    18. Re:The main usability flaw I find by FooBarWidget · · Score: 1

      That's only if the term really is derogatory. Gimp may refer to disabled people, but to me as a non-American, Gimp sounds more like a kind of shoes. Furthermore, Gimp can also refer to a pulp fiction character.

      Mono can refer to a decease, to the Spanish word for monkey or to mono/stereo audio. Does the fact that Mono *may* refer to a decease automatically mean nobody should ever use the word "mono" for any product?

    19. Re:The main usability flaw I find by Blakey+Rat · · Score: 2, Funny

      Yes, yes, but imagine if those apps were named:

      * Deafy
      * Retard
      * Dumbass
      * Drooler

      GIMP isn't a bad name because it doesn't describe what the program does, GIMP is a bad name because nobody wants to use gimped software.

    20. Re:The main usability flaw I find by Rakishi · · Score: 1

      Gimp may refer to disabled people, but to me as a non-American, Gimp sounds more like a kind of shoes. Since Americans make up a large portion of the users and English makes up an even larger portion if a given phrase has negative connotations in it you don't use it.

      Does the fact that Mono *may* refer to a decease automatically mean nobody should ever use the word "mono" for any product? Yes. If the vast majority of the possible users associate a given term with negative things then you don't name your damn product as that. Plain and simple. Names do matter.

      Furthermore, Gimp can also refer to a pulp fiction character. And that character is also not something that you want people to associate with your product.
    21. Re:The main usability flaw I find by dg41 · · Score: 1

      I agree. I work in an accessible junior high school and I had to change the desktop shortcut to GNU Image Manipulation Program because I got complaints about it being offensive. It may seem silly to some, but I can understand the concern.

    22. Re:The main usability flaw I find by ClosedSource · · Score: 1

      I think the whole GNU "joke" is getting a bit old and shouldn't be perpended to so many applications. It's a bit like calling it AMWITABIMP (A Man Walks Into A Bar Image Manipulation Program). GCC could be renamed AMWITABCC (A Man Walks Into A Bar Compiler Collection). You get the idea.

    23. Re:The main usability flaw I find by Anonymous Coward · · Score: 0

      You could pick any name and I guarantee people who simply hate GIMP and everything it stands for (free high quality photo manipulation) will complain about it.

    24. Re:The main usability flaw I find by PitaBred · · Score: 1

      Basically, people are stupid, bitch about it, and you have to jump? Gotta love the new America, where it's your right and God-given duty to be offended by everything without even thinking about trying to understand it.

    25. Re:The main usability flaw I find by Trogre · · Score: 1

      How about GNUPaint then?

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    26. Re:The main usability flaw I find by timothy · · Score: 1

      To anyone who went to a summer camp somewhat recently (an American one at least, can't speak for elsewhere), "gimp" is the plasticky string used to make annoying bracelets, necklaces, etc.

      timothy

      --
      jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
    27. Re:The main usability flaw I find by Anonymous Coward · · Score: 0

      Except it isn't a joke. It is branding. GNU here is the 'brand'. Yes, GNU might have a quirky meaning when expanded, but in general, GNU is short for GNU.

    28. Re:The main usability flaw I find by ClosedSource · · Score: 1

      Well, its a "joke" that became a brand. There's no good reason why the "G" for GNU needs to be included in the application's name. The fact that it is, suggests that the GNU "cuteness" is still alive and well. I thought that sort of thing was cute too when I read about it in Metamagical Themas in the mid-80's, but it seems very stale now.

    29. Re:The main usability flaw I find by Anonymous Coward · · Score: 0

      Gimp? Not hemp?

    30. Re:The main usability flaw I find by chub_mackerel · · Score: 3, Funny

      Professional Image Manipulation Program...

      Oh, never mind.

    31. Re:The main usability flaw I find by 4D6963 · · Score: 1

      Ask yourself, would you use the New and Improved Graphics Generation and Enhancement pRogram? Would you tell your friends about it? Would you suggest it to your boss?

      Oh crap.. maybe that's why so few people want to mess around with my ARSE, I mean my Analysis and Reconstruction Sound Engine.

      --
      You just got troll'd!
    32. Re:The main usability flaw I find by DuranDuran · · Score: 1

      "Deafy"!

      For that, sir, I friend you.

      --
      "You can justify anything by putting it in quotes, adding a famous name and making it a sig" - Albert Einstein
  11. Re:GIMP will always be a gimp by stubear · · Score: 3, Funny

    You can put lipstick on a pig but in the end, you still have a pig.

  12. Audio-visuals by kabdib · · Score: 4, Funny

    With cameras and microphones and other things:

    ----

    "Our performance traces indicate large amounts of cussing when images are resized."

    ---

    "Wow. During that file open, three hundred users gave the finger to the camera."

    "And that one guy --"

    "I don't want to talk about that guy. Wahwahwahwahwah I-can't-hear-yoooo. Don't remind me of what he did."

    ---

    "Nine hundred instances of users hitting the computer with a hammer while cropping. At least, that what we think the accelerometers were saying."

    --

    "The rapid rise in temperature was probably caused by the users pouring gasoline on the system and lighting a match. We'll try to address that issue in the next release."

    --
    Any sufficiently advanced technology is insufficiently documented.
    1. Re:Audio-visuals by Unoti · · Score: 1

      Haha, good stuff...

      "Oh and look, right after trying to figure out transparency layers, 80% of our user base launched Wine and Photoshop"

  13. GIMP and multiple screens by Life700MB · · Score: 1


    IMHO, people should understand that the MDI way (that is, the "photoshop way of arranging the windows) was born under the assumption that you had only one screen to work with.

    But with X-window based virtual desktops, you just dedicate one of them to the Gimp. Check it, your Gimp experience will improve a lot!

    --
    Text link ads, the easiest way to earn money with your web

    1. Re:GIMP and multiple screens by Anonymous Coward · · Score: 0

      But Photoshop on Mac doesn't work like this. You know the platform most people who seriously use Photoshop pick. A more windows photoshopers are just EyeCandy Filter whores who pirated it since version 4.

    2. Re:GIMP and multiple screens by fastest+fascist · · Score: 1

      Unless you're a painter, and frequently have to make minor tweaks to brush settings etc. in the menus (and gimp btw doesn't seem to offer a popup-menu for that at the click of a button like photoshop), in which case you probably first of all have your pen mapped to just one of the screens, and even if you have a quickpoint area or a toggle switch to switch control to another display, you don't want to drag your cursor across all that screen real estate every few seconds. In this case using tab to hide the menus is the way to go, except that behaves a bit funny, in my Gimp at least. One press of tab hides all menus, another brings the tool menu bar back, and a third tap brings the rest of the menus back. Then to hide the menus again I have to click somewhere on the canvas, and THEN press tab again. That's a lot of clicking and key-pressing over time, let me tell you.

    3. Re:GIMP and multiple screens by samjensen · · Score: 1

      I thought it was born in the Mac world where each application can be handled as a unit, as well as controlling each individual window. In any case dedicating a virtual desktop to the GIMP might save you some headaches. [OT: Every time I think about these things I want to create a WM that works similar to OS X's and has a dvorak-qwerty keyboard layout.]

      --
      this space intentionally left blank
    4. Re:GIMP and multiple screens by NMerriam · · Score: 1

      the MDI way (that is, the "photoshop way of arranging the windows)


      No, that's the (old) Windows way of managing windows. Even Photoshop on Windows doesn't lock everything in the MDI container anymore (and hasn't for several years). Photoshop on the Mac (where it was created) has never behaved like a Windows MDI app.
      --
      Recursive: Adj. See Recursive.
    5. Re:GIMP and multiple screens by frogstar_robot · · Score: 1

      YMMV depending on the window manager you use. With kwin, I can give Gimp it's own desktop and use tab to bring up and dismiss all windows. It is also common with X window manager windows in general to "pin" them which means they stay in the foreground even you are doing work in the background. It is handy to pin tool windows, put them somewhere convenient (so I can work on the canvas with the window handy), then dismiss entirely when I won't need something else for awhile. Basically, Gimp was developed on X-Window and is a reasonably civilized app with a good Window manager.

  14. The awfulness of Photoshop by Anonymous Coward · · Score: 0

    Why do people so often complain about GIMP's UI, and not about the fucking awful user interface of Photoshop(TM)? Seriously speaking, is there anything concrete behind these complaints that goes beyond "I've been using Photoshop for 10 years, dammit, and GIMP does not behave as Photoshop"?

    1. Re:The awfulness of Photoshop by Unoti · · Score: 2, Interesting

      Yes, there seriously is. The big areas where I love Photoshop and hate Gimp revolve around layer properties, layer blending, transparent backgrounds, and grouping and copying layers.

    2. Re:The awfulness of Photoshop by Anne+Thwacks · · Score: 1
      I for one complain about the gimp. I have tried many times to use it, and have yet to even manage to open a file with the gimp.

      All I want to do is open a file, rotate it to correct for poor placement in the scanner, and then fix the gamma a bit and maybe crop it... then save the results.

      Not demanding, but last time I tried there was no viable help, and no hint as to how to do any of this.

      As for MDI, its not a problem. I am OK with MDI, not that I specially like it, My problem is "where the *&%$ are the controls?"

      --
      Sent from my ASR33 using ASCII
    3. Re:The awfulness of Photoshop by zippthorne · · Score: 1

      The controls have always been in the context menu. the GIMP people really love the right mouse button. Every time you use it it's like you're flipping off your computer.

      --
      Can you be Even More Awesome?!
    4. Re:The awfulness of Photoshop by Knuckles · · Score: 1

      I have tried many times to use it, and have yet to even manage to open a file with the gimp.

      Maybe you haven't yet managed to start your computer? Wait! -- you are posting to Slashdot.

      Seriously, how hard is it to open a file in GIMP? I launch it from the application menu and it comes up with 3 windows: one titled "Layers", one titled "GIMP tip of the day", and one titled "GIMP". Just "GIMP" has menus, so I open "File", choose "Open ...", and doubleclick the desired file. Sounds like any other application to me.

      last time I tried there was no viable help

      When, in 1995? Because my GIMP help clearly states, e.g. "The "File" Menu of the Toolbox .... 5.3 The Open command activates a dialog that lets you load an existing image from your hard-drive or an external medium. For alternative, and sometimes more convenient, ways of opening files, see the Files section."

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    5. Re:The awfulness of Photoshop by Fallingcow · · Score: 1

      In my first go at Gimp, prior to the 2.0 interface update, it took me quite a while to figure out how to save an image.

      That the option would not only be on the image's window, but in a menu that was accessed by right-clicking on the image, simply did not occur to me.

      I'd never, ever seen a program of any kind where the "save" option was not part of the same window as the main toolbar, let alone one where it was reached through a right click.

      2.0 was a big help, but I still think the interface blows compared to Photoshop, and that's with having used the Gimp at least twice as much as PS.

    6. Re:The awfulness of Photoshop by Knuckles · · Score: 1

      Agreed, but 2.0 was released when? 2003? Can we lay discussions about flaws in 1.0 to rest, please?

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    7. Re:The awfulness of Photoshop by VJ42 · · Score: 2, Insightful

      Why do people so often complain about GIMP's UI, and not about the fucking awful user interface of Photoshop(TM)? I totally agree, as a casual user, I actually find GIMP easier than Photoshop. However, as I noted above I'm not letting GIMP off that easy, IMO it's not competing against Photoshop(do Pros use GIMP?), for me, it's competing against the likes of Paint Shop Pro (and other mid range image manipulation packages), which is a hundred times easier to use than either.
      --
      If I have nothing to hide, you have no reason to search me
    8. Re:The awfulness of Photoshop by Anonymous Coward · · Score: 0

      I for one complain about the gimp. I have tried many times to use it, and have yet to even manage to open a file with the gimp. You're right. "File | Open..." is pretty frig'n complex.
    9. Re:The awfulness of Photoshop by dbcad7 · · Score: 1
      I would pay for PaintShop Pro for Linux.. like I did for windows.

      However since it's not being done, I do use Gimp. It took awhile, but I can do pretty much anything a non graphics professional user like me wants to do.. I have just been using the stock install of Gimp (Ubuntu and Xubuntu).. I mean to one day search to see what other effects and filters are out there. not that the stock set is bad, but maybe it's just fond memories of PaintShop Pro that lead me to believe I could do cooler things with their effects.

      --
      waiting for ad.doubleclick.net
    10. Re:The awfulness of Photoshop by Zantetsuken · · Score: 1

      One of my favorite Photoshop tools is the clone stamp for making things/people disappear and put the wall back in behind whatever I removed - PS: 1 button, alt-click to specify source, then click on area to duplicate it to.

      I guess I'm just not into graphics enough to have any need to familiarize myself with GIMP enough, but for me with GIMP, its not just "Where is the equivalent button at" because in Photoshop I find it such a major tool, its inconceivable to not have it easily accessible. Just how the hell do I get the same effect in GIMP without going through 30 more steps? And I'm not talking about consolidating this into 3 tools I have to use in order - I mean 1 tool, basically how it is in Photoshop, so that I can use it repetitively (like once every 2 seconds repetitive to clone an entire area) - but redefining the source within a quarter inch away of where I started putting the clone in to keep it from developing jagged square tiles every 2 inches...

    11. Re:The awfulness of Photoshop by BigSven · · Score: 1

      It works exactly like that in GIMP. There's a dedicated tool for it, called the "Clone tool", and you will find it located in the toolbox. The tool works exactly like you described your workflow in Photoshop. No 30 steps, no need to use several tools.

    12. Re:The awfulness of Photoshop by Zantetsuken · · Score: 1

      Alright, I was going to list the tools on the tool pallet, but about a third of the way through listing the tools on the default pallet, I found the "Clone tool" in the "Dialogs" > "Tools" dialog box, and that clicking on it selected the appropriate tool that happened to already be on the pallet - but it sure wasn't labeled "Clone tool" - instead it was "Paint using patterns or Image Regions". If I could at least have "Paint using patterns or Image Regions (Clone)". Why is the dialog box for customizing the tool pallet label it as clone and not the pallet itself? Its a consistency issue that might be minor to some, but it sure confused the hell out of me for quite a while...

  15. GIMP's Typical Use by Anonymous Coward · · Score: 2, Insightful

    If they want to know how GIMP is typically used, that's easy. GIMP's typical and most popular use is for people to say, "Hey, you can edit your photos under Linux with GIMP, and you don't have to use Wine and Photoshop."

    But professionals using GIMP for doing real work? That's atypical. Hopefully that will change.

  16. Scary by suv4x4 · · Score: 4, Insightful

    You know, how do you recognize a project is someone's pet project? It's an overcomplicated solution for a problem with a trivial solution.

    Want to find out what makes the GIMP ui suck? Ask the damn users! They won't exactly shy away from telling you.

    I'm a Photoshop user and I have GIMP installed here to use the occasional esoteric plugin functionality. Let me tell you few things you can immediately get busy fixing:

    1. for some reason GIMP developers decided every single thing needs its own window and its own menu bar. It's weird as f*ck: put the entire layout in a single window with integrated panel layout (similar to how Eclipse does it, for example).

    2. each plugin is its own modeless exe dialog that takes arbitrary amount to start after it was called (at which time you can modify the processed image.. sometimes, and sometimes GIMP crashes because of it): create a proper lean plugin API and modal plugin dialog.

    3. the menus and options are all over the place: there seems to be no strategy at all about what goes where

    4. GIMP has really bad startup time, and performance, compared to commercial graphics editors (such as Photoshop)

    5. There's no way at all to organize your layers in a more complex setup: there are no layer groups, layer folder, or anything like that. It's just a big sack of flat layers, that you can select one at a time, and link them together. This is Photoshop 4 level functionality, and most graphics editors are waaaay past that by now.

    6. There are no proper drawing tools in Gimp at all. For a graphics package that claims to be targeted at geeks making icons and web devs making web designs, this is ridiculous. We're forced to fake our ways with selection tools and scripts, which covers only a fraction of what we need.

    7. A personal issue I have with Gimp: no proper grid. I use the grid in Photoshop all the time, set on unobtrusive "pixel" mode, and usually at 8, 16, 32 pixels with subdivisors. In Gimp, no subdivisors, no pixel mode, and for some reason the *mere fast of displaying* the grid, makes everything slow down to a crawl.

    1. Re:Scary by Soulfry · · Score: 3, Informative

      There is a very active group of individuals who are currently doing things like expert walkthroughs and observational studies: See http://gui.gimp.org./

      Our data is intended to complement this data by quantifying the ubiquity of tasks/activity/system setups. For example, what are typical resolutions of monitors? This type of information can help focus design by indicating what types of interaction designs are feasible and not feasible given the hardware of current users. What we've seen so far is a far greater number of 1024x768 resolutions than anticipated. Breaking these numbers down to see where in the world these resolutions are being reported is one of the next steps we plan to do to better contextualize the data. See http://www.ingimp.org/stats/monitors.

      We also have some emperical data to support the notion that the multiple windows design choice is not the best. Our data indicate that the percentage of the monitor covered by the document window is typically about 50% for most users (again, see http://www.ingimp.org/stats/monitors ). Most Photoshop users seem to maximize their document windows; with GIMP, this seems to happen much less frequently, probably because doing so obscures GIMP's other windows.

      Michael Terry

    2. Re:Scary by Anonymous Coward · · Score: 0

      5. There's no way at all to organize your layers in a more complex setup: there are no layer groups, layer folder, or anything like that. It's just a big sack of flat layers, that you can select one at a time, and link them together. This is Photoshop 4 level functionality, and most graphics editors are waaaay past that by now.

      I believe this is an artifact of the GIMP's native file format, XCF. This file format is not only undocumented, it's purposefully undocumented.

      6. There are no proper drawing tools in Gimp at all.

      I've complained about the same thing. Drawing a ring in another graphics application: pick the ring drawing tool, drag from one point to another. Drawing a circle in the GIMP: select the spherical selection tool, select a circle, pick the fill tool, fill the circle, go to a menu and shrink the selection, then erase the selected area.

      When I complained about it being too difficult and not at all sensible? I got told that it was my own fault for not reading the manual. That's right, you need to read the tutorials to find out how to draw basic shapes!

    3. Re:Scary by suv4x4 · · Score: 1

      Well, I wish you luck Prof. Terry, but I see from a mile away this is not going anywhere. For what I know, software is written by humans for humans, and the best way to find out what humans are after is to just do a good old usability study with

      a) asking people directly what are they frustrated with

      b) monitoring people directly (as: in person, or on video) how they use the program and what they struggle with

      This is what commercial software companies do since they don't have years of free time to fiddle with collecting artificial data to "guess" upon. And it works.

      In your other post you said how you can use the logs to identify Photoshop users since they accidentally use CTRL+D for the wrong action. Here's a perfect example of overcomplicating things. You could've just asked the people participating: are you a Photoshop user. That eliminates any uncertainty and complexity associated with monitoring logs and "guessing" what the users' background is.

      Another example from your post up there:

      We also have some emperical data to support the notion that the multiple windows design choice is not the best. Our data indicate that the percentage of the monitor covered by the document window is typically about 50% for most users (again, see http://www.ingimp.org/stats/monitors [ingimp.org] ). Most Photoshop users seem to maximize their document windows; with GIMP, this seems to happen much less frequently, probably because doing so obscures GIMP's other windows.

      As a graphics designer who tried to use this program, I could've told you all of the above immediately, and in a much simpler fashion. I know because *I use* the program. I don't guess how other people use it.

      You'd ask me "what do you think about multiple windows" and I'd tell you "they suck, merge them into a single window with panels". No need for "empirical data supporting notions", or "statistics for percentage of screen covered by document window".

      But I hope in a few years you collect enough empirical evidence to catch up with the rest of us, and finally someone does something about it, before GIMP is completely forgotten by the community.

    4. Re:Scary by Anonymous Coward · · Score: 0

      > put the entire layout in a single window with integrated panel layout

      You didn't think that one through. What happens when you have two or more monitors? Then you're stuck not being able to use 50% or more of your screen real estate unless you cover everything behind the main window. For example, with GIMP I can put my original image on my small 19" display to the left, the drawing tools and e-mail on the 22" widescreen to the right and my working image on the 30" display in the middle. When I use Photoshop, I'm limited to only using a single monitor or dragging the Photoshop window across to another monitor which doesn't work well because it hides other windows and because of the different resolutions of the monitors. Programs like Photoshop and Eclipse are harder to use than necessary because they limit you to using a fraction of your screen area.

    5. Re:Scary by Soulfry · · Score: 3, Interesting

      Qualitative methods like the ones you suggest -- observations, interviews, ethnographic methods, contextual design -- are some of the best methods out there to uncover the data you suggest should be collected. In fact, my HCI class focuses exclusively on these methods. They're cheap, they're fast, and you got a lot of data very quickly.

      ingimp doesn't intend to supplant these techniques. In fact, it would be a mistake for people to assume it could or should. And the GIMP project already has a good group of people who are using the very techniques you propose (see http://gui.gimp.org/ ).

      However, GIMP is a very general purpose application and there are limited resources to improve it. How should future development efforts be prioritized? Are most users experts or novices? Do they use it to color correct images, crop and resize them, or are they doing more sophisticated things like graphic design over hours of use? What are common workflows? Are they the same workflows we assume people are doing, or are they completely counter to our expectations?

      Quantifying broad usage is not something that can be done by qualitative methods alone, but it can help to focus future development efforts if you can better characterize your user base, how they're using the software, and how many people are using it in various ways. With this data, you can optimize for the minority or the majority -- at least you know who you are optimizing for.

      One of the benefits of this data is that longitudinal patterns of usage can be discovered that wouldn't come out in laboratory based usability studies. For example, if a new feature is added, these stats can help you determine whether people are adopting and using the new features as expected. Longitudinal data is rare -- we're building a longitudinal data store right now unlike any other in the open source community.

      One of the challenges that is glossed over is that creating a sustainable usability infrastructure is no trivial task. We're collecting data in a very unobtrusive way that requires very little effort on the part of the user, and that data has a fairly high degree of ecological validity -- people are using the software in their own environments, not in an artifical usability lab. Again, while not a replacement for qualitative methods, the data we collect do help answer other questions valuable to guiding development efforts in a resource-constrained environment. Other ideas on creating a self-sustaining usability infrastructure, which does not overly burden the developers or users, are certainly welcome.

      On a final note, there are benefits to this data beyond usability itself. For example, we've found that people use the most frequently used command stats to discover features/commands/plug-ins they weren't previously familiar with, and which they find valuable. The data set is a bit richer than it at first seems.

      Michael Terry

    6. Re:Scary by kayoshiii · · Score: 1

      1) Yeah Ok I will give you that.... The single menu was a comprise from only offering items via a right click context menu.... Personally I don't mind having a right click context menu. But I guess I am just used to it.

      2) Horay for a modeless interface. Yes It lets you shoot yourself in the foot but lets face it a moded interface sucks it makes your workflow a lot less flexible. No I can't do anything because I have the colour selection window open and other such brainless stuff.

      3) The GIMP menus have a logic to there layout there is absolutely a strategy of what goes where. It is different to Photoshops I personally think that it is clearer (at least in the dev version).

      4) The Gimp (on linux) absolutely kills Photoshop (on Windows) in terms of startup time. In terms of performance Photoshop is has a handy lead on just about everything out there and I would say that the gimp sits pretty well within that pack - though I do conceed that older versions of gimp needed a bit of tuning to perform well. I have in past used it to open images which were so large that photoshop absolutely choked. The trick was to zoom in the image so that the tile cache could hold all the visible chunks in memory which was fine in this case because we were editing fine details.

      5) I will conceed that point. It is part of the fabled GeGL that is finally comming.

      6) The gimp doesn't offer vector layers per say but it does offer drawing tools. One can create straight lines by holding down shift with any of the drawing tools. selections and curves can be filled and stroked and complex shapes can be created by means of a plugin. However if you are working on mainly geometric shapes you will get a lot more milage out of inkscape the GIMPs Sister program. you can even drag and drop svg files created by inkscape directly into the paths menu or import and render them.

      7) I will give you that one

    7. Re:Scary by MMC+Monster · · Score: 1

      Well, I hope some of the developers listen to the suggestions that you have. The multiple-window approach is fine if you assume everyone has large monitors and use virtual screens (so that GIMP fills up an entire screen with it's multiple windows). You are spot on that maximizing windows aren't done in GIMP because of obscuring other GIMP windows. I hope some developers will take it to heart and code a single window mode (preferably as a new default).

      --
      Help! I'm a slashdot refugee.
    8. Re:Scary by Anonymous Coward · · Score: 0

      When I complained about it being too difficult and not at all sensible? I got told that it was my own fault for not reading the manual. That's right, you need to read the tutorials to find out how to draw basic shapes!
      As long as FOSS keeps going the RTFM route instead of the KISS route, they'll never take any significant marketshare.

    9. Re:Scary by marcosdumay · · Score: 1

      "What we've seen so far is a far greater number of 1024x768 resolutions than anticipated."

      Really, what definition did you expect? 1024X768 has being the defaul resolution for Linux for ages (X used to not work very well with anything else). It's being replaced with 1280X1024, but that doesn't happen overnight.

      Also, Windows users that care to download GIMP would probably care to change their video mode.

    10. Re:Scary by __aaltii7299 · · Score: 1

      You know what's sad? It's not a contest, he's not challenging you, he's telling you as a user what he needs.

    11. Re:Scary by suv4x4 · · Score: 0, Redundant

      Michael, please don't bother wasting your time arguing with the Photoshop fanatics. These guys are not interested in helping improve the state of free software, they are simply here to browbeat anyone who would consider using it instead of their beloved adobe products.

      Did you miss the part where I said Krita is a lot better development than GIMP? How do you explain this.

      "Photoshop fanatics"... jesus, you guys are desperate.

    12. Re:Scary by Soulfry · · Score: 1

      That may be so (1024x768 being the default resolution for Linux for ages), but 90% of the ingimp users so far are Windows users (see http://www.ingimp.org/stats/system_stats ). So your explanation of the result doesn't explain this finding.

      Michael Terry

    13. Re:Scary by Anonymous Coward · · Score: 0

      I don't have any problem with RTFM itself. It's when you need to RTFM to find out how to do what should be immediately obvious that it becomes a problem. This is something I've only seen with the GIMP, not with Free Software in general. The GIMP developers seem to pride themselves on having an obtuse interface. Steep learning curves are one thing, being difficult for the sake of it is another entirely.

    14. Re:Scary by syousef · · Score: 1

      Try gimshop. It addresses many but not all of your issues.

      http://gimpshop.blogspot.com/

      --
      These posts express my own personal views, not those of my employer
    15. Re:Scary by Kent+Recal · · Score: 1

      How should future development efforts be prioritized?

      I like to consider gimp a proof of concept. Back in the days it proved that free software is capable of creating something "similar to photoshop".
      Ugly, cumbersome, nobody really wants to use it but hey, image editing for $0 dollars!

      Many years have passed since that time and the adoption rate of gimp should have told you by now that something very essential must be wrong (under the premise that you're targeting a mainstream audience and not some very special niche). If you were to track gimp usage by technical means you'd see that your "conversion rate" is abysmal. Just about every linux user out there has probably tried gimp - once or twice. I even know a few people who tried to use it for serious work - a few weeks before giving up.

      And it's not like the basic wrongs hadn't been pointed out a trillion times over just about any communications device ever invented.

      So, if today you still have to ask "what issues to address" then i don't think you'll be able to understand, much less fix them properly.

      Maybe your idea of what GIMP should be like simply differs too much from what most (occassional and pro) users want out of an image editing tool.
      But hey, you are the creators and not obliged to anybody. So why not rather focus on the strengths and your vision of GIMP?
      Why try to fix "issues" that haven't bothered you and the regular GIMP users in all the years?

      I doubt that you can turn GIMP into krita in reasonable time anyways, even if you wanted to.
      And that's what any kind of usability feedback would tell you to do (yup, in my dayjob I'm a fortune teller).

      If you seriously want to open GIMP up for a broader audience I think I have a better idea, though.
      Make the UI customizable. Really customizable. As in, every single UI item such as toolbars, buttons
      and menus should be drag'n'droppable to any location (yes, even menu items to buttons and vice versa).
      Furthermore make all behaviours customizable, like whether to open new images in a window or tab, etc.

      Then provide profiles (and heck, a repository for user customized profiles) that imitate the UIs of
      old-gimp, photoshop, paintshop, and so on. You get the idea.

      What, GTK doesn't do that? Well, I didn't say it wouldn't be a shitload of work... ;-)
    16. Re:Scary by r00t · · Score: 1

      1024x768 was never the default for Linux. The default has always been to use the highest resolution possible. Often this has even meant a 256-color mode with a low refresh rate and blurry little text.

      1024x768 does in fact sound like the default for Windows, at least as chosen by the PC vendors. For many years it was 640x480. Then they went up a bit, I think first to 800x600 and now to 1024x768. Older people want big text, and lots of Windows apps break if the font sizes change, so the PC vendors use a low resolution.

    17. Re:Scary by Chandon+Seldon · · Score: 1

      You know what's sad? It's not a contest, he's not challenging you, he's telling you as a user what he needs.

      In that case, what he's saying he needs is Photoshop - which he already has. This isn't even the normal "can't switch to Linux because GIMP isn't Photoshop" discussion - the original poster has even said he's happy using Windows.

      The GIMP has made different design decisions than Photoshop, and the fact that Photoshop users like Photoshop better isn't even interesting anymore.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    18. Re:Scary by dunkelfalke · · Score: 1

      the answer is problably because the 15" tft screens were quite popular and most of them have exactly this resolution.

      --
      Conservatism: The fear that somewhere, somehow, someone you think is your inferior is being treated as your equal.
    19. Re:Scary by Anonymous Coward · · Score: 0

      I think maybe the programmers are much happier interacting with algorithms than trying to interact with actual people.

      Point #1 is right on. Dealing with multiple windows bugs me in both Photoshop AND the GIMP.

  17. SUV / New Coke / added armor fallacy. by Ungrounded+Lightning · · Score: 5, Insightful

    The project hopes to answer questions such as 'What is the typical monitor resolution of a GIMP user?' and 'Is the GIMP used primarily for photo editing or drawing?'"

    Looks to me like they're about to fall into the fallacy that caused Daimler-Chrysler to do a redesign of the Jeep line that killed their market.

    The marketing department looked at what fraction of SUVs were actually used off-road. They came to the conclusion that it was small. So they redesigned their line to be more comfortable on-road at great cost to its off-road performance.

    Turns out that a significant fraction of their market was people who NEEDED the off-road capability - and had the resources to pay for it, reliably buying cars, year after year, through all economic cycles.

    Jeep stopped being the car they needed and became another clone of the rest of the market: "Mall Terrain Vehicles" that LOOK like an off-road car but are really just a funny-looking small/high van that qualifies as a "truck" to escape the fleet mileage regulations. Their guaranteed market went elsewhere and they were in head-to-head competition with a slew of vehicles over which they had no advantage.

    Similarly, Coke looked at all the people buying Pepsi, saw that they were younger and that Pepsi's main difference was that it was sweeter, and replaced Coke with New Coke, which was sweeter yet. Result: People who drank Coke because they liked a less-sweet drink switched to Pepsi.

    And then there was the high-ranking officer in WW II who spent months counting all the bullet holes on the returning bombers, then did a big presentation on how those areas should have armor added. At the end of his presentation a lower-ranking officer asked "Shouldn't we, instead, add more armor to those areas that are only lightly holed? After all, this sample represents only the planes that came back."

    = = =

    I think the same thing could happen here: Paying attention to what people do a lot of just focuses on what you're already doing right - at the cost of ignoring the things that people do occasionally, or only some people do, but which they need to have. Further, the things they do rarely may be used rarely specifically BECAUSE they're hard to use and the interface needs improvement.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:SUV / New Coke / added armor fallacy. by Soulfry · · Score: 1

      One of the things we do to combat the potential issues you identify is to carry out observations of real users to understand what high-level behaviors are associated with the low-level log data. For example, we discovered that some users occassionally duplicate a document and then immediately close it. Doesn't happen often, and only with a subset of users.

      Why do they do this? Because they are Photoshop users using Photoshop key bindings in GIMP -- Ctrl-D deselects in Photoshop and duplicates in GIMP. So with this set of actions in the log, we can identify Photoshop users using GIMP.

      The other way we address this problem is to provide multiple perspectives on the data. Looking at the Command Stats, you'll notice that we break down the most frequently used commands in a number of ways: By session, by user, and so on. There are multiple ways to consider "most frequently used commands" and we are sensitive to the fact that any one perspective is not the one correct way. As an example, raw counts of command use will put tools like the paint brush at the top of the list. But perhaps only 10% of the population uses the paint brush. So we also provide information on the percent of users who use a particular command to grant you these additional perspectives.

      Finally, we're constantly adding new stats; we've only just begun mining this data.

      Michael Terry

    2. Re:SUV / New Coke / added armor fallacy. by Blakey+Rat · · Score: 1

      I agree with your general sentiment, and I also agree that this project might be a dead-end. A better approach would have been to take the man-hours spent creating this software and instead use it on proper man-on-the-street usability studies. Grab someone, sit them in front of GIMP, and have them create a greeting card or something. Record it on video and watch it later on, they'll get a lot more information than this automated system can obtain.

    3. Re:SUV / New Coke / added armor fallacy. by X_Bones · · Score: 1

      What makes your analogy a false one is that the ingimp folks aren't like the marketing departments from the big companies you mentioned. They're not collecting broad 'market data', if you will, from Photoshop/PaintShop/CorelDraw/etc. users (or all SUV drivers, or all soda drinkers). They're doing exactly what you seem to want them to do, which is ask their target users how to improve the product they currently prefer.

      It's as if Chrysler sold you a Jeep with sensors on the steering wheel and seat cushions. You'd already decided to buy the Jeep, and Chrysler wants to know how you use it to make future versions more comfortable and responsive.

  18. Roll Outpackages by pembo13 · · Score: 1

    If they roll out a package for Fedora, I'll be installing this soon. I like the idea of Gimp, but I always fumble around the interface, and rarely use it when I am not in a hurry.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  19. As I understood it... by Anonymous Coward · · Score: 0
    'Is the GIMP used primarily for photo editing or drawing?'

    My impression is that it's primarily used to paste Tux onto pictures of lingerie models by teenagers who then loudly insist that it's every bit as suited for professional use as Photoshop.

  20. Re:GIMP will always be a gimp by Aminion · · Score: 5, Funny

    You can put lipstick on a pig but in the end, you still have a pig.
    ... and that pig will be the object of thousands of zoophiles' hot fantasies! Wait - what were we talking about...?
  21. what are you, 4 years old? by Anonymous Coward · · Score: 0

    is there anything more idiotic that you can complain about... perhaps the colors of the icons or the hair style of the developers?

    1. Re:what are you, 4 years old? by morgan_greywolf · · Score: 1

      Now that I think about it, the icon/mascot doesn't even look like a 'gimp' to me, it looks a bit like a fox. ;)

  22. Fanboyism, user interfaces... by Spy+der+Mann · · Score: 5, Insightful
    Another key to remember is that it's free. That goes miles in my book.

    That is an awful mistake for F/OSS fanboys. "Oh, it's free, so we shouldn't complain". This is like being blind to the problem. If it's free and it works, why isn't EVERYBODY using it? (In other words, why is Mozilla Firefox MUCH MORE popular than the GIMP? Think about it).

    Sometimes we can forget that graphical applications are meant to be used by designers who use most of their time retouching photographs and stuff. Here, time is money. And if the lack of usability in the GIMP makes me spend 5 times more the time than I would with Photoshop (and i'm being considerate), it's just not worth switching. To put it another way, Photoshop's user interface _IS_ worth the price. I still can't believe the GIMP guys CANNOT make something as user friendly (or don't want to, which is worse). It shocks me and frustrates me.

    A quote from a designer's blog:

    You know that Linux is ready for governments and businesses when a 30 day review points out DVD and photo editing as the main weaknesses -- and not because there are no Free Code replacements, but because they aren't quite good enough yet. The reviewer only tried two applications, GIMP and Kino. I share his feelings towards the GIMP photo editor, which I regard as an "old school" Free Code project where the developers would rather tell the users why their program is, in fact, highly usable than conducting serious usability tests and making improvements. To be fair, the existing GIMP user base, which is used to the current implementation, may also resist significant changes.

    That is not to say that the quite remarkable GIMP functionality could not be wrapped into a nicer user interface. GIMPShop is one such attempt, which I have not tried. I hope that it will become a well-maintained fork; I don't have much hope for GIMP itself to improve in the UI department. I am personally partial to Krita which, while still young, seems to have generally made the right implementation decisions, and is truly user-focused (as is all of KDE -- I love those guys). I am not a professional photo editor, so I don't know how mature Krita is for serious work. It is good enough for everything I do.


    Ooooh... what a bold statement! The GIMP is *NOT* user-focused. Don't tell me.

    See, professionals don't want just "a better pile of poo" to do their imaging work. They (and I, too) want something that IS EASY TO HANDLE. Because in graphical applications, form is function. And this is something that many programmers (at least many of those that I've discussed with) simply fail to understand.
    1. Re:Fanboyism, user interfaces... by mrchaotica · · Score: 1

      In other words, why is Mozilla Firefox MUCH MORE popular than the GIMP? Think about it.

      <smartass reply>Uh, for the same reason that Internet Explorer is MUCH MORE popular than Photoshop?</smartass reply>

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    2. Re:Fanboyism, user interfaces... by Anonymous Coward · · Score: 0

      "That is an awful mistake for F/OSS fanboys. "Oh, it's free, so we shouldn't complain". This is like being blind to the problem. "

      Yeah, isn't being blind to the problem a real bitch? Just like people like you who go, "Well, these stupid suckers are gullible enough to program this application for ten years and release all of their work for free! That makes them my-y-y BITCH!"

      You are doing the equivalent of taking a shit on the floor in the middle of the public library and wiping your ass with pages ripped from the books. Fuck you.

    3. Re:Fanboyism, user interfaces... by suv4x4 · · Score: 2, Funny

      Yeah, isn't being blind to the problem a real bitch? Just like people like you who go, "Well, these stupid suckers are gullible enough to program this application for ten years and release all of their work for free! That makes them my-y-y BITCH!"

      The problem here isn't that graphics designers are actively seeking to make fun of GIMP. It's that GIMP's developers and fans keep trying to push GIMP down our throat. It gets really old real fast, and we're forced to tell you straight in the face that GIMP sucks compared to the majority of commercial products out there. It sucks even compared to other open source editors (such as Krita).

      Designer: "Shoot, that CS3 upgrade price is steep. But I'll pay it of course..."

      GIMP fan: "Dude, you gotta switch to GIMP! It's F*R*E*E and [insert drivel about conspiracies, "evil", information wants to be free etc]"

      Designer: "I've given GIMP several shots, it's really very far from a mature product, I'll pass on it."

      GIMP fan: "Dude, it's F*R*E*E, no upgrade price, isn't this what you're complaining about".

      Designer: "I complain since there's no cheaper alternative, GIMP isn't an alternative."

      GIMP fan snaps and goes into an endless cycle:

      GIMP fan: "No, dude, it's F*R*E*E, use it!"

      GIMP fan: "No, dude, it's F*R*E*E, use it!"

      GIMP fan: "No, dude, it's F*R*E*E, use it!" ...

    4. Re:Fanboyism, user interfaces... by ClosedSource · · Score: 1

      "Well, these stupid suckers are gullible enough to program this application for ten years and release all of their work for free! That makes them my-y-y BITCH!"

      The bitch doth bitch too much, me thinks.

    5. Re:Fanboyism, user interfaces... by Brusco · · Score: 1

      Confucius say: Ploglammel design application same as blicklayel design house.

    6. Re:Fanboyism, user interfaces... by Anonymous Coward · · Score: 0

      That is an awful mistake for F/OSS fanboys. "Oh, it's free, so we shouldn't complain".

      Greedy little bastard, aren't you. "Aw, you only gave me plain chocolate ice cream. I wanted the kind with chocolate chips!"

      Sometimes we can forget that graphical applications are meant to be used by designers who use most of their time retouching photographs and stuff.

      Self centered, too. I do Job X, therefore every tool that can be used for Job X is "meant" to be used by me.

      Grow up. A lot of us need software that is cheap and fixable. A lot of us need software that can be installed without preparation anywhere there is a good Internet connection.

      I still can't believe the GIMP guys CANNOT make something as user friendly (or don't want to, which is worse). It shocks me and frustrates me.

      Then start improving it, you fool. Free software is what you make it.

      They (and I, too) want something that IS EASY TO HANDLE.

      Show us the patches.

    7. Re:Fanboyism, user interfaces... by Anonymous Coward · · Score: 1, Interesting

      Greedy little bastard, aren't you. "Aw, you only gave me plain chocolate ice cream. I wanted the kind with chocolate chips!"

      Naive little fool, aren't you? "It's free, it must be perfect, and if it's not, other people can fix it up to make it what they want!"

      Self centered, too. I do Job X, therefore every tool that can be used for Job X is "meant" to be used by me.

      Self-centered? As part of the group a product is aimed at, the tool is meant to be used by him. That's the joy of marketing, product design, and statistical analysis.

      Grow up. A lot of us need software that is cheap and fixable. A lot of us need software that can be installed without preparation anywhere there is a good Internet connection.

      The rest of us need software that is usable. The fact is that most people think GIMP has a crap interface. Getting all loud and stroppy like a slighted child is no way to defend your favourite tool.

      Then start improving it, you fool. Free software is what you make it.

      Show us the patches.

      And here we have it, folks: the key weak point of OSS. Perhaps, more accurately, the key failing point of the OSS fanboys.

      Not everyone has the appropriate training. Of those that do, not everyone can spare the time to fix it. Assuming an interface designer puts the effort into fixing it up and submitting it, what do you suppose the GIMP developers will do with those patches? Rumour mill has it that they've told interface designers to piss off, in the past.

      Here's the bit where you say "well, they can just fork it and make their own version, and if it's truly better, it'll take off."

      Not everyone can manage a project.

      So, keep your naive fanboy attitude in check, move out of your parent's basement, and into the real world. It's not all roses out here.
    8. Re:Fanboyism, user interfaces... by Anonymous Coward · · Score: 0

      It's worse than you think! The grandparent insulted someone because he disagreed!

    9. Re:Fanboyism, user interfaces... by Spy+der+Mann · · Score: 3, Interesting

      Show us the patches.

      And here we have it, folks: the key weak point of OSS. Perhaps, more accurately, the key failing point of the OSS fanboys.

      EXACTLY! :)

      Fanboys fail to understand that there is something in the world called CUSTOMERS, unable to program, unable to send patches, but with specific needs. Fanboys like software made "by programmers, for programmers". Or actually "by programmers, for themselves and screw everyone else, if you don't like MY software, fork it or fork you!".

      In the link I mentioned about "a better pile of poo" we see that this kind of software, by programmers for programmers, was made in the early stages of software developers. Today, software is made by teams of developers, artists and user interface experts (aka "interaction dudes").

      You know what's interesting? That fanboyism is usually greater in linux circles. Windows developers are used, accustomed to nice, friendly user interfaces - and although most of the time they make crappy software with awful programming techniques in Visual Basic, sometimes they excel and make wonderful user interfaces. (Now mix nice user interfaces with an MVC approach and woo hoo! )

      I tend to think that Linux programmers are so used to hack and slash code, that they forgot what it feels like to have a nice UI, with keyboard,mouse shortcuts, context help, cut-copy-paste, etc etc. Most of the Linux open source software I've tried have a crappy interface. This is why I prefer Irfanview, Pixia and Virtualdub to the GIMP or AVIDemux respectively. By the way, I tried Jahshaka once. What an awful UI.

      Update: This is just in. A friend of mine just told me: "gimp is a bunch of garbage. I downloaded it and the gui is adobe photoshop chewed up and sneezed at the monitor". Your honor, I rest my case :)
    10. Re:Fanboyism, user interfaces... by Draek · · Score: 1

      and how, please tell, do these "CUSTOMERS" help the project? they don't contribute money (it's free), and they don't contribute source-code (they're not programmers), so besides the ego-stroking that follows having a larger market-share than $PROPIETARY_COMPANY_X, why would a non-commercial open-source project try to please *them* instead of, y'know, people who do give something back to it?

      and that's without counting your oh-so-fanboyish remark about Windows users being used to nice, friendly user interfaces of course, that anyone who has ever used said OS would find laughable.

      --
      No problem is insoluble in all conceivable circumstances.
    11. Re:Fanboyism, user interfaces... by callistra.moonshadow · · Score: 1

      Thing here is -it's not a pile at all. GIMP works great with my WACOM digital tablet as well. I do a bit of art and have a small online gallery. I render first with paper and pencil, charcoal, or colored pencil, scan in and then do the rest digitally. GIMP is wonderful. It works just fine. I agree with a prior poster that said it's all about familiarity with the interface. I think that some people don't want to rtfm or deal with something that isn't mom's Photoshop. The free part is just an added bonus.

      --
      --Cally
    12. Re:Fanboyism, user interfaces... by dave1791 · · Score: 1

      "why would a non-commercial open-source project try to please *them* instead of, y'know, people who do give something back to it?"

      With that kind of arrogance, only a programmer would ever bother using it.

    13. Re:Fanboyism, user interfaces... by FooBarWidget · · Score: 1

      Why is it arrogance? Suppose your grandmother bakes bread for people for free (for whatever reason). Hundreds of people call her to tell her that her bread sucks, and demand better bread. Your grandmother doesn't want to and says that she isn't getting paid. Is your grandmother being arrogant?

    14. Re:Fanboyism, user interfaces... by kimvette · · Score: 1

      Oh really? When did Microsoft start bundling Mozilla Firefox with Windows? ;)

      Seriously though: Photoshop got where it is because it is the best tool for editing images, with the best interface.

      Corel tried to compete for many years by offering the second-to-last and third-to last version(s) of their suite at a really, really low price (used to be able to pick up a shrinkwrapped CD in a cardboard sleeve at stores like CompUSA for well under $30, sometimes under $20 - they know professionals will want the latest version and will pay a premium for it) and while it obviously sells well, I still see that Adobe dominates the market despite Corel's taking that approach for many years.

      I like The Gimp but there are many things seriously broken with it:

        - the UI model in general. When I raise a document window, it should raise ALL associated palette dialogs with it. I should not have to manually hunt for each dialog and raise it manually. They implemented a partial fix in preferences but it does not work well.
        - Those G-D file open/save dialogs. The Gtk developer who decided dumbing those down makes workflow easier out to be drawn-and-quartered. Those dialogs are what I hate the absolute most about Gnome in general.
        - Effects are lost after making any changes (in effect, to mimic Photoshop's effect you clone what you want to have an effect on to another layer, run a suite of filters on it, and adjust the opacity - such as outer glow or shadowing on text. Make a change to the original and you have just lost that effect and have to re-do the entire thing by hand)
        - Text styles are lost after making any changes.
        - layer handling is unintuitive. The floating layers are a good idea, but there should be a "paste as new layer" option to simplify it for new users; don't complicate it by turning it into many steps.

      Some of the posters in here claim that Gimp hurts because it tries to do so much; this sounds like the "one task, one tool" mantra that drove Unixy operating systems for about 30 years. In a CLI that philosophy makes sense, but in a suite one should try to offer a complete solution to improve workflow. Otherwise, why would openoffice.org and koffice be so popular? I know there are still folks who write letters and reports in LaTeX using emacs or vi, and that's wonderful to them, but while you're busy creating your header and footer, the more reasonable person using a WYSIWYG editor has already printed out or emailed the letter and has moved on to the next task.

      The Gimp should manage windows better, that godawful file dialog needs to be fixed, and layer effects are a very desirable feature. Think of the user, and while KISS should apply at some level, it shouldn't apply when it cripples the application or hampers workflow, or otherwise complicates the user experience. Sometimes complex tasks need a complex solution; in those cases don't deny the user that solution but design it in as logical a way as possible. Adobe has made billions off of their suite, WITHOUT using monopolistic tactics that Microsoft did. They obviously did something right. Personally I hope Adobe makes their suite available on Linux - it would be interesting to see what happens to gimp and inkscape. Would they continue to gain market share (albeit slowly) or would interest in them die?

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    15. Re:Fanboyism, user interfaces... by mrchaotica · · Score: 1

      Oh really? When did Microsoft start bundling Mozilla Firefox with Windows? ;)

      The point I was getting at is that more people care about web browsers than do professional-level* image editing software.

      the UI model in general. When I raise a document window, it should raise ALL associated palette dialogs with it. I should not have to manually hunt for each dialog and raise it manually. They implemented a partial fix in preferences but it does not work well.

      First, understand that The GIMP is cross-platform, and that different platforms use different UI models. The platform you're running it on probably isn't the one it was initially designed for. Second, understand that The GIMP is not a window manager, and therefore it is not (or at least, should not be) its job to manage windows! If you're having problems with managing The GIMP's windows, get a better window manager (and if you're using MS Windows, and therefore can't replace the window manager, get a better operating system).

      Those G-D file open/save dialogs. The Gtk developer who decided dumbing those down makes workflow easier out to be drawn-and-quartered. Those dialogs are what I hate the absolute most about Gnome in general.

      Perhaps the best idea would be for the GTK developers to make their toolkit support native dialogs when running on non-X platforms.

      Effects are lost after making any changes (in effect, to mimic Photoshop's effect you clone what you want to have an effect on to another layer, run a suite of filters on it, and adjust the opacity - such as outer glow or shadowing on text. Make a change to the original and you have just lost that effect and have to re-do the entire thing by hand) - Text styles are lost after making any changes. - layer handling is unintuitive. The floating layers are a good idea, but there should be a "paste as new layer" option to simplify it for new users; don't complicate it by turning it into many steps.

      Now these are legitimate gripes. I only hope they get (can and do) fixed once GEGL is complete.

      Some of the posters in here claim that Gimp hurts because it tries to do so much; this sounds like the "one task, one tool" mantra that drove Unixy operating systems for about 30 years. In a CLI that philosophy makes sense, but in a suite one should try to offer a complete solution to improve workflow.

      Those people ought to just use ImageMagick and quit complaining about The GIMP. I think we can safely ignore them.

      Personally I hope Adobe makes their suite available on Linux - it would be interesting to see what happens to gimp and inkscape. Would they continue to gain market share (albeit slowly) or would interest in them die?

      I don't know about The GIMP, but -- at least, according to my girlfriend, who is a 2D computer artist -- Inkscape is actually good. She actually prefers it to Adobe Illustrator. On the other hand, she does not prefer The GIMP to Photoshop.

      (*assume for the purpose of this post that the GIMP counts as "professional level" -- AFAIK that's the goal, at least)

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    16. Re:Fanboyism, user interfaces... by hollywoodb · · Score: 1

      Ooooh... what a bold statement! The GIMP is *NOT* user-focused. Don't tell me.
      Clearly you haven't read their awesome tutorials!
      Here's my favourite: http://www.gimp.org/tutorials/Straight_Line/
      --
      I may have to share this planet with animals, but I'm doing my damn best to eat every last one of them.
    17. Re:Fanboyism, user interfaces... by kimvette · · Score: 1

      First, understand that The GIMP is cross-platform, and that different platforms use different UI models. The platform you're running it on probably isn't the one it was initially designed for.


      kim@kimc2d:~> uname
      Linux
      kim@kimc2d:~>
      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    18. Re:Fanboyism, user interfaces... by xtracto · · Score: 1

      and how, please tell, do these "CUSTOMERS" help the project? they don't contribute money (it's free), and they don't contribute source-code (they're not programmers), so besides the ego-stroking that follows having a larger market-share than $PROPIETARY_COMPANY_X, why would a non-commercial open-source project try to please *them* instead of, y'know, people who do give something back to it?

      Then these Open Source programmers should keep their code and programs to themselves and not let others use it... What these customers are providing is exactly that, FEEDBACK. Of course usually the Open Source programmers seem to be allergic to such a thing. I agree with parent poster, just take a look at VirtualDub vs Jashaska, the last one is a fucking joke.

      Of course I understand that it is impossible to crate a program with the complexity and maturity of Photoshop, this program is backed up by Adobe, a company that can pay thousands in HCI research, patents and who can have a complete army of people /LISTENING/ to their customers needs. While in the GIMP you might only have a bunch of people that give their spare time to code whatever they think is the next cool thing for the GIMP.

      But who is /really/ to blame?, it is not the GIMP programmers, but the GIMP [/Linux/OpenOffice, etc] fanboys who are trying to convince other people that GIMP can be used to replace Photoshop... while that is false.

      --
      Ubuntu is an African word meaning 'I can't configure Debian'
    19. Re:Fanboyism, user interfaces... by Anonymous Coward · · Score: 0

      and how, please tell, do these "CUSTOMERS" help the project? they don't contribute money (it's free), and they don't contribute source-code (they're not programmers), so besides the ego-stroking that follows having a larger market-share than $PROPIETARY_COMPANY_X, why would a non-commercial open-source project try to please *them* instead of, y'know, people who do give something back to it?

      Because these non-contributors are contributing by providing feedback on quality of the work you're producing. You might be familiar with a concept of a QA group? Many corporations have them. Of course since you're doing this for free and quality doesn't matter, why should anybody bother to help you out with the project, or let you get involved with theirs?

      Then there's reputation When and application becomes known as a POS, developers will stay away from it because it hurts they're ability to actually make money. I know that I will certainly not hire a developer who has Gimp on his/her resume, because Gimp is a POS.

  23. Is GIMP still being developed? by FooBarWidget · · Score: 2, Interesting

    Is GIMP still being developed? This is a serious question.

    I've been a big GIMP fan for years. Years ago, I was excited about the 2.0 release of GIMP. It brought many new features and the UI got a serious revamp. But now it has been several years, and it seems that GIMP development has slowed down. They're still releasing newer versions with bug fixes, but no new features. For example: I recently bought a Wacom tablet, and while GIMP has Wacom support, I miss some of the things that Photoshop has, such as support for variable brush width based on tablet pressure. The long-awaited GEGL, which was introduced years ago and will supposedly add CMYK and 16-bit support, is still not ready, and to my knowledge is still pre-alpha. (Not that I need CMYK and 16-bit, but at least that silence all the complainers.)

    A year or two ago I also read an article about someone wanting to sponsor GIMP development. But that effort went nowhere, as his request was eventually ignored.

    What is going on? Is GIMP still being actively developed? Are the GIMP developers still interested in adding new features?

    1. Re:Is GIMP still being developed? by andrewd18 · · Score: 1

      I totally agree... The GIMP reminds me of Enlightenment these days... hurry up and do something big already!

    2. Re:Is GIMP still being developed? by Anonymous Coward · · Score: 0

      It's pretty easy to see if there is active work going on for it:
      1. Go to http://gimp.org/
      2. Note that they've had a couple of development releases in the last couple of months
      3. Click on the NEWS links to find out what's being fixed/worked on.

    3. Re:Is GIMP still being developed? by FooBarWidget · · Score: 1

      I know about that, and I read NEWS from time to time, but look at what has actually been changed. They're mostly bug fixes and relatively minor tweaks, not major features.

    4. Re:Is GIMP still being developed? by Trogre · · Score: 1

      They're probably still bitter that Cinepaint, a fork that they wanted nothing to do with but now seems to be doing so much better than they'd thought.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    5. Re:Is GIMP still being developed? by BigSven · · Score: 3, Informative

      GIMP does support variable brush width based on tablet pressure since version 1.2.

      And yes, it is still being developed and we are very close to finally releasing GIMP 2.4 which will bring lots of new features and usability improvements.

    6. Re:Is GIMP still being developed? by BigSven · · Score: 1
      That's what happens when you are in feature freeze, preparing a new stable release. There's only bug fixing and minor tweaks because otherwise we would never get 2.4 done and we absolutely want to release GIMP 2.4 for two reasons:
      1. to let our users benefit from the new features, usability and performance improvements
      2. to finally start the integration of GEGL into the GIMP core

    7. Re:Is GIMP still being developed? by FooBarWidget · · Score: 1

      "GIMP does support variable brush width based on tablet pressure since version 1.2."
      It does? How does that work? It supports variable brush transparency, but I can't find variable brush width. Or is that ability limited to the ink tool?

      "And yes, it is still being developed and we are very close to finally releasing GIMP 2.4 which will bring lots of new features and usability improvements."
      That's good news. Good luck.

    8. Re:Is GIMP still being developed? by BigSven · · Score: 1

      The paint tools have a set of toggles labeled "Pressure sensitivity". There, next to the check-box "Opacity", is a check-box labeled "Size". If you check that the brush will shrink depending on the pressure you apply.

      I added this feature eight years ago at the Chaos Communication Camp. How could you have missed it all that time?

    9. Re:Is GIMP still being developed? by FooBarWidget · · Score: 1

      Ah, thanks.

      I missed it because the idea never occurred to me. I thought it would have something to do with the Settings dialog, or the specific brush that I selected. The pressure sensitivity option never did anything for me when I'm using a mouse, so after I bought a Wacom the idea never occurred to me to look there.
      Perhaps this will help with your usability study.

      Anyway, I now have one less reason to use Photoshop. :)

    10. Re:Is GIMP still being developed? by FooBarWidget · · Score: 1

      Follow-up to my last comment.

      I do notice a problem in pressure sensitivity compared to Krita and Photoshop. Take a look at this image that I just drew with my tablet. If you look at the red lines (and particularly the areas pointed to by the blue arrows), you'll see that the transition in brush width is not smooth. In my pressure sensitivity options, 'hardness' and 'size' are turned on. Turning on 'opacity' does not seem to help.
      For comparison, this is how a line looks like in Krita, and it looks much smoother.

      This may be a thing that one wants to improve.

    11. Re:Is GIMP still being developed? by BigSven · · Score: 1

      That's due to an optimization that GIMP does here. The brush mask is cached so that it doesn't have to be rescaled all the time. In order to allow such caching the size is adjusted in full pixel steps. That's not a problem for wide strokes but if you go down to very small brushes, it becomes a problem.

      Yes, this could certainly be improved, patches welcome. But please check a recent 2.3 release before you start coding. There have been lots of changes to the brush scaling code so this might even have been addressed already.

    12. Re:Is GIMP still being developed? by FooBarWidget · · Score: 1

      I just tried 2.3.18. Pressure sensitivity appears to be entirely broken, unfortunately. If the pressure is less than x (where x is some value that I don't know) then nothing happens, just as if I'm using a mouse.

    13. Re:Is GIMP still being developed? by Filmwatcher888 · · Score: 1

      Change the name already. That should be bugfix #1.

  24. GIMP usability is not the issue by Michael_gr · · Score: 1, Interesting

    The problems with the gimp are mind numbingly easy for any semi-talented UI designer to spot and fix.
    The problem is the development team: there's not enough of it, and there's no leadership strong enough within them to commit to a roadmap. If they only decided to stop coding for a while, decide what their end goals are (this is not a question users should be answering), plan the next few versions in advance and then actively look for new developers to implement whatever they decide on, things would look different.

    1. Re:GIMP usability is not the issue by thenerdgod · · Score: 1

      The problem is the development team: there's not enough of it, and there's no leadership strong enough within them to commit to a roadmap.

      Exactly. ...having discussed things on the GIMP Usability Forum, it's obvious that the GIMP developers (to misquote Kanye West) don't care about designer people.

      The general attitude is "We're not going to change anything because even though the similarity of constant anecdotal 'complaints' may actually constitute user testing, we refuse to believe it until someone does systematic user testing." Of course, imgimp is the answer to their request, but automated testing does nothing. They're missing the point that assisted user testing is needed, where you give someone a mock up and ask them where they expect to find things, and how they expect to do things. What they've been getting, in droves, is people who are GIVING THEM THIS EXACT INFORMATION, in forums, in blogs, in wikis and slashdot posts. Things like "Why are script-fu and filters two different things?" and "what are Xtns?" not to mention "Why does the palette take up so much space?". Then there's the whole MDI/SDI thing. The horrible fact is that the GIMP is an MDI application. There is a shared set of tools that act on multiple document windows. Gasp. Unfortunately most X window managers have no idea what this means, and the concept of 'tool windows' is meaningless (i.e.: if I have 8 tool windows open, I have 8 task items in my task bar, and sometimes you have to click-to-focus and click-to-invoke on a non-focused window).

      There are some very simple things the GIMP developers could do to fix the application:

      1. Rename the damn thing. I'll say it again: would you suggest the GIMP to your grandmother? My grandmother wouldn't even visit 'excite.com', lest it turn out to be salacious. They should call it SPORK (the GIMP fork)!
      2. use the existing preferences infrastructure to:
        • make the palette at least 2-column so it leaves more space for the document window
        • set the 'tiny' UI style to the default
        • make the 'File Xtns Help' menu a popup menu, and rename Xtns to something sane. Or; make them buttons that open popup menus
        • Reorganize the menus themselves to group common functionality. I don't care if it's familiar to photoshop users. I care if the menus make sense. move "Tools Dialogs Filters Script Fu" into a hierarchy that matches their function, and name them per their function.
      3. Also, the entire "select" system is hard to grasp for people used to other programs. Not just photoshop. PhotoDraw, PhotoPaint, MacPaint... whatever.
      4. Add layer grouping. Do away with new layer dialogs.
      5. Group tools on the tool palette
      6. in general look into shrinking the space taken up by the various palettes. On some screens fully half the layer palette is taken up with labels and buttons. God help me, but part of the reason Adobe has its own widgets is because the windows standard ones take up too much space. Except you have no excuse because GTK widgets were DESIGNED FOR THE GIMP AAAA!
      7. For the love of God, do some paper testing.

        Get real designers, and I don't care if they're familiar with Photoshop... hell, Adobe just redesigned the damn thing on us so it's not like we're shocked by the New. Get them and sit them down with paper mockups and ask them how to do common design tasks, common painting tasks, common editing tasks.

        Admit that a lot of us have done this already ourselves. Sure a lot of it seems to you to be "oh that's just because they know photoshop", but damnit man, it's not photoshop we know, it's everything. Photoshop, MacPaint, ColorIt! (yeah, I said it), PhotoDraw, whatever. There is a common language to these tools and you keep trying to miss it just to be different.

      8. Look again at this... especially the part about "All that touch

    2. Re:GIMP usability is not the issue by CronoCloud · · Score: 1

      Admit that the program has problems. You keep insisting on proof when proof is all around you. There are designers and SMEs who want to help, but you keep getting defensive and saying that it's not a problem with the software, it's our preconceptions. ...I hate to break it to you, but our preconceptions drive software interfaces. Why do you think you have little pictures of file folders on your desktop. Why does it have a trash can? If you don't want to design to our preconceptions, why not just make the picture of a paint bucket look like a chicken shooting gore on a canvas? Could it be that we have a preconception of how tools work, and a good developer/designer creat


      I had the exact same issue with the Pidgin developers, they wanted "objective" data on why some of their recent UI decisions were not so good. Simply saying, "Look at all the complaints from the users." wasn't good enough for them. The had the "What do they users know, and they're not paying us anyway." attitude.

  25. Where is it sending my data? by Anonymous Coward · · Score: 0

    I have not read the article, I clicked on the comments expecting to read things related to privacy concerns.

    1. Re:Where is it sending my data? by Soulfry · · Score: 1

      Yeah, I'm kind of surprised no one is talking about privacy, either.

      But then again, we are very upfront about what data we collect and the ways your privacy could be affected. And... you can always inspect the source code if you have any privacy concerns.

      Michael Terry

  26. I know it's almost a troll point but.... by Anonymous Coward · · Score: 0

    I've tried Gimp over the years and it's okay as a freebie but if you give me the option of Photoshop or Gimp I default to Photoshop every time. I don't use 90% of what Photoshop can do so it isn't lacking high functions it's the UI. Photoshop simply works where as Gimp is a pain to use. I recommend it to people all the time if they can't aford Photoshop but I see little reason to use it since I have Photoshop. I know it's not what they want to hear but if you want to fix it mimic what works, Photoshop. At the very least most users are used to the Photoshop conventions. Photoshop has a simple straight forward layout. My biggest complaints for painting is a lack of painting tools so I do use other programs at times, even Dogwaffle does some cool stuff and even the commercial version is cheap. The freebie version is even fun to use. There are other painters but for photo work Photoshop is the standard for a reason and they just need to deal with that fact and accept more of Photoshop's conventions. Just because it's free and open source doesn't make it better. Blender is a powerful program but it's bizarre nonstandard interface keeps me from using it. I've tried three times to learn it and always end up back with Maya and Lightwave. I love the idea of using an open source animator but the UI is a major headache to learn. After days of trying even with tutorials I could do more my first hours with either Maya or Lightwave. That's the sign of a bad UI. The two easiest I ever found? Modo for modelling and Anime Studio Pro for 2D animation. Either software you can get a good working knowledge of in a day or two. For gaming the Unity Game engine is staggering and easy to learn. You simply can't beat a well designed UI that is well documented.

  27. Self-selected group? Self-denial? by Dekortage · · Score: 2, Interesting

    From the presentation slides, it seems like 200 people have installed it (netting "over 100,000 commands" in the log files). Obviously more will do so in response to the Slashdot article (and appropriate web pollination)... but aren't these self-selected geeks already? How are you going to get non-geeks to install this instead of the regular GIMP (assuming you convinc them to take a look at it)?

    Furthermore, how does this help determine what GIMP isn't doing properly? I mean, if you have various tools at your disposal, and GIMP sucks at doing X, then you might do half your work in GIMP and the other half in another app. So all the usability problems around X won't show up in the logs -- almost a kind of self-denial.

    I use Photoshop on a nearly daily basis. Last time I tried GIMP it was not ready for professional print design, to be sure, and only probably good enough for desktop publishing or Web graphics. How about Pantone or CMYK support? Non-destructive layer effects? Variable-sized brushes? Actually useful text formatting?

    --
    $nice = $webHosting + $domainNames + $sslCerts
  28. Double standard. by Anonymous Coward · · Score: 0

    "Now Prof. Michael Terry and a group of researchers at the University of Waterloo have created ingimp [CC] [MD] [GC], a modified version of the GIMP that collects real-time usability data in order to help the GIMP developers find and fix its usability problems. "

    The interesting thing is that when Microsoft collects data to make it's software better, it's a bad thing. When OSS does it, then it's a good thing.

    1. Re:Double standard. by Soulfry · · Score: 1

      With the OSS version, you know exactly what data is being collected and where it is being sent. And, we make it all available for anyone to analyze, so you know who can potentially see it and make use of it. These are typically all unknowns with closed source software.

      Michael Terry

    2. Re:Double standard. by PitaBred · · Score: 1

      You forgot the biggest part: you can always opt-out of it. You don't have to install ingimp. There's no such thing with closed source software aside from firewalling off the machine entirely. But I believe that the GPP of this is a troll ;)

    3. Re:Double standard. by Anonymous Coward · · Score: 0

      "But I believe that the GPP of this is a troll ;)"

      So's this guy. Better catch him before someone sees his post.

  29. Or IBM optimizing the most-heavily-used opcode. by Ungrounded+Lightning · · Score: 4, Interesting

    Then there was the time IBM instrumented a mainframe to determine what instructions were heavily used so they could focus their optimize-the-microcode effort on them.

    They found one particular instruction that accounted for some exceedingly large fraction of the execution time. So they went to work on the microcode and doubled its speed. Then they deployed the new microcode and measured the application performance, expecting to see a big improvement.

    It didn't change a bit.

    After a little more research they discovered they'd optimized the idle task's wait loop.

    = = = =

    Collecting data can be useful. But making good decisions based on it requires wisdom and insight.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:Or IBM optimizing the most-heavily-used opcode. by halivar · · Score: 1

      This story sounds specious. Are you sure it isn't an urban legend?

    2. Re:Or IBM optimizing the most-heavily-used opcode. by Chandon+Seldon · · Score: 1

      It makes a good fable in any case, clearly communicating the intended moral of the story.

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
  30. I renamed it already... by jolyonr · · Score: 1

    When I talk to "normal" people and mention GIMP, I'm always careful to call it the "GNU IMP graphics software". It is, otherwise, one of the most ridiculous names in modern software.
     
    Jolyon

    --


    Please read my Canon EOS tech blog at http://www.everyothershot.com
    1. Re:I renamed it already... by rhizome · · Score: 1

      When I talk to "normal" people and mention GIMP, I'm always careful to call it the "GNU IMP graphics software". It is, otherwise, one of the most ridiculous names in modern software.

      yes, but do you pronounce it "new," or "ganoo?"

      --
      When I was a kid, we only had one Darth.
  31. Keep it simple. by MaWeiTao · · Score: 2, Interesting

    The biggest problem I have with GIMP is it's interface. It's clear the application was designed by programmers and not designers. I feel like they've tried to cram too much onto the screen and they suffer from a similar problem I was with Microsoft applications. They try to offer too many ways to do things and get too technical with details. I don't need 10 different sliders for customizing a brush. If I want a custom brush I should be able to just create the graphic as I would anything else then just drag it into a custom brush box and be done with it.

    Photoshop is getting progressively more bloated but I still find it more fluid than anything else. I'm not constantly hindered by the application.

    The solution isn't to do more coding. The data they gather may result in solutions that only complicate the issue. What they should do is sit down with a small team of designers. Include people with experience in photo-editing, website layouts and interface design. Ideally, find people that have little to no experience with GIMP. Work with this team to develop an interface. And most importantly, keep things simple.

    Inevitably, most applications end up being overly complex because of some overwhelming desire to cram in every last feature the developer can dream up. There also seems to be little planning. Build a set of guidelines and adhere to them. And one last thing, be sure that all essential function can be activated via the keyboard. When I'm doing time-consuming production I don't want to hunt around for small icons, or be constantly switching between the mouse and keyboard.

    1. Re:Keep it simple. by Richard_J_N · · Score: 1

      Could we at least have an option to make gimp run in a single full-screen window? I agree that, if you want to do lots of complex things in gimp, it's quite useful to have multiple windows. But for simple work, why can't GIMP do the same as every single other program, and get all the toolbars etc into the same place! Most applications get this right; some eg thunderbird even let you choose between layouts to suit yourself. (The other big offenders are kooka and digikam).

      Incidentally, xaralx would be a fantastic alternative, but it seems to be dying - there's been no activity this year.

    2. Re:Keep it simple. by Aladrin · · Score: 1

      "Ideally, find people that have little to no experience with GIMP."

      I disagree. This is -not- what you want. If you do that, you'll end up with all the ways The GIMP isn't Photoshop. We already -know- that.

      What we want is all the ways The GIMP could be improved for ease of use and efficiency. Some of that will be to copy some Photoshop features, sure, but if done right, it could surpass Photoshop, instead of merely tagging along behind it, always 3 steps shy of being the best.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
  32. gimp vs. photoshop by brunascle · · Score: 1

    you know what's odd? everyone always hears "gimp is hard to use" blah blah blah, but the other day i tried to use photoshop for the first time... and i couldnt figure it out. for one: how do i zoom in by more than 1x at a time? 2. where the hell is the bucket fill button? 3: how in god's name do i set the transparency of a color?

    i couldnt figure it out. and i had to go back to the gimp. that's my story. hope you enjoyed it.

    1. Re:gimp vs. photoshop by vimh42 · · Score: 1

      I hate to say it, but your post is as bad as the Photoshop users who first try with Gimp can't get anything done. They have some differences in interface and functionality. One would expect a little bit of a learning curve however both have much in common. If you are reasonably fluent in one, then quite honestly, you should be able to use the other with minimal fuss.

    2. Re:gimp vs. photoshop by frogstar_robot · · Score: 1

      Thing is, we hear day in and day out that not being UI identical to PhotoShop down to 6 submenus deep means that Gimp is utter crap. All these Photoshop experts never remember that they were once newbs and spent a few months or years deeply learning Photoshop. There are legitimate criticisms of Gimp, it has an 8-bit per channel colorspace limitation which very much limits the applications it is appropriate for and there isn't much in the way to color accurately use it's output in professional publishing even if it didn't have the 8-bit limitation.

      So actually, the more whingy of the PhotoShop users could use some reminding that from other eyes their tool of choice isn't necessary UI nirvana.

    3. Re:gimp vs. photoshop by Anonymous Coward · · Score: 0

      > All these Photoshop experts never remember that they were once newbs and spent a few months or years deeply learning Photoshop

      The main difference that comes to mind for me is that I started off using MS Paint, the graphics tools in ancient PC DTP packages like First Publisher, Corel's PhotoPaint, Paintshop Pro and so on and so on... from all these other packages, it took me a couple of hours to get used to Photoshop. And yeah, I didn't think the interface was too hot, really, but I got used to it. A year or so /previously/ to first seeing Photoshop, I'd spent a similar amount of time trying to get used to the GIMP and came away feeling almost violent. The problem isn't that the GIMP differs from Photoshop, it's that the GIMP differs from /pretty much every graphics app on the face of the planet/

      I wanted to misquote Dijkstra's infamous pronouncements on COBOL and BASIC for The GIMP and Photoshop respectively, but it's not really that fair to Photoshop. But it's certainly the case that having programmed in real languages, it's quite possible to learn BASIC in a couple of hours, but trying to code in COBOL makes you want to kill people.

  33. That's what she said.... by StressGuy · · Score: 1

    .....lame.....so very lame......

    --
    A goal is a dream with a deadline
  34. Almost. by Benanov · · Score: 1

    4. GIMP has really bad startup time, and performance, compared to commercial graphics editors (such as Photoshop)

    Only under Win32, and mostly in the font loading spectrum. It's a hell of a lot faster in a native GNOME.

    1. Re:Almost. by BigSven · · Score: 1

      Startup on Win32 is pretty fast, definitely a lot faster than Photoshop. If it isn't, then your font cache is broken as explained in the FAQ.

      Yes, it would be good to finally figure out why this happens at all and there are people working on this (see bug 154968).

  35. Re:Self-selected group? Self-denial? by Soulfry · · Score: 1

    We're working to be a part of the official Debian distribution, we have a single Windows installer, and we're readying a Mac port -- we want to make it as easy as possible to download and use this distribution so it's not just "self-selecting geeks" :)

    But self-selection will always be a problem. If you have ideas on how to get around self-selection bias in human subjects research -- where people must volunteer to participate -- please let us know! :)

    And just to clarify, we're not trying to find usability problems as much as we are trying to quantify behavior/activity/system setups. Other efforts are helping to identify critical usability issues (see http://gui.gimp.org/ ). Our data provide an additional perspective on GIMP usage in the wild -- data that exist nowhere else. We're also quite unique among both commercial and open source projects: No other software collects this type of usage data, makes the data collection and dissemination process as transparent as we do (especially since it is open source), and makes all the collected data available for anyone to analyze. We're building a very valuable repository not only for understanding GIMP's usage in the wild, but also for research involving data mining, intelligent user interfaces, and so on.

    Michael Terry

  36. will it detect crashing? by jordan314 · · Score: 0

    My usage would go something like this: Open up gimp, open a file, gimp crashes. The windows version I'm using (gimp 2) has some serious stability issues.

  37. Expert in usability by Chris+Shannon · · Score: 2, Interesting

    I watched the video, and the only thing that stuck in my mind, is that I think you're not qualified to study usability if you have to Alt-Tab through a bunch of firefox instances because you haven't discovered tabs yet.

    --
    "Follow me" the wise man said, but he walked behind.
    1. Re:Expert in usability by Anonymous Coward · · Score: 0

      I love tabs in Firefox. But sometimes I'll want all tabs in the same browser window, and sometimes I want screens in different windows. I'll often use both techniques at once: to organize or separate categories of stuff that I'm looking at or working on (for example: personal vs. work-related, etc.); to compare/cut'n'paste what I have open in two different windows; even because I may have other program window open and my hand "knows" Alt-Tab can rotate through them as I am working.

  38. very difficult by Anonymous Coward · · Score: 0

    We almost switched to the gimp at my old middle school, but no one (eg, the smarter of the multimedia students, the multimedia teacher) could figure it out to satisfaction.

  39. ugh... by mpapet · · Score: 1

    If it's free and it works, why isn't EVERYBODY using it?

    There are a number of logical failures with this line of reasoning. Free has little to do with the reason "everybody" uses something. Most times, it is the product that has enough money to shout the loudest.

    graphical applications are meant to be used..
    Ranting about the GIMP really doesn't get your point across. For some of us the GIMP is great. For you, it sounds like you want to use Adobe products. Go for it.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  40. Here's a Hint... by DiscoNick · · Score: 1

    Clone Photoshop. It may not be the best interface, but I can assure you most people will be familiar with it.

    1. Re:Here's a Hint... by vladsinger · · Score: 1

      And before anybody suggests gimpshop, trust me, it's not even close. With all due respect to its developer, of course.

  41. Isn't usability just... by fireman+sam · · Score: 1

    ... a measure of what you are used to using? :set sarcasm

    I've been using the Gimp since around July 1996. As it was my first experience at using graphics software, I found that once shortcuts and mouse clicks were remembered, using it was no problem. The problem occurred when I was forced to use Photoshop for a job I had. I found the layout of the interface clunky and the whole single window think was crap to work with. I just wish the Photoshop developers would get their act together and set the layou more like the Gimp, and then maybe Photoshop could be the next Gimp killer. :set nosarcasm

    --
    it is only after a long journey that you know the strength of the horse.
  42. User interfaces... by fyngyrz · · Score: 2, Insightful
    See, professionals don't want just "a better pile of poo" to do their imaging work. They (and I, too) want something that IS EASY TO HANDLE. Because in graphical applications, form is function. And this is something that many programmers (at least many of those that I've discussed with) simply fail to understand.

    Ok, some questions, then. What if an interface offered approaches more consistent than Photoshop's or GIMP's? For instance, in the main toolbox, both Photoshop and GIMP mix area selection tools (eg, rect, ellipse) with tools that actually modify the image using areas (eg, smudge, fill.) Because of this, the only way to know what a tool in the tool box will do is to become familiar with it; the location (in the toolbox) doesn't define the type of functionality. What if the area selection tools were in one toolbox, and tools that modified the image were able to be placed in another - perhaps just the ones you think you'll need today? In terms of usability, this type of approach associates physical location with function; this *should*, theoretically, enhance usability.

    The same thing applies to layers. Photoshop's interface treats layers like they were not images, rather, as if they were only components of images. But essentially, they are images, as demonstrated by the ability to select one and edit it as if it was the image. What if a four-layer image allowed you to see, and edit, all four layers at once, just as if they were normal images, while changes to the sum of all the layers, let's call that the "master" image, are visible in yet another window? Wouldn't that be more consistent than treating a layer as if it were something other than an image? It provides direct, and simultaneous, access to everything at once (many layers begin to bring window management into the equation, but those skills are even more basic than anything inside an image editor.)

    Before you answer, I would like to point out to you how many complaints that couch themselves as usability complaints refer to an application not working "like" Photoshop, and how often the phrase "industry standard" is brought up; it seems to me that when complaints of this type are voiced, they refer to learning the person has already done, and they want *compliance*, because they already have (a set of) muscle memory that they work with. They actually don't want better or easier, because better and easier is different, and different will impede their progress while they learn (if they are even willing to learn!)

    I make decisions about these precise things as part of my job; I'd be very interested in specific opinions from anyone on these issues.

    --
    I've fallen off your lawn, and I can't get up.
    1. Re:User interfaces... by Telvin_3d · · Score: 1

      Here is my take on your two propositions.

      First, the idea of separate menu sections or menus for different families of tools is only one way to look at it. While first thought says that it should be more efficient, in reality I don't think it would pan out. There are multiple ways to define a 'family' of tools some of which are going to be more efficient than others. For example, you could group tools that are typically used for photo manipulation or colour correction together, regardless of what they actually do, and it would be arguably more efficient than grouping by type. This leads into your comment about how the current layout relies to some extent on the user already knowing what all the tools do without any aid from the interface. To some extent, this isn't a valid concern for either of these programs given their stated goals. As software that is designed for professional use, efficiency and robustness are the only real measures. A good interface only matters as far as it speeds up or streamlines the workflow. How it effects the learning curve is irrelevant. If either of these packages were targeting themselves at the general consumer market it would be differnt, but they are not.

      The other question about layers all depends on point of view. They are only 'images' if you look at them as images. most programs that sue layers of one sort or another (Adobe products, video editing, 3D) treat layers as a method of organization first, something to hang modifiers on second and an actual element of the final product a distant third. In Photoshop's case it treats layers as components of images because the original (and still major) use of them was to organize and layer components of a single image. The ability to apply the same edits multiple layers at once would be a neat trick, but at the same time would never be used. Off the top of my head I cannot image any image workflow where multiple layers with portions of the same edits would not signal either massive wasted effort or a severe lack of understanding of most of the intermediate or advanced techniques of any image editor I have ever used.

      I would be curious to hear your take on any of these points.

    2. Re:User interfaces... by fyngyrz · · Score: 1

      First, the idea of separate menu sections or menus for different families of tools is only one way to look at it. While first thought says that it should be more efficient, in reality I don't think it would pan out.

      Actually, it works quite well.

      My area toolbox contains 14 area selection tools: freehand, polygon, i-shapes (preformed, like stars; bears; triangles; continent outlines, etc), rect, rounded rect, ellipse, polyarc, bezier, bspline, numeric rect, wand, text, entire image, redo and 13 modifiers and controls: Area re-edit (for pre-select mode), color key, splatter, hold square, hold to image aspect, hold to aspect of clipping being placed, invert (complement), intersection (select only where current selection overlays previous selection), union (select where either of previous and current selection lie), exclude (select anywhere previous and current selection are not), outline only (rather than area - this implements line drawing and so forth), open selections (for instance, freehand doesn't auto-close if this is on), and anti-alias. Right clicking brings up various things like wand methods [RGB, HSL, Tolerance, Resample, Soft, 8-way] Keying modes [RGB, Hue, Color Space, Steepness, Height, Alpha] rect roundness, selection of preset shapes, fonts, splatter parameters [randomness, sizing, edge behavior, aspect], custom aspect controls for the (nominal) 1:1 setting, and finally the feathering dialog. All area selections can be set for [a] select and do nothing (this is how Photoshop works) or [b] select and trigger operation ("immediate" mode - this is the mode I usually prefer, I can work faster.)

      This is just the area toolbox functionality. Most everything related to areas is accessible from this one place, although there are a few controls up in the menu system: corner/center selection modes and a special blending toolkit that uses a computed centroid of the area selection and distance from the edge(s) to create selection softness using three sliders that give you the base and apex width of a graph, as well as its height from 0 to 100%.

      Adding to all this is right-button functionality over the image. Pressing the right mouse button while sizing a selection releases the initial anchor and lets you re-position the selection live; releasing it lets you go back to sizing. This is particularly handy in my preferred editing mode, "immediate." Certain selection modes - like text - offer a lot more, like the ability to skew, rotate, and size the text selection prior to final placement using the right mouse button.

      My effects toolbox contains whatever I've found to be useful for the task at hand. For instance, when I'm editing images (often, it's a hobby) it contains fill, sample (eyedropper), balance, brightness, contrast, gamma, colorize, sharpen, Gaussian blur, horizontal feature removal, vertical feature removal, radial feature removal, clip, scale by percent, scale by pixel, monochrome, re-texture, alpha, flip, rotate(90 increments), free rotate, and brush, as well as the scripting and plugins tools (these can incorporate a wealth of functionality, of course, but I usually have a blue/green-screen de-fringing plugin and just pick (or write) scripts as I need them.) Right clicking the icon gets you the operation dialog, if it isn't already open. You can drag tools in and out of the box, re-arrange them in any order, change the X:Y arrangement of the box, save it as a named tool caddy, or turn it off and just use the usual "go find it" methods all the time. A few things - like levels, clone, scale to current window size, assign image to role [brush, secondary], print, copy to clipboard, insert to filmstrip and "layerize" are in each image's context menu, and so don't need to be in the op caddy.

      During a photo editing session, I can get at anything either from the operations tool bar or from the operations menu (both offer identical cascading sets of organized operations, just two different ways to get at them.

      --
      I've fallen off your lawn, and I can't get up.
  43. Re:Self-selected group? Self-denial? by cecille · · Score: 1

    The print thing isn't even just a problem for professional applications. A while ago I was doing some casual poster design stuff for a group at the university. They didn't have the budget for a real plotter, so they normally print on colour 11x17, then cut the margins and put the poster together as essentially a mosaic.

    The new tech guy in the office decided that the gimp was the way to go no matter what, and promptly removed photoshop from the design computer for unknown reasons. I have to admit, I love my photoshop, so this was a bit of a setback. None the less, I've used the gimp a few times before, and I don't hate the interface. It seemed to go well enough and it wasn't a real printer anyway, so RGB was fine.

    However, once we got to printing time, the real disaster struck. I couldn't find a convenient way to slice the image up in the gimp. I thought maybe they had thought of this and tried to see if it would print nicely for me, but I only got one corner. At one point I did have the top row printed, but it didn't account for print margins and I ended up with white gaps. Now I could have done it by hand, but it seems that for some reason the gimp is lacking a print preview. That seems odd to me, but for the life of me I couldn't find the damn thing. Anyway, I ended up having to go get my laptop to print. That's basically the last time I'm likely ever going to use the gimp.

    --
    ...no two people are not on fire.
  44. Re:GIMP will always be a gimp by Anonymous Coward · · Score: 0, Informative

    Here ya go:

    GimpShop

  45. Missing The Point Entirely by mpapet · · Score: 1

    Maybe a bigger problem will be that you can't instrument what GIMP doesn't do: CMYK, Color Management, look/work just like the industry standard..

    1. When did the GIMP project's first goal become world domination?
    2. Yes, GIMP does support color managment. No, not to your satisfaction. http://www.khk.net/color/color_manager.html
    3. Yes, GIMP does have some CMYK features. No, not to your satisfaction

    GIMP is a great tool for many. Judging by your hysterical comments, it is not a good tool for you.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
    1. Re:Missing The Point Entirely by jddj · · Score: 1

      I think perhaps you're missing the point(s)

      1. I think the GIMP is a really nice little tool, and useful for what it is. I'm really not trying to slag it, though you assume that's what I'm about. Not so.
      2. I think that nearly anyone who has used GIMP for more than a few minutes thinks the UI could use some fixing. The existance of GIMPShop and this instrumentation work both show I'm not alone in feeling it could use a fresh steamy plate of UI Helper.
      3. Here's the real point of my post: the instrumentation can deliver data on how long a task might take, or how long a user wandered around with the mouse trying to accomplish something. But it cannot deliver data on features that the program does not have - and that these missing features are some of the key weaknesses. They'll slide under the radar of the UI work because it's not possible to instrument something that doesn't exist. That's all I'm saying.

      Finally, my point about another "not Photoshop" app. Linux could use a few more killer apps. Apache certainly is one. MySQL another. Photoshop was for a long time THE killer app on Mac OS. It was a reason to buy a Mac - all the reason you need.

      Me, I've got Photoshop and don't need GIMP. But in thinking about improving GIMP, I think that if it could be made Photoshop's equal (at least in factory features - getting the 3rd party stuff is pretty unlikely), you'd be a bit closer to adoption of Linux on the desktop - certainly closer for photographers and graphic professionals. This ignores the wide variety of suppporting apps that pros rely upon on their Macs and Windows machines, but having it a highly-usable and productive tool with Photoshop feature parity both helps further desktop adoption AND makes it easier to use for geeks that just like to putter around in it a bit.

      I hardly think that's a hysterical view - the label seems to say more about your biases than it does about mine, as you appear to have misinterpreted them

      So they want to make GIMP easier to use - is that a bad thing? Are you really coming out for "harder to use"?

    2. Re:Missing The Point Entirely by Anonymous Coward · · Score: 0

      I think that nearly anyone who has used GIMP for more than a few minutes thinks the UI could use some fixing. The existance of GIMPShop and this instrumentation work both show I'm not alone in feeling it could use a fresh steamy plate of UI Helper.

      No, the existance of GIMPShop show that the Gimp does not have the horrible UI of Photoshop (which btw PS shared with the Windows Program Manager. Even Microsoft saw how bad this UI was and killed it with Windows 95).

      I very seldomly see other arguments about the Gimp UI than "oh no, it doesn't behave like Photoshop on Windows". Heck, even Photoshop on Mac doesn't behave like Photoshop on windows.

    3. Re:Missing The Point Entirely by mpapet · · Score: 1

      I think that if it could be made Photoshop's equal (at least in factory features

      Making a photoshop equal is a fools errand.
      1. That kind of me-too thinking won't help anyone and positions GIMP as the perpetual Yugo of the American auto market.

      2. You wouldn't switch with Gimpshop. How about if GIMP implemented all of Adobe's half-baked gui? No, you wouldn't. You could do quite a bit of professional work in gimp, but you won't because you don't want to.

      3. Posting comments like "if only GIMP was more like photoshop" and "if only the name were different" is disingenuous at best and very annoying to people like me who move easily between the two applications. GIMP is a good tool for the work it can handle. Please learn to distinguish between your strong personal bias and objective capabilities of the applications in question.

      --
      http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  46. Why bother by Anonymous Coward · · Score: 0

    I use MS Paint and it works just fine thank you very much.

  47. new tag by Anonymous Coward · · Score: 0

    aboutfuckingtime

  48. They need a tool for that? by KDR_11k · · Score: 1

    I can tell them the first flaw right away: The tool windows and such get hidden behind the current image window when the focus changes. If there's an option to prevent that I haven't found it (which would be another usability issue).

    Another major annoyance is that brushes can't be scaled. In Photoshop, if you need a brush size that's not in the presets you just drag the size slider, in GIMP you're fucked.

    Well, at least those were present in the last version I used.

    --
    Justice is the sheep getting arrested while an impartial judge declares the vote void.
    1. Re:They need a tool for that? by chammy · · Score: 1

      criticism 1: I can right click my window in KDE and set it to "Always on Top". Problem fixed. criticism 2: You can create a custom brush with a bigger size. I'll admit it's not as nice as a slider, but it works enough that you wont be "f*cked".

    2. Re:They need a tool for that? by frogstar_robot · · Score: 1

      The version of Gimp I'm using right now has a slider for brush size. It is the current development prerelease and I don't know how long it has had the feature but the feature seems a bit on the obvious side and has likely been present for at least the 2.x series of the app.

    3. Re:They need a tool for that? by KDR_11k · · Score: 1

      Not everyone has a window manager that can set always on top and even then it's not great because the windows will be over other programs as well so when I switch to Blender I still have the tool windows visible.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
    4. Re:They need a tool for that? by spitzak · · Score: 1

      This is due to that goddamm "click to top" behavior that was copied from Windows. This basically means that when you click in a window, it raises before telling the program.

      If you read old release notes for X11 you will see they dropped this behavior because it was obviously bad.

      Unfortunatly it reappeared in about 1995 when window managers started copying Windows in order to be "more user friendly" which is code for "act as much like Windows as possible".

      In case you cannot understand why this behavior is bad, here is a hint: A program can raise ITSELF in response to a click and thus achieve exactly the same user interface without this stupid behavior. There is NO reason for the system to do this at all. It is not a question of whether it is good behavior from the user's point of view. It is simply that it is TRIVIAL for this decision to be left to the programs.

      Click-to-top has completely ruined multiple-window apis (including Gimp) and caused endless frustration by requiring tiled or "mdi" or other abonimations or require displays to be crammed into increasing small areas to avoid overlap.

      Hey, and "child windows" or "transient for" or layers or "keep on top" or all that other crap is NOT a solution. They are all bandaid attempts to patch it, by making a complex system of rules for disabling the "click to top", when in fact they could disable it ALL the time and everything would be trivial and easy, and Linux would have programs with GUI's that were far better than anything on Windows due to the ability to make overlapping windows useful.

  49. Abraham Wald by The+Real+Nem · · Score: 1

    A favorite story for stat teachers, I believe this is what you're thinking about.

  50. MDI vs windows by ToyKeeper · · Score: 1

    First, I must say that Photoshop does have some serious advantages over GIMP, such as its extra color models, color depth, and layer grouping.

    However, Photoshop's MDI system is not one of those advantages. The MDI concept (pseudo-windows inside a single main window) seems to be a way to work around the horrible window management in MS Windows. But on a unix system, MDI like that actually prevents a better window manager from doing its job.

    Sure, the MDI might add magnetic window edges, tiled window layouts, and grouping multiple windows into one frame with tabs. But my regular window manager does it better, along with a whole bunch of other features the MDI system will never have. The MDI concept cripples the application by making it incompatible. For example, I can place an xterm and a web browser into a single tab group, but I can't add a MDI-enhanced color picker window to the same group because it's not a real window. Also, I can't drag a MDI widget onto a different desktop or a different screen, to get it out of the way. And if I have anything custom, like tweaks to work around disabilities, it won't work at all with a MDI system.

    MDI makes the learning curve steeper too. It introduces a completely different set of triggers to invoke actions similar to what the regular window manager provides. This means users must remember two sets of commands, instead of just one.

    It's fine with me if GIMP decides to implement its own miniature, specialized window manager... so long as there's an option to turn it off. But I'd much rather the effort was spent on editing features, like nondestructive filters and 16-bit color.

  51. Mod Parent Insightful or Informative by mpapet · · Score: 1

    Pick one or the other.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  52. Novel Idea by ShawnCplus · · Score: 1

    Two simple words: Parent Window. Sure the toolboxes have the ability to dock to the main toolbox but if you want to see all of your image my maximizing it you have to switch between windows to get at your toolbox which becomes extremely tedious, even with shortcuts.

    --
    Excuse me while I gather the virgin sacrifice and assemble the pentagram required to solve your problem
  53. Drawing? by Anonymous Coward · · Score: 0

    People rarely draw completely new content in applications like The Gimp. Well, people that know what they are doing at least.

    Most artists will choose something like Inkscape or Illustrator over The Gimp or Photoshop when it comes to drawing things.

    Manipulating preexisting raster graphics is really what The Gimp and Photoshop are good at, not creating new content. Most of the time drawing new content in raster form is an unwise idea.

  54. remember mozilla? by FranTaylor · · Score: 1

    Remember before Mozilla was done, everyone used to complain about how crappy Netscape was, and how it really needed lots of work.

    Then Mozilla, Galeon, Firefox, etc. came out, and everyone dropped Netscape like a hot stone.

    Any work put into making Netscape better was just wasted.

    GEGL is not done yet. Perhaps history will repeat itself?

  55. disagree with #1 by ToyKeeper · · Score: 2, Insightful

    I mostly agree, but I find item #1 to be misguided: " put the entire layout in a single window with integrated panel layout"

    If you want better window management, use a better window manager. Putting the window management features into GIMP would actually cripple the program for many of us. Photoshop's MDI is a great way to work around the limitations of the window manager in MS Windows. But it's still a kludge. A better window manager is a far better solution, and there are plenty of good solutions already available.

    More details are in another comment:
    http://developers.slashdot.org/comments.pl?sid=248 153&pid=19817169#19818683

    1. Re:disagree with #1 by suv4x4 · · Score: 1

      If you want better window management, use a better window manager. Putting the window management features into GIMP would actually cripple the program for many of us. Photoshop's MDI is a great way to work around the limitations of the window manager in MS Windows. But it's still a kludge. A better window manager is a far better solution, and there are plenty of good solutions already available.

      I'm not the one who's craving to use GIMP never mind the price. It's the GIMP community trying to push GIMP forward as a replacement of Photoshop onto designers.

      A good app conforms to the platforms it targets. The rest is just excuses. What am I supposed to do, switch to Linux to make GIMP a little better? Yea, sure.

    2. Re:disagree with #1 by Chandon+Seldon · · Score: 1

      A good app conforms to the platforms it targets.

      The "GNU" part of the program's name isn't there for no reason, it's there because the GIMP was developed to run on the GNU System. That means that the primary platform it's targeting today is GNU/Linux with the Gnome desktop.

      What am I supposed to do, switch to Linux to make GIMP a little better? Yea, sure.

      If your primary goal is to run GIMP on your computer, that's exactly what you should do. Unless you've found some purpose for an OS other than running the apps you use...

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    3. Re:disagree with #1 by Anonymous Coward · · Score: 0

      Relying on changing the OS--switch to Linux, or adding hardware--extra monitor are both fallacies. They're symptomatic of bad fundamental design and steadfast refusal to admit it.

  56. the way i see it by kaizokuace · · Score: 1

    GIMP developers just need some healthy FOSS competition. Competing with the likes of photoshop is too much right now. Another graphics package needs to be started. The competition would get these dev's in gear. I believe the only kind of competition that exists in FOSS community is withing itself, not from closed source packages. I just wish I was a mad hacker cuz then ofcourse I wouldnt have to be saying this and instead doing it! But I am just a 3d artist... :\ \

    --
    Balderdash!
    1. Re:the way i see it by frogstar_robot · · Score: 1

      They have it in Krita. Due to the years it has been around, Gimp has more bells and whistles but Krita has the advantage of being designed with 32bit colorspaces from the ground up. Now Gimp is supposed to be refactored around a library called GEGL that will address that and some other issues. This has been "coming soon" for a number of years now. I bet Krita reaches feature parity with Gimp before Gimp's colorspace limitations are fixed.

      Come KDE4, it will be easily possible to run Krita in OS X and Windows. That increase in userbase usually seems to draw more developer attention.

    2. Re:the way i see it by kaizokuace · · Score: 1

      yes unfortunately if an FOSS software gets ported to windows and osx it will become more popular. I am not sure whether or not something like krita will work more or less efficiently in osx or windows(probably not windows) but I would someday love to convert to linux completely and to do that I need software that is better and more usable than the windows counterparts. A photoshop replacement is the first step for most artists, followed by a nice 3d package (blender just dont cut it) But thanx for giving the heads up on krita I didnt know about it. What is going into KDE4 that will make it easy to port to osx or windows?

      --
      Balderdash!
    3. Re:the way i see it by frogstar_robot · · Score: 1

      Most who use and create FOSS won't promise you better than the windows stuff you're using now. They'll start and improve their projects and occasionally rival commercial products. Sometimes it so happens the FOSS world will create something you like, use and enjoy!

      One of the goals for KDE4 is to remove inherent dependencies on X11 and other UNIXisms and make the primary dependencies of KDE apps QT, kdelibs, and some other non-X11 libs. Furthermore, QT4 will be available as a GPLed library on unix-type, Windows, and OS X platforms. To make a long story short, the Windows and OS X versions of KDE applications won't need X11 or UNIX compatibility layers to run. Now I must hasten to point out that the KDE Workspace isn't being ported away from Linux and Unix. It doesn't make much sense to run kdesktop, kwin, and the panels on the other platforms. KDE4 on Windows and Mac OS X will be a set of libraries and services that let the major KDE apps run so you have things like Amarok, Konqueror, and yes, Krita on (natively) Windows.

  57. Time to wake up to the real problem by edxwelch · · Score: 2, Insightful

    Lack of user feedback is not the problem with the gimp. Users have being telling the Gimp programmers for years what's wrong with their UI.
    The problem is that gimp programmers ignore all critism of their UI and likewise they will ignore this ridiculously complicated solution to gather user feedback.

  58. It's not that Gimp is hard... by element-o.p. · · Score: 1

    ...it's that people used to using Photoshop on Windows have to learn a different UI to make Gimp sing and dance the way they can make Photoshop sing and dance, and after mastering one program, most people don't want to have to learn something new.

    Back in the day, I used the freeware Paint Shop Pro (v.4, IIRC) on Win 3.1 and later Win 98. It took me a long time to learn Paint Shop Pro's UI, but I did finally learn it, and even really liked it. Eventually I upgraded to PSP 7.0 on Win2K, and had to learn the UI all over again. At first, I hated it and wanted to use the old UI I was used to, but finally, I figured it out. A little later, I switched to Linux and started using the Gimp. At first, just like I had done with both versions of PSP, I was unproductive because it was new, and I hadn't figured out how to use all the tools. A year or two later, my wife took a web design class at the local university where they used...you guessed it, Photoshop. She can't stand Paint Shop Pro or the Gimp, because she learned Photoshop, and is used to the way it works. So....when she ran into difficulty with Photoshop, guess who she always asked for help? And you know what? I had as much trouble doing anything in Photoshop as a Photoshop pro would have using the Gimp. Fast forward to the present, and while I'd rather use the Gimp simply because it's what I use most, and therefore what I am most familiar with, I *can* use any one of these three programs. I find PSP is a little easier for creating animated gif's (to be fair, I've not tried this with Photoshop). My wife has added some phenomenal effects to photos with Photoshop that I haven't been able to duplicate with the Gimp, but I find the Gimp easiest for most everything else.

    Okay, that's anecdote, I'm a computer geek, and maybe I'm just weird. However, my experience at work bears out my personal observations. We're a small company, and we simply can't afford to buy Photoshop for everyone here who needs to occasionally edit or retouch an image, so we put the Gimp on our employees' computers. Guess what -- while they might need a little help getting started, everyone that has used the Gimp has learned to use it with very little fuss, and most of them who have also used Photoshop gripe about what a PITA it is compared to the Gimp...because they use the Gimp more often.

    IMHO, the Gimp isn't really that hard, but it is different enough from what most graphical design people who trained on Photoshop are used to using, and that difference can be a real barrier to someone who views computers and software as merely a tool for accomplishing something else (i.e., most everyone who doesn't read /. on a daily basis).

    --
    MCSE? No, sir...I don't do Windows. Yes, I am an idealist. What's your point?
  59. Not scary at all ! by Anonymous Coward · · Score: 0

    Hmm, so I'm a GIMP user since around 2000. I use it it everyday for scientific images and also do some web design. Occasionally I use Photoshop which is installed on nearly all computers in the lab. I hate it - just because I'm used to the GIMP way of doing things. In my highly subjective opinion Photoshop's menu layout is confusing, the dialogs are ugly and the MDI interface makes me cry. Your mileage will vary, I guess.

    Btw, my copy of the GIMP (2.3.18) is only mildly customized: I added a hand full of additional keyboard shotcuts and put all those little option dialogs into one single window (using tabs with shortcuts to swith between them). That's it. Works like charm.

  60. Fork it already by Anonymous Coward · · Score: 0

    Seriously, why do we put up with these clowns? Let them finish off those juicy new features they're working on, take the code, and fork it. Wrap it all into a nice tabbed (one file per tab) interface in a single window. Change the name to something I can have on my work machine without my boss thinking less of me for it whenever he sees it.

    Do that, and do it well, and I guarantee your app will take the GIMP's place in the next Ubuntu release, which is really all you need to do these days to be king of the hill. And if somebody out there doesn't do this, maybe I ought to get off my ass and do it.

  61. one idea by ilovegeorgebush · · Score: 1

    I know: GIVE THE DAMN APPLICATION A BACKGROUND!

    Would be interesting to see the output of these automated observations, though...

  62. Crashing by hkmarks · · Score: 1

    I just installed Ubuntu after using Windows for years, and I have a lot of experience with Photoshop. I've tried GIMP numerous times on Windows and I'm starting to find my way around it under GNOME. The experience is much, much better in GNOME.

    I have two major problems with GIMP. One, of course, is the interface (skip this paragraph if you've read everyone else's comments). Why is the "file" menu -- or any menu other than toolbar options -- on the toolbar? There are too many windows. Windows get covered by others. Switching windows is a pain. Editing multiple images is just obnoxious. Each menu, image, submenu, and dialogue is treated as a separate window and it's horribly messy. This is a HUGE problem in Windows because there is only one desktop, and so GIMP interferes with every other program. In Ubuntu with Beryl it's not so bad because it's easier to switch desktops, so GIMP can have its own side on the cube. There's also more window control. But most computers still run Windows, and until it works better in Windows it's not going to be the next Firefox.

    Second is that it crashes under Windows. It doesn't work. It's unstable. At least it was for me, on three different computers over four years, running Windows ME, XP Home, and XP Pro. Maybe it's just me, maybe it needs tweaking before it works properly, but I'm damn good at following instructions, I followed the instructions, and it didn't work. If it crashes on Windows, the 85-90% of people who use Windows probably won't adopt it.

    For now, Paint.NET is a better free option for non-professional users using Windows, simply because it's more stable.

  63. Window clutter? by Anonymous Coward · · Score: 0

    So say you have a multi-monitor setup. Maximise your window. Only covers one window. If it covers both, there's a big gap in the middle.

    GIMP you can move the multiple windows can be shoved over to one and the main image window (which has very little clutter, maximising object space) can maximise nicely on the one screen.

  64. Banned from #gimp by FooBarWidget · · Score: 1

    Interestingly, I was banned from the #gimp IRC channel (actually, banned from the entire GIMPnet IRC network) for reminding the GIMP people about these complaints about the name. Was I being a jerk or are the GIMP developers really elitist like people on Slashdot usually claim?

    1. Re:Banned from #gimp by eternalnyte · · Score: 1

      You know, isn't it a bit counter-intuitive to complain about the name of the GIMP? I mean, c'mon.. let's say you create a program, and you give it a name. You LIKE the name, it's your baby, you name it. Now a bunch of people on slashdot and on IRC burst in and start saying "man, that name sucks.. change it" repeatedly.. It's not you're job to name it... I'd be pretty annoyed if people started an uproar over my daughter's name, give the GIMP folks a break.

    2. Re:Banned from #gimp by Trogre · · Score: 1

      This is a product we're talking about here, the name for which is supposedly meant to be meaningful and promote its use.

      BTW, your daughter's name sucks.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    3. Re:Banned from #gimp by eternalnyte · · Score: 1

      You are truly an expert in naming things in a way that is meaningful and promoting... I bow to you.

      http://www.urbandictionary.com/define.php?term=tro gre
      Urban Dictionary: trogre
      A troger is when a person is so ugly, they are a mix between a troll and an ogre. "Look at that girls face! What a trogre!"
    4. Re:Banned from #gimp by CronoCloud · · Score: 1

      I could be mean and say that some open source developers have no emotional sensitivity or understanding of user-needs or UI at all. That's what I've seen. It could be the GIMP developers, or the Pidgin ones or the ffmpeg ones. It's all "I released it to scratch an itch, I don't care if anyone else uses it at all. I am the developer, I'm not being paid, user opinions don't matter"

        If that's the case, keep it private and never release it. Personally I tend to judge projects on end user documentation, if it sucks, the developers don't care about their users and probably are like those mentioned above. Projects with good end user documentation get my respect.

      And yes, I just got banned from gimp.net too. Apparently they don't like being told the name is stupid. Yes, it's all traditionally recursive in that silly overly geeky way, and it's a Pulp Fiction reference but that doesn't make it a good name at all. In fact It's a stupid name. GIMP developers, admit it and change it and quit being stubborn about it. Personally, I think gnuImage would be nice.

      And just because other software has non-obvious names like "Firefox" or "Excel" or "Thunderbird" doesn't mean that the name "GIMP" sucks any less. That's no excuse. Fix it and end the complaints, then you can focus on the CMYK and 8 bit issues they all complain about.

    5. Re:Banned from #gimp by CronoCloud · · Score: 1

      How could they not know that using "GIMP" was a bad idea. Oh wait, I know, they're geeks who might be a bit lacking in "people skills" in love with their own recursive cleverness.

      As has been said, a products name should encourage people to want to use it, not discourage it. People have been complaining about the name for years, the GIMP developers are just to stubborn to admit they were wrong to have chosen "GIMP" in the first place.

    6. Re:Banned from #gimp by Anonymous Coward · · Score: 0

      In fact It's a stupid name. GIMP developers, admit it and change it and quit being stubborn about it. Personally, I think gnuImage would be nice.

      It's only a stupid name for some English-speaking people. I know a lot of French, German and Spanish users who think that the name is great. It is short, unique, easy to remember and it can be associated with "positive" terms in some languages (e.g., gimpel in German - also known as pyrrhula pyrrhula, or eurasian bullfinch - a nice bird).

      So I think that you blanket statement "it's a stupid name" only applies to a rather small number of users: narrow-minded English-speaking users. There are fortunately many more GIMP users who do not belong to that group.

    7. Re:Banned from #gimp by CronoCloud · · Score: 1

      Yes, I got this argument in the IRC channel. And it's a faulty one. The GIMP project began at UC Berkeley, right? English speakers, right? Then why did a bunch of native English speakers give a name that is known to have offensive connotations in English to a project.

      It's English, GNU Image Manipulation Program, the mascot is Wilbur not an Eurasian Bullfinch.

      The whole "It's not offensive in foreign languages" excuse is just that, an excuse to be stubborn and not admit the original mistake.

  65. Am I the only Fireworks user here? by glittalogik · · Score: 1

    (Smackdowns welcome if I'm wrong about any of the following; just my personal experience.)

    I've got GIMP as part of my default Ubuntu install, and it's never impressed me much. I agree with the general gist of previous comments which is that the UI doesn't need to be like Photoshop, it just needs to be decent.

    The dealbreaker for me at the moment is the piss-poor Text tool. A few days ago I wanted to make some text with a border around each letter. Tried to find a border colour setting, no go. Looked up a few tutorials, and it's a frigging ten-step process using multiple layers and tools, wtf? I tried Krita, and that was even worse as far as I could tell, and I'm not sure where to go from here as far as Linux apps are concerned.

    All the previous comparison comments here are in reference to Photoshop and PSP, but I recently got given a copy of Adobe Fireworks to use at work for a variety of daily tasks, (mostly straightforward stuff - cropping, resizing, adding text to diagrams, basic compositing) and I love it! Whilst everyone grimaces at the mention of its name, it does what I want easily, intuitively and well. Despite minimal graphics experience and no claim to expertise with any particular software package, I have never had to go hunting for a special tool or look up a tutorial in order to create white text with a 2px black frigging border. It doesn't seem like too much to ask, I don't see why it should be such a challenge in other apps.

    1. Re:Am I the only Fireworks user here? by Anonymous Coward · · Score: 0

      I am a professional web developer. I have been using Fireworks for years for designing web pages and application interfaces. It is by far my favorite program for this kind of work. I can do more crazy stuff with Photoshop, but if you are designing a UI less is more. I especially love the interface. When I first started using Macromedia products it took some time to learn their "way". I find it is more efficient than GIMP and the focused nature of Fireworks makes it better for web graphics. Photoshop can do web graphics of course, but it can also do print, CMYK high color, wash dishes, make biscuits etc.

      I wish GIMP were more usable for web design.

  66. Each gimp window with its own dedicated monitor by Anonymous Coward · · Score: 0

    I wish you the best. Unfortunately I'm sure GIMP developers once they hear you
    about the multiwindow design and the non maximalisation of the main window
    will just decide that each gimp window should have its own dedicated monitor.
    And they'll recode things so that opening a new window witout a dedicated
    monitor will just output a new error message:
                You do not have enough monitors, for usability reasons each gimp window must be
    maximized in one physical monitor, please add more monitor to your system. A 6 monitor
    system is the minimum you should have in order to run gimp (don't forget that you
    nee a seventh monitor if you want to run other programs at the same time as gimp).

  67. Re:GIMP will always be a gimp by MobileTatsu-NJG · · Score: 1

    "They should start over and model it after photoshop. The could call it photoshoppe."

    One man's 'off-topic' is antoher's 'insightful'.

    --

    "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

  68. +10 Flamebait and Lulz by ozphx · · Score: 1

    > What is the typical monitor resolution of a GIMP user?

    640x480 VESA due to lack of Free(tm) drivers.

    > Is the GIMP used primarily for photo editing or drawing?

    Neither.

    Many have tried and failed.

    Thank you, I'll be here all night ;)

    --
    3laws: No freebies, no backsies, GTFO.
  69. THAT IS NOT THE SAME THING by Anonymous Coward · · Score: 0

    The term 'gimp' is NOWHERE near as derogatory as the n-word. Don't even compare them. Using it as a silly example on /. only shows your ignorance.

    1. Re:THAT IS NOT THE SAME THING by Anonymous Coward · · Score: 0

      The Gimp is still a stupid name. After all these years, even the hardiest Gimp users are embarrassed to tell their coworkers what image editing software they use.

  70. Glad! Thought it was just me! by BillGatesLoveChild · · Score: 1

    I recently started using GIMP after listening to years of raptured ravings by the GIMP fantribe.

    Got to say I was disappointed. It's very unwieldy. Windows everywhere, missing hotkeys (annoying absent on frequently used items), no easy way to add a macro (even if you have to do the same six steps on forty photos), unclear design (a bad mental model: often you're scratching your head... so what the hell do I do now?) If anyone says "but you can do this", they miss the point. GIMP is far too hard to use. The help isn't very good: few clear examples, and the only way to find help on something is to know how to do it. Maybe there are good books out there, but the ones I've looked at haven't been up to much.

    The good news is GIMP does work and it's better (and cheaper!) than many of the alternatives. The GUI definitely needs an overhaul.

  71. Let me get this straight... by sasserstyl · · Score: 1

    The gimp team are creating a network-based data gathering system to conduct a usability study.

    Hello?!

    How about simply asking users to report their experiences? Or even watching people use the software?

    Sure, it'll involve a bit of human to human interaction but come on - its a price worth paying!

    Yes, the Gimp is already a great tool but:

    1. It's nowhere near Photoshop in terms of out-of-the-box functionality
    2. Please, if you insist on having a separate window for everything, write a little window z-order controller that ensures the relevant windows are visible (i.e. like photoshop does)

    And you want to know what peoples' screen sizes are? Here I'll save you the effort - exactly the same size as all the customers who can happily use adobe photoshop.

    1. Re:Let me get this straight... by BigSven · · Score: 1

      First of all, it's not the GIMP team working on this. The GIMP team is busy preparing GIMP 2.4. The ingimp developers are different people. We are communicating and helping them with technical questions. And at some point we might consider integrating this code into GIMP proper. Of course as an option and certainly not without asking the user.

      You said "if you insist on having a separate window for everything, write a little window z-order controller that ensures the relevant windows are visible". Good point. Well, that's what the concept of transient windows is good for. And GIMP 2.4 will make heavy use of that.

    2. Re:Let me get this straight... by sasserstyl · · Score: 1

      Thanks for your clarification re the separation of the Gimp team and the ingimp developers. It sounds to me like you have the z-order issue in hand for release 2.4. Great stuff! My criticism is meant in a constructive way because I would like to see the Gimp succeed.

  72. Double crossing by tepples · · Score: 1

    You can put lipstick on a pig but in the end, you still have a pig. ... and that pig will be the object of thousands of zoophiles' hot fantasies! Wait - what were we talking about...? Animal Crossing.
  73. Photoshop vs. Gimp Flame War! by crhylove · · Score: 1

    I'll fire the first salvo:

    They both suck.

    I've used Photoshop, and the Gimp for 6+ years, and I have to say, both interfaces suck. I don't have any specifics for improvement, but I'm sure I could come up with some if I were sitting in front of either one right now. I just know both interfaces are clunky, counter intuitive, slow, require too much screen real estate, buggy, bloated, and archaic.

    Granted, they each have advantages over each other: Photoshop does CMYK, some of the tools just "work" better, etc. Gimp is less bloated, offers more handy functions "out of the box", and is cross platform.

    But let's zoom out and look at the larger issue, which is that, in 2007, our photo editing and graphics arts programs should be a lot farther along. I should be able to do illustator or inkscape style things directly in the gimp, and I should only need one program to do all of that with an easy menu, and easy and obvious shortcuts. As of right now, the only shortcuts I use are copy, cut, and paste, because all the other ones link to some function I rarely need. Like how about a ctrl+s that automagically makes a drop shadow of the foreground layer? Or a ctrl+o that automatically gives a font an outline? The current ways of doing this in the gimp, which I do about 100x a week, at LEAST are ludicrously slow, and require me to use wild ass script-fu, and then copy, and then undo, and then paste.

    Heaven help me if I'm away from home and on some winblows machine that is loaded down with Norton. Simple tasks can take an hour!!!

    rhY

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
  74. Then why not KIMP? by tepples · · Score: 1

    It does, GNU="GNU's Not UNIX", GIMP="GNU Image Manipulation Program", GTK="GIMP Tool Kit". IE, they can't really "drop GTK", GTK was created for GIMP!

    Names can be changed. For example, why can't they just use Qt and make KIMP?

    1. Re:Then why not KIMP? by akita · · Score: 2, Informative

      They (KDE) tried, but the gnome fundamentalists didn't let them. This was in the middle of the gnome/kde wars, when Qt wasn't pure enough for some.

      You can still find references on the web:
      http://dot.kde.org/1096230607/1096270511/

      I always think, what if they did it ? It would be better than gimp for sure, seeing the quality of other kde apps at the time.

    2. Re:Then why not KIMP? by akita · · Score: 2, Informative
  75. in the real world by Anonymous Coward · · Score: 0

    I started with NOTHING AT ALL to speak of on Windows 3.1 and 95 ahd 98. Then I migrated to Linux with Xv and ImageMagik and eventually GIMP. Using them in the real world was torture, but it was the only wheel in town. Fortunately, I am a submissive masochist when it comes to graphics tools. Eventually. I migrated to a Macbook Pro with Photoshop CS, then CS2 and the beta of CS3. Every freaking step was torture. Being able to use color management and having more than 8 bits per channel while manipulating images keeps me tied to Adobe. It's not just the freaking user interface. They are all different. They all suck. Any questions?

    1. Re:in the real world by Anonymous Coward · · Score: 0

      OK, so I'm lying my ass off. I really started on an SMPTC 6800 with an ASR-33 for both 110 baud I/O and non-volatile memoty (paper tape), then graduated to a Radio Shack Model 1, and began incorporating Z-80 assembler code in Microsoft BASIC programs to make any kind of graphics program do something interesting. I waded through CP/M, then CP/M-86, MS-DOS, IBM-DOS, GEM, Windows 1.0, 2.0, 3.0 OS/2, NT, 95, 98, 2K, XP,2003 ad nauseum. So now you have it, 1977 to 2007. Things are a hell of a lot better, but they still suck more than most people will ever know... sheesh

  76. tools ... ? by pbhj · · Score: 1

    I thought gimp was a photo-editting prog not a drawing program. For tools I use inkscape.

    What I'd love to see is a unified canvass that any drawing prog could use. You could then choose any tool from any package you liked ... you could do a gimp-color rotation then proceed to use the vector editting tools of inkscape, add on some text boxes using scribus - all without closing the image window. Even if the apps wrote to different layers of one canvass that would be awesome IMHO.

    Anyone seen this idea in use anywhere?

    1. Re:tools ... ? by eternalnyte · · Score: 1

      You know, that is a great idea... difficult to implement, though, as you'd need to have all image editors implement support (or at least I think you would).. Maybe an "image server" sort of application that provides a standard interface and just stores the color/alpha info for a layered image, then it would be the application's job to edit and communicate the changes to the server? Hmmm... there's got to be a better way but it certainly sounds interesting, especially for a graphics workstation, maybe not too useful for others.

  77. Probing Questions by ThatsNotPudding · · Score: 1

    "The project hopes to answer questions such as 'What is the typical monitor resolution of a GIMP user?' and 'Is the GIMP used primarily for photo editing or drawing?'"


    Plus the biggie: "How many effing times is this a-hole gonna photoshop a picture of a rabbit with a pancake on it's head?"
  78. Will this really help usability? by Sperlock · · Score: 1

    Looking at the statistics given on ingimp's site, most of these give quantitative data - the number of times a command was used, image sizes, monitor resolutions, OS, etc. The "activity tag" data at least gives an idea of what a user is using GIMP for, but I'm not seeing it being tied to the commands used for that particular activity. I can only see this being mostly useful for determining who your users are and what they are doing, but from there these should be turned into personae that can be used for actual usability testing to help find usability flaws. Take these activities and find someone to try to do them, have them speak their thoughts out loud, and then see where the real usability flaws are.

    --
    http://informationthreshold.blogspot.com - Information Threshold
  79. gotta love that double standard by Anonymous Coward · · Score: 0

    so when microsoft does this in windows it's the evil empire violating privacy, but when it done in a piece of shit knockoff of photoshop it's a good thing...

    i'm shocked....

  80. Multiple windows and different window managers by wrook · · Score: 1

    I never understood why people keep complaining about the GIMPs multiple windows. Yes, it's weird if you've only ever used Windows apps (or apps pretending to be Windows apps). But personally I *like* mutliple windows. It means I can squirrel away functionality that I don't care about and bring it back easily. I arrange my windows on the screen the way *I* want and I use the window shade functionality of my window manager extensively. I'm *happy* with mulitple windows and multiple menus.

    Well... usually. You see, I had occasion to use the GIMP under Windows the other day. And I couldn't use a damn thing. #$%!ing windows poping up all over the place. Couldn't iconify and uniconfy things the way I wanted to. And to top everything off, I'm clicking to focus every bleeding window every 3 seconds. Talk about frustrating.

    Sersiously. I *hate* single window apps with a passion; big bloat-creatures with functionality jumbled all over everywhere. But I can understand why some people positively can not put up with multiple windows. As a developer, I personally think the flaw lies in the window manager (or the fact that you can't choose your window manager). But as a user that needs to get things done, I understand the point.

    It would be nice to be able to have 2 modes for the GIMP. One for each kind of user.

    BTW, I'm thinking of moving over to a tiling window manager... I expect I'll want something even different then.

  81. Everyone knows what the problem is by raddan · · Score: 1

    Ingimp will not change this fact. The devs simply disagree whether it counts as a 'problem'. I don't think it's any secret that the majority of the people who come to The GIMP, especially those with a Photoshop background, simply can't grok the UI. And there's no denying that The GIMP's UI deviates from almost every other application's model out there. In fact, the only similar one I can think of is xv; hardly stuff for newbies.

    This study perpetuates that denial: the people who give up on GIMP do so almost immediately. It's not just a Photoshop background that ruins it for you-- it's prior experience with Windows or the MacOS. The GIMP is simply too different. What useful information are you going to gain from people who give up immediately? Or if they spend all their time looking in menus having to do with color-- how will you know that they need a specific color model without them being able to tell you?

    Now it may be that for people with no prior experience with the above mentioned programs, or for those who are willing to spend the time to learn The GIMP's unique way of doing things, then maybe The GIMP really is the best way to edit images. But, as Eric Raymond has pointed out-- sometimes it's not enough to be "the best"; the cost of switching also has to outweigh the cost of learning a new way of doing things. Considering that Photoshop falls into the "extremely expensive software" category, what does this say about The GIMP when The GIMP is free of charge? If what the devs really want is for people to flock to The GIMP en masse, then they need to pull their heads out of the sand: The GIMP UI is a problem. Otherwise, we can safely put The GIMP into the category of extremely useful (and even revolutionary) but oddball software out there like Plan 9, TEX, emacs, and so on. It'll continue to be used rather successfully by a vocal minority, but it won't be the standard.

  82. The UI is not the Major Problem by Pisal · · Score: 1

    The UI isn't the main problem with GIMP. You can teach a person who is willing to learn to use a new app if they are willing to learn and the management is persistent enough.

    The problem with GIMP lies however on its speed when working with a larger picture. When an extremely detailed picture is used, GIMP doesn't work as well as Photoshop in terms of speed. With the same computer and same large picture, it takes ages in GIMP to move around or do anything, whereas it is a breeze in Photoshop. Now that is a frustrating experience that would cause people to migrate back to commercial programs.

    1. Re:The UI is not the Major Problem by BigSven · · Score: 1

      Try a recent development version then. We have addressed exactly that problem lately. Panning the zoomed out view of a large image is a lot faster now and the quality of the zoomed out view has been improved at the same time.

  83. Quick: Where's this simulator? by tepples · · Score: 1

    If you're willing to spend five seconds looking at your options, you'll have no difficulty finding a Linux equivalent for any common task. Quick: Where's the "simulate running an orchard, paying off a mortgage, pimping your house, and chatting up virtual neighbors" program for GNU/Linux? How would I go about looking for one?
  84. Windows vs. tabs? by tepples · · Score: 1

    I think you're not qualified to study usability if you have to Alt-Tab through a bunch of firefox instances because you haven't discovered tabs yet. What is the difference between Alt+Tab through a bunch of windows, whose names are across the bottom of the screen in the taskbar, and Ctrl+Tab through a bunch of tabs, whose names are across the bottom of the location bar?
    1. Re:Windows vs. tabs? by Chris+Shannon · · Score: 1

      I'll admit that sometimes it's useful to have 2 firefox windows open, say one for work, one for other stuff, or to compare or copy and paste. But this guy had 8 open! I dislike this because the Alt-Tab window in Windows does not show the program name until you select it, making it very inefficient for switching quickly. The order of the programs on the task bar is not related to the order they are in the Alt-Tab screen. Also, if you have your task bar on auto-hide to keep it from eating up your screen space, you can't simply glance at it, like you can with your firefox tabs. Also your firefox tabs adjust their size dynamically to use the most of the available space.

      For me, the reason I prefer tabs so much is that you can open all new links in background tabs with middle clicks. This allows you to continue reading the current page and lets you know when the new link has completely downloaded at a glance. But more fundamentally, it keeps your workspace organized. It's easier to control-tab, to move one tab to the right, and control-shift-tab to move one tab to the left, than it is to slowly alt-tab to the correct window. Also, by using tabs, you only need one Alt-Tab to switch to another application.

      With relevance to the gimp, I notice that I spend an unnecessary amount of time ensuring the various windows and dialogs are not blocking each other, or being blocked by another program's window. It's a pain to alt-tab between 4 or 5 Wilbur icons, having to read the title at each step. In Linux, I make sure to run the gimp on its own desktop. In windows, I'm forced to minimize everything but the gimp.

      The common theme among instances vs. tabs, gimp interface, multiple desktops vs. single desktop can be summed up in one word: hierarchy. Linux desktops environments like KDE and Gnome get this right. Keep your email client, and all email related stuff in one desktop, web browsing in another desktop, the gimp in yet another. Keep your various work related applications in their own desktop. Switch between them with Control-F1 (through Control-F8).

      Each desktop's Alt-Tab will be local, greatly reducing clutter. In Windows, when you get to have that many programs running, it takes all day to alt-tab between them, and you're pretty much forced to close some. The gimp adds to this problem by introducing multiple windows when there should be only one. They are on the right track with having "Layers, Channels, Paths, Undo" all in one docked and tabbed dialog.

      From wikipedia:
      The number of windows used by GIMP's interface can cause desktop clutter. This is not only because the GIMP uses a (controlled) single document interface, but also because it uses multiple windows for its tools, color palette, etc. (unlike many competing graphics programs, which use a multiple document interface or an SDI with integrated toolbars).

      That would be number 1, on my list of Gimp usability suggestions.

      Having said all this, once you get to find all the useful features, and creating shortcuts to them, man is it ever fast!

      --
      "Follow me" the wise man said, but he walked behind.
  85. copy the leader by Anonymous Coward · · Score: 0

    Why is it so difficult for gimp to get a usable interface? Why don't the developers do what most other applications do- follow the leader and borrow their look and feel. If its illegal, the Microsoft should be in prison. So forget this nonsense about improving it with feedback...just look at what others are doing and copy that.

  86. hah...I love Gimp by Urza9814 · · Score: 1

    I personally love Gimp's interface. What I can't STAND is Photoshop's. Takes me forever to find the shit I want on that piece of junk.

  87. Advanced interfaces/the interface of the future. by input.expert · · Score: 1

    Usability, gui, cli, and the stand alone keyboard and mouse.

    The problem with program/application usability is the inflexible default program/application interface.

    I have been working on the wasted repetitive hand movement from keyboard to mouse for the last three years. I have solved this problem with an advanced integrated keyboard mouse.

    I have total control of the on screen interface and can point, click, type, and scroll in any order simultaneously and instantly without taking my fingers off the home row, and have not lost any of the performance or speed of a stand alone mouse.

    With an integrated keyboard mouse, the debate between the gui and cli is a non-issue to me. I can use gui or cli on the same interface equally with no performance loss.

    The problem between gui and cli was the stand alone keyboard and mouse. When you integrate the keyboard and mouse, you can integrate the gui and cli with big performance gains.

    I have the same performance as if I had two hands on the keyboard and a third hand on the mouse.

    I dominate current gui and cli users, because I have equally access to both gui and cli.

    I can work, so far, across four 19" screens at will.

    I am now working on an advanced interface that is fully customizable by the user that sits on top of all applications. It integrates gui, cli, and search.

    We all work differently. We each need a personal interface. That is my goal, to have a fully customizable interface that sits on top of all applications.

    I hope to provide my keyboard to financial traders and the military first, because of their need for microsecond input and control.

    I hope to present my research and development on advanced input, interface, and interaction technology to a HCI or ACM conference for requirements for my PhD in advanced HCI.

    from the "father of the perfect keyboard"

  88. Suggestion by Tablizer · · Score: 1

    One thing that bothers me about gimp and other graphic software is the fricken "feature bath". I've used many options/features before but forgot where it was. Perhaps have a wild-card search of options with the ability for one to put in their own supplimental keywords. Menus have outlived their usefulness for feature-rich software.

  89. well that's insightful by r00t · · Score: 1

    Now that you put it that way...

    I ought to be able to close the toolbox. Sometimes I don't even need it. I do always need an image window though; keeping the gimp open without one is only useful to avoid the agonizingly slow start-up if I want to work on another project.

  90. multimonitor not required by r00t · · Score: 1

    You do however need virtual desktops to keep your sanity. Linux obviously supports this very well.

    MacOS Tiger has virtual desktops. Perhaps you'd like to use that?

    Numerous add-ons for Windows are available. Wikipedia has a list of a few dozen implementations. (see the "virtual desktop" entry and stuff linked from there) It seems that people are dying for virtual desktops on Windows, but Microsoft doesn't give a shit. Have you thought about getting a Mac?

    1. Re:multimonitor not required by Skye16 · · Score: 1

      I enjoy building my computers, and what's more, I love knowing I can build a computer with the same specs and performance of a Mac Pro and it'll cost me half as much to do it. Hell, the best part about getting a new computer is putting all of it together :]

      If it weren't for the required hardware purchase, I'd *love* to move to OS X. Unfortunately, I'm not worth the effort to Apple, so my money will stay firmly wedged in my pocket :D

  91. eliminating self-selection bias by r00t · · Score: 0, Troll

    Because involvement in human-subjects research is voluntary, there will always be a self-selection bias. Hmmm. How about making it non-voluntary?

    First, pick a random person. I suggest paying somebody with access to a government database. This will ensure that you don't miss babies, incarcerated people, people without phone numbers, etc.

    Second, go get them. You could have a couple of your larger graduate students just shove the human subject into a van and hold them down. Another option is to threaten the subject with a shotgun.

    Third, sit the subject down in front of the gimp and make them do stuff. Getting people to actually use the gimp will often require the shotgun. Observe any discomfort, panic, frustration, or anger that the subjects experience while using the gimp.
  92. Wrong aproach! by slashmais · · Score: 1

    The first principle for any application that has a non-specialized user base is that it must be intuitively usuable.

    From the blurb: "The project hopes to answer questions such as 'What is the typical monitor resolution of a GIMP user?' and 'Is the GIMP used primarily for photo editing or drawing?'""
    This does not give any pertinent information on making obvious actions available in the UI.

    The above two 'questions' are nonsensical: they refer to functional areas/modules/settings that should be choices offered by the UI.
    Once that choice is made the UI should allow immediate, intuitively obvious actions for that choice.

    The (to call a spade a spade) stupid UI currently offered by the GIMP made me drop it, and revert to simple easy, obvious bitmap editors.

    --
    time time everywhere and not a second to spare
  93. you forgot gamma by r00t · · Score: 1

    Out of your list, the 8-bit channels are the only problem for me.

    I hope they never add CMYK crap to the core. Native Y,Cb,Cr would be kind of useful though, to avoid round-off errors when editing JPEG images.

    Gamma probably the worst problem. It might actually be what you see as antialiasing quality problems; that can be a symptom of treating non-linear data as if it were linear. Nearly all of the gimp does operations on non-linear datathat are only meaningful on linear data. The result is image degradation. Besides generally making colors wrong, image noise can stand out more and antialiased edges can become darker.

  94. What, something wrong? by r00t · · Score: 1

    How can you not like a program named after a midget or dwarf used as a submissive for gay sex?

    That's an entirely appropriate way to name a graphics program.

  95. IMP, not GIMP by advocate_one · · Score: 1

    drop the G just call it Image Manipulation Program, or IMP for short... oh, that might just offend some of the religious fundies out there who'd think it could have a satanic connection...

    --
    Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
  96. Single window interface by Anonymous Coward · · Score: 0

    I installed GIMP to many users that never used a drawing program before.

    The first thing they do is maximize the toolbar window, and the second is close the layers window. This results in a completely useless application. Users are by default not used to use applications with multiple windows.

    Inkscape's predecessor Sodipodi (http://www.sodipodi.com/index.php3?section=screen shots) had a similar interface as The Gimp has. Inkscape's developers managed to make a usable singlewindow interface, so I think this is the way Gimp's interface should be headed.

  97. PS keybindings by BigSven · · Score: 1

    Why didn't you just use the Photoshop keyboard bindings that ship with GIMP? For someone who is coming from Photoshop, that should make things a lot easier. For someone who is accustomed to the keybindings used on the GNOME desktop, it will feel akward though.

  98. A quasi-novel solution! by Ayanami+Rei · · Score: 1

    GIMP should allow you to:
    * Undock the "toolbox" from the main application window (file/acquire/prefs menu area, essentially)
    * Minimize the main application window to a system tray icon on Windows
    * Allow it to run "widgetless" like a daemon on unix (where opening up an additional image is as easy as running gimp "filename" from a terminal or launched as a result of a GUI file action)
    * Duplicate the file/etc menus in the right click menu for said system tray icon on Windows

    I think something like that would make a lot of people happy.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  99. The thing about stuff like drawing circles... by Ayanami+Rei · · Score: 1

    Since version 2.0 they try to push you in the direction of drawing a circle with the path tool (or converting a circular selection to one) and then stroking it with a brush.

    Everyone using the GIMP without a tablet should be shown selections, paths, and manipulating them in tutorials, because that's what you're going to spend a lot of time doing if you can't freehand.

    --
    THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
  100. Windowmanager - screens by Anonymous Coward · · Score: 0

    Not everyone has a window manager that can set always on top Its Opensource. The reason everyone doesn't have a windowmanager that cant do "allways on top" is because everyone does not want one.

    If everyone/you wanted this functionality, nothing stops you from getting a windowmanager with said functionality built in.

    and even then it's not great because the windows will be over other programs as well so when I switch to Blender I still have the tool windows visible For the Blender-problem, use another screen (ctrl-alt-rightarrow)

    Gimp also kicks ass whan you have more than one physical screen, you can work on the fullscreen image on your main screen, and have the controls and smaller images on the secondary one. The imaginary screens hold the rest of the programs (bluefish, anjuta, terminals etc.)
    1. Re:Windowmanager - screens by KDR_11k · · Score: 1

      I'm using it under Windows because the programs that the finished output gets thrown into are usually Windows-only. More screens and different window managers require extra software for something that other apps do out of the box.

      --
      Justice is the sheep getting arrested while an impartial judge declares the vote void.
  101. Well then make it one window by 5of0 · · Score: 1

    If you don't like it, change it...use the deweirdifyer. Or xnest on Linux. Problem solved. I went more in-depth in my comment below.

    --
    You all have Oo.o and Firefox, so get World Wind.
  102. Re:Self-selected group? Self-denial? by Dekortage · · Score: 1

    Sounds like GIMP lacks good print preview or print tiling mechanisms. Tiling is when the program prints out the image across multiple pages, with overlap on each page, so that you can cut out and assemble the pages into one larger printed image. I'm betting it lacks slicing, too, which is something Photoshop/ImageReady excel at -- taking a large image and blocking off areas to be saved as different image files, each with its own file name and type (GIF, JPG, PNG) and compression settings. This is invaluable for web design. (If GIMP does this, that's cool.)

    --
    $nice = $webHosting + $domainNames + $sslCerts
  103. Just dump it by jmcoursi · · Score: 0

    Everyone has always complained about the interface for years and the developers refuse to hear. They keep insisting that you don't know how to use your screen space. Since a program is only as good as its team, I don't see any hope unless fresh people take the lead. But who would like to do that ? There are probably better alternatives for first-class people.

  104. GIMP is not installed by default aka Unknown by Anonymous Coward · · Score: 0

    1. GIMP is UNKNOWN to most users

    Most computer users don't know about the GIMP. Commercial companies advertise, GIMP don't. It's a mistake to compare GIMP to Mozilla Firefox, because Netscape was known to millions of people in the early days of the web, and this is a big part of the success of Firefox today combined with ads. Most computer users have Microsoft Windows, and installing third party software is very difficult for most users of Windows. You have to search the web for "image manipulation" or "photo editing" or something like that just to find software, and to install GIMP you need to download and install TWO packages - IN THE RIGHT ORDER from the GIMP for Windows pages. GNU/Linux users have it easy, because GIMP is most often installed by default or available for selection among installable packages.

    The point of this point? The number of POTENSIAL users of the GIMP on Microsoft Windows is dropping - FAST!

    2. Getting your own images into a computer is UNKNOWN to most users

    If you have a new computer, you probably have a card reader somewhere on your computer. If you are lucky or forward thinking, the card reader can read the kinds of cards your cameras have. Just pop the card in the reader, and follow the instructions on screen. No instructions? You have an old version of Microsoft Windows.

    The point of this point? The number of people who will actually do any image manipulation at all are dropping - FAST!

    3. Image manipulation is UNKNOWN to most users

    Okay, you have your images, you find Open, you manage to find your images even though the folders look weird in the GIMP. Hey, there's the family! Ugh! What devils are these? Red eyes - oh no! And that ugly thing from aunt Mildred to the side there - how do I get rid of that?

    The point of this point? Most users don't know how to do the things they would like to with their pictures, regardless of package.

    4. Image manipulation is KNOWN TO VERY FEW PEOPLE

    And that's the main problem. Not the GUI, not shortcuts. However, for those very few people who do know, mostly professionals in advertising, what are the their main problems with the free software alternatives compared to Adobe's range of products?

    a) Workflow - swithing between different Adobe products is quite easy, given similar menues and names for the same operations across the product range. How is this for GIMP, Inkscape, Kino and Scribus? Did it become just a little harder to remember the correct way?
    b) Revision control - built in and preserved as you move between Adobe applications. You need this when working in a team on a project for a client.

    The point of this point? Professionals work in TEAMS, they work FAST to keep clients, they need a SERIES of tools, they need QA, they need training. All of this is possible with free software too, but how many are doing it AND telling others about it?

  105. A simpler way of getting usability flaws by DrXym · · Score: 1
    Sit various graphics designers, novices, casual users, expert users in front of GIMP and listen to what they say. I guarantee that you will come away with hundreds of comments.

    GIMP has fundamental usability issues which have festered for years. I've had the odd rant about GIMP going back years and most of the issues are still there. They really should stop feature development and make the next major release all about cleaning up the existing functionality. Despite the atrocious UI, the GIMP is an amazingly powerful tool. It's just frustrating to use, and IMHO the effort and time currently required to use it is probably DOUBLE what it could be if it were cleaned up.

  106. i just told them to get fucked for you by Anonymous Coward · · Score: 0

    god bless

  107. Why do that? use common sense to fix it. by master_p · · Score: 1

    And common sense says:

    1) use an MDI interface.
    2) group similar functions together.
    3) use better and more informative icons.
    4) follow the new/open/close/save/cut/copy/paste paradigm that everyone else uses.
    5) use the right click as a contextual menu.

    etc

    No need to instrument the program, just go ahead and do it as a regular application.

  108. What i find funny by EachLennyAPenny · · Score: 2, Interesting

    Open any book about usability. On the first pages you'd come across the axiom to avoid creating a menu structure which is more than two levels deep. Gimp's menu structure on the other hand is deeply nested. There are so many basic usability problems which could be easily corrected without using any special software.

  109. Instead of trying to develop every new thing... by Anonymous Coward · · Score: 0

    ...listen to the gripes that have been around a while.

    Needs a properly working palette dock. Having separate windows all the time gets clunky if you only have a single monitor setup. Also why clutter the taskbar? People doing web development or other multi-app multitasking don't care for that much.

    Also needs better tablet support. Should have a little better tablet sample rate so you don't get jumpy straight segments when trying to do a quick stroke. Reading pressure sensitivity properly on *ALL* OSes and tablets really is a big deal too.

    Future printing support (since printing is where PhotoShop/Illustrator are making the big $$ from) would also be good, but interface usability should have priority.

    For the most part Gimp is cool. It fills in a niche that few others in the free open source community are trying to satisfy. Developers just need to take users who aren't programmers more seriously instead of telling them to read the source and make their own changes.

  110. Batch Operations by weberjn · · Score: 1
    Got a digital camera? Want to resize and sharpen a chip full of images for web? Tried that with Gimp? Without Lisp knowledge?

    With Irfanview it's something like select images and do operation on the images. With an off-the-shelf Gimp it's not possible.

    see: Bug 173066 - Feature Request: Batch-Processor

  111. And if the devs are fine with that by Anonymous Coward · · Score: 0

    why should they care what marketshare they have?

    WE AREN'T COMPETING! We're producing what we like and letting people build off it. Write your own, you can either use the GPL code (and therefore maybe start a more useful fork of GIMP) or start from scratch and keep it propriatory. I don't care. What I DO care about is you making out that we're dumb because we aren't doing what "needs to be done" to increase market share.

    That aint what we're doing. We're writing programs for ourselves.

  112. What about the people that don't use it? by Anonymous Coward · · Score: 0

    I absolutely can't stand GIMP because of it's usability flaws...it just plain sucks when it comes to things like that. The only people that do use GIMP are people that have gotten used to it's weird quirks so getting data from that subset of people will only help that subset of people already used to the quirkiness.
    If they really want to fix the usability issues of GIMP they need to totally rework the UI from scratch in my opinion. It is already too bad to make any improvements on it that will help out the mainstream user.
    Just so you guys don't get the wrong impression, I am a programmer (not a graphic artist) and use Linux extensively mostly via command line so Im not one to care about UI all the time. But when it comes to graphics program you really need to have a good UI if you don't want to waste a bunch of time.

  113. Better yet... by drakaan · · Score: 2, Informative

    ..at least for those of us using Windows XP or (shudder) Vista:
    Paint.NET is getting better and better (and has an active user community creating plugins, etc). I tried it about 2 years ago and wasn't all that impressed, but as of my latest inspection, it's pretty useful software. Just make sure to check out the forums for effects and tutorials.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  114. CTRL+K = Delete by Annymouse+Cowherd · · Score: 1

    My least favorite thing about the GIMP is that Ctrl+K is delete, not Delete.

  115. GIM Paint by bagofcrap · · Score: 1

    I've always just called it GIM (pronounced Jim) Paint.

  116. Noob usability report by Frantactical+Fruke · · Score: 1

    A month ago, for the first time in years, I needed to work on an image. LastFM wanted a picture of me, but complained because it was not square enough. Well excuse me for being an elongated person.
    So I open the Gimp 2.2, load the picture and look into adding a white sidebar with my name on it. Let's walk the menus. Image - Canvas size looks good. I widen the Width, but the Height grows with it. After some headscratching, I figure out that the pretzel icon next to the box is a lock. A mouse hover tool tip might be good here. But cool, now it's 600x600.
    Hey, why is it checkered gray? Let's fill that with white. Select the bucket icon in the toolbox and swap the foreground color from black to white. The tooltips are great here! Click on the checkered gray area to color it in. Nothing happens! Now what?
    Maybe it's one of those layer thingies the pros mumble about. Menu troll time!
    That was funny! Layer - Transparency - Add Alpha channel didn't seem to do nothing, but went gray afterwards. Let's try color to alpha next. All right, the dialog has a white box, so maybe it'll turn this alpha layer white? Oh no, now the whole picture's checkered! Undo undo undo.
    Image - Fit canvas to layers resizes to the size of the original picture. Aha, I need another layer to cover the checkered area!
    Layer - New layer seems to do the trick, as the broken line is now around the whole canvas. So now the fill tool should work, right? Aaaah, now the whole canvas is white! Where's my photo? Try some layer menu things, but I seem to have to white layers here. Undo.
    I choose Select rectangular region tool from toolbox and mark the checkered area. Now the bucket fills just that part! All right! We are making (slow!) progress.
    Now let's write into it.
    I choose the Text tool, click where I want to write, oops, must move mouse onto the text dialog, or the writing will be interpreted as a tool switch, oh and switch foreground color to black, yes.
    I write my first name and last name into different boxes to arrange them nicely.
    Can't move them around apparently. Can't click on the text to edit it. I'll just erase them and rewrite. Oops, the Eraser does not do ANYTHING AT ALL. Undo and rewrite then.

    Okay, I can figure out most things here. It could be more obvious, but it works. Except for the Eraser, which does not erase anything. I remember using Paintshop Pro seven years ago. That was easy and fun. You just tried everything in the menus to learn more. With the Gimp, I feel I need a book or help dokument to explain layers or something to me *first*, before I can do anything painlessly.
    But I don't need image tools more than once a year, so I'll just have to suffer through this learning curve every time I touch it.

    1. Re:Noob usability report by Anonymous Coward · · Score: 0

      Huh. I guess I know the GIMP better than I thought I did. In case you or someone like you needs help with a task like this, here are the steps:

      1. You got the canvas size right. The lock is actually a chain link. The height and width are "chained" together so that when you modify one, you modify the other. Yes, a tooltip would be welcome here. I've seen the "chain" metaphor in other apps, so it made sense to me.

      2. Grey checkering means "transparent". I think that's an image editor convention. To me, post-canvas-resize, it means there are layer issues. Maybe I learned this through trial and error. Use the Layers->Flatten Image and it'll fix the problem by removing the transparent background and filling it with the background color. I use layer merging and image flattening a lot, so I guess I'm aware of that sort of thing.

      3. Writing text isn't like putting letter-shaped paint onto the canvas. It's more like cutting words out of a magazine and sticking them on. Your new text is an object, shown in the Layers box. This lets you move and edit the words independent of the background image. To move, use the move tool (keeping the cursor over one of the letters). To edit, click on the words again with the Text tool (I think). If you want to get rid of the text, you can delete your text object or objects. If you want it to act like paint on the image, use Layers->Flatten Image again. The eraser will erase pixels on the currently-selected layer, which will only work for text if you've flattened it into the background.