Slashdot Mirror


GIMP Interface Proposals?

Anonymous Coward asks: "It would seem that naught but its developers themselves like the GIMP's UI. How would you like the GIMP to look? Reply with links to GIMPed (or Photoshopped, if you swing that way) screenshots. Individual features, the menu structure, or (preferably) default workspaces after you open up a blank new canvas." With the release of version 2.2 in the bag, 2.3 development should now be in full swing. What aspects of the interface do you think the GIMP team should make for the next release and for future relases down the line?

218 comments

  1. Proper MDI. by Refrozen · · Score: 4, Insightful

    All I'd want is a proper MDI, all the windows in a main container, I hate having them all free, loose, and can fall behind everything else and.... ugh.

    1. Re:Proper MDI. by Miffe · · Score: 5, Informative

      For X there is Xnest.
      And for windows there is Windows Gimp Deweirdifyer

    2. Re:Proper MDI. by Refrozen · · Score: 0

      That's fine, but it should be built in... or at least an install time option.

    3. Re:Proper MDI. by obi · · Score: 3, Insightful

      Ugh, no. That's one of the things on Windows I hate the most. These apps take the functionality over of the window manager, and you get several types of focus (the one in the app, the focused app, etc) - leading to confusion and clutter, and it makes it hard to use different apps together, which leads app to replicate alot of functionality in the application itself and become extremely bloated.

      However, it's true that there should be some kind of "grouping", something to connect panels to their app. A good example of this is on Mac, where the secondary panels are only visible if one of the primary windows of the app is focused.

      But that's a matter for the window manager - would be nice if that gets implemented in metacity or kwin or sawfish, or whatever floats your boat. But just because some functionality is missing in the WM, doesn't mean you should implement it in the wrong place - the applications.

      (As a side note, I'd like to see the same for tabbed windows a la firefox - it would be nice if an app could signal the WM to make tabs for itself, or even if one could attach different applications to each other)

    4. Re:Proper MDI. by JonyEpsilon · · Score: 1

      This is possibly the most useful thing I've ever learned from /. !

    5. Re:Proper MDI. by chaoaretasty · · Score: 1

      This is a very split opinion, why not add the feature and let users toggle it?

    6. Re:Proper MDI. by Anonymous Coward · · Score: 0

      If by 'proper', you mean, the Mac way, then yes. If by 'proper' you mean the Windows way, then god help you, you poor, poor, fool.

    7. Re:Proper MDI. by sw155kn1f3 · · Score: 1

      The problem with it is that window manager has no clue what tabs to create, in what order... The same with auto-hide and arrangements. So expect some applications behaving "strange".
      That one thing... Another is that at different platforms/WMs the same application will behave differently. That's not very good.
      And yes, different applications will need different schemes anyway, so every developer will code own workaround, depending what WM it's running on.
      Look, generalizations are good. But in real life it sometimes just doesn't work. Application knows better how to layout own windows than any window manager and can and ought to manage own windows in sensible manner. That's just sane usability requirement.
      Nice try.

      --
      - Arwen, I'm your father, Agent Smith.
      - Well, you're just Smith, but my father is Aerosmith!
    8. Re:Proper MDI. by drakaan · · Score: 1
      But that's a matter for the window manager - would be nice if that gets implemented in metacity or kwin or sawfish, or whatever floats your boat. But just because some functionality is missing in the WM, doesn't mean you should implement it in the wrong place - the applications.

      True, if you're talking about an application that only runs on (or is only primarily used on) Linux-ish systems. There, you're talking about a user base that picks and chooses window managers.

      One of the things about Windows that doesn't completely suck is that you can more or less expect an application to be presented in one particular way. Click on a shortcut and a window opens up with an application in it. GIMP (and numerous other GNU apps) follow a different design philosophy, but that doesn't mean that un-Windowsness is always a good thing, or that all of the people who use your app are going to like it.

      One of the things that put me off of using GIMP at first was the unfamiliar feel. I've used a few different apps for raster-based image munging and (probably because they were made for MS-based systems), they used a single mainwindow, etc. Lots of folks would just look, say "what the hell is this crap?" and call it quits (especially after their first and second bouts with the file dialog).

      I'd say making the open file dialog more usable and giving an MDI option would be a big boost to getting newbies who don't know (or care to know) about GNU/Linux to give GIMP a serious try.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    9. Re:Proper MDI. by John_Booty · · Score: 2, Interesting

      (As a side note, I'd like to see the same for tabbed windows a la firefox - it would be nice if an app could signal the WM to make tabs for itself, or even if one could attach different applications to each other)

      I really agree. Tabbed instances of application windows make a boatload of sense. Microsoft (and other desktops) have somewhat tackled this by grouping an application's windows in the taskbar (or "dock") or whatever your WM calls them) but this isn't very useful in my opinion. I'd like to see tabs implemented by the WM in some standard way within the application itself...

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    10. Re:Proper MDI. by Refrozen · · Score: 1

      Yeah! Visual Studio.net style! That would be great! Ditch the entire MDI, and steal the interface from VS.net!

    11. Re:Proper MDI. by SlickMcSly · · Score: 1

      Having programmed in Win32 and X I know it's perfectly possible to create multiple windows for a single application in Win32 with about the same amount of code as you would in X. The decision to use independent windows instead of a container is either because they didn't know how (typical for a new programmer), it wasn't implemented when the ui groundwork was laid, or they actually thought it was a good idea. Since I doubt it's the first case and wouldn't know about the second, it's prolly the third.

      I think what the devs originally had in mind was a kind of group focus where all the windows are independent but still change focus together (eg minimize/restore one, minimize/restore all). However, they may have since just gotten lazy or used to it.

      I still agree with everyone though, it's barely better than using the command line.

    12. Re:Proper MDI. by arkanes · · Score: 1

      Actually, the docking/tabbing in VS 2005 is the best layout mechanism I've ever seen. GIMP could do a lot worse than to mimic it.

    13. Re:Proper MDI. by yRabbit · · Score: 1

      That's what I would like to see as well. I don't like having ten GIMP things in my taskbar, I don't like having to raise or minimize all of them seperately.
      Other than that, I'm actually pretty comfortable with GIMP's UI. Though, actually.. I liked the file dialogue in before 2.2 more! (and for some reason the new one always likes to read my A: drive, the first time it is opened)
      I think the reason I liked it before 2.2 is because I could easily type into it and use tab completion, without having to click a + or such (and I don't even see anything for it in the "open" dialogue, but that's okay, I usually open a folder and drag what I want to edit into GIMP.)

    14. Re:Proper MDI. by ibbey · · Score: 1

      But that's a matter for the window manager - would be nice if that gets implemented in metacity or kwin or sawfish, or whatever floats your boat. But just because some functionality is missing in the WM, doesn't mean you should implement it in the wrong place - the applications.

      So are you saying that an application running under a typical window manager doesn't know when it has focus? I'm not a programmer, but it seems that as long as the application knows it is focused, it should be trivial to bring the other windows to the front, shouldn't it? This is a feauture that the Mac has had for most of it's existence... I find it flabbergasting that you are suggesting that X-Windows lacks this ability.

    15. Re:Proper MDI. by obi · · Score: 1
      The problem with it is that window manager has no clue what tabs to create, in what order... The same with auto-hide and arrangements. So expect some applications behaving "strange".
      Well, I'm not sure if it's that difficult. What firefox/epiphany does, is: "when opening a new tab, add it to the end of the tab list of the current window". Now, why do you think a WM couldn't do this?
      Another is that at different platforms/WMs the same application will behave differently. That's not very good.
      Application knows better how to layout own windows than any window manager and can and ought to manage own windows in sensible manner.
      Let me get this straight: it's not good that things are different on different platforms/WMs, so your solution is to implement it (possibly differently) in every app?
    16. Re:Proper MDI. by Anonymous Coward · · Score: 0

      Make them like Delphi (= 7): MDI w/o the containing window holding (and hiding) everything, and with a small "project manager" container window.

      Don't make it like Visual Studio/Visual Studio.Net.

    17. Re:Proper MDI. by Anonymous Coward · · Score: 0

      Ugh, no. That's one of the things on Windows I hate the most.

      Me, too. ;-)

    18. Re:Proper MDI. by obi · · Score: 1

      So, you're saying apps should all handle their own focus management, possibly in different ways, possibly broken or buggy in different ways.

      And if you don't like the focus management, and would like to change the focus policy, all you have to do is change all apps.

      So yes, what you suggest is possible, but that doesn't mean it's a good idea.

      At least with the choice of window manager comes the choice of focus policy, and you know that all apps will adhere to it.

    19. Re:Proper MDI. by ibbey · · Score: 1

      So, you're saying apps should all handle their own focus management,
      possibly in different ways, possibly broken or buggy in different ways.


      No, that's not what I'm suggesting. I agree with you that the OS (or window manager in the case of X Windows) should handle this. Apparently, however, they don't. Since that is the case, the developers seem to have three choices... Either put up with constant complaints from annoyed users, switch to an MDI-like interface, or, unfortunately, manage their non-file windows themselves.

      BTW, this obviously IS possible. I normally use Firefox, but I know that Konqueror has the ability to float it's toolbars. The floated toolbars don't show up in the taskbar, and they are automatically moved forward & back with the parent window. I thought that the problem with GIMP might be that I was running it under KDE, but switching over to Gnome, I see that the issues are the same there. Konq, also works the same was as it does under KDE-- the tolbars don't show up on the taskbar. Assuming Konq manages it's own windows, perhaps this implementation is less then ideal. But from the point of view of a user, I couldn't care less-- it works the way I want and expect.

      So, is the best way to handle the problem to do it in the app? No. In an ideal OS, the WM would handle this for you. But barring that, it would seem that the developers have no good choice but to do it themselves. The only other option-- not doing it & forcing the user to manage the windows manually-- only seems like a good option to the developers.

      Also, focus policy has nothing to do with the issue. Handled properly, the tool windows follow the file windows. If you have a "focus follows mouse" policy, pointing at the file window brings the file window, and the relevant tool windows, to the front. If you point at a tool window in an application that has more then one file open, the last accessed file would be brought to the front. Everything would be the same with a "focus on click" policy, except that you would have to click on the window. This is the way it works in virtually every other OS, and it is the way the user expects. I'm all for trying other paradigms for user interaction, but only when there is at least some user benefit to the proposed change. Changing simply because the developers have "moral" objections to the other option is silly.

    20. Re:Proper MDI. by hell_for_leather · · Score: 1

      i'll second that.

    21. Re:Proper MDI. by sw155kn1f3 · · Score: 1

      >> Let me get this straight: it's not good that things are different on different platforms/WMs, so your solution is to implement it (possibly differently) in every app?

      Of course not in every app. Heigher level primitives for tabs, mdi etc should reside in widget toolkit app uses (GTK+ in this case). That's how things are supposed to be in the real world. And implementing "tabs" is very straightforward and it'll be barely 200 lines of code with normal toolkits.
      And no, adding some "special and automatic" tabs into WM isn't a good idea. You already have it in the form of taskbar.

      --
      - Arwen, I'm your father, Agent Smith.
      - Well, you're just Smith, but my father is Aerosmith!
    22. Re:Proper MDI. by magefile · · Score: 1

      This is possibly the most useful thing I've ever learned from /. !

      You misspelled "only". (I kid because I love.)

  2. I'm not a GIMP developer by nocomment · · Score: 2, Interesting

    And I kinda like the GIMP UI. :-)

    --
    /* oops I accidentally made a comment, sorry */
    /* http://allyourbasearebelongto.us */
    1. Re:I'm not a GIMP developer by dn15 · · Score: 3, Interesting

      Same here. I don't see anything in particular wrong with it.

      On a semi-related note, it would be nice to see the Mac OS X version make some of its windows more like palettes that don't necessarily have a focused or unfocused state. As-is, clicking on a tool's icon actually takes two clicks. The first brings the window to the front, then the second selects it. Similarly, you needs to clicks to actually use it on the document. This is not a problem in Linux since the window focus model is typically configured in a way that allows the first click to select the tool even if the window does not have focus.

    2. Re:I'm not a GIMP developer by Anonymous Coward · · Score: 0

      man quartz-wm, look at the bottom of the manpage.

    3. Re:I'm not a GIMP developer by virid · · Score: 1

      I second this post.

      --
      "The world only exists in your eyes. You can make it as big or as small as you want." - F Scott Fitzgerald
    4. Re:I'm not a GIMP developer by jspoon · · Score: 2, Informative
      From the ReadMe on GIMP.app:

      If you are using Apple's X11 and find it annoying that you must click on a window once to bring it to focus and a second time to use a tool on it, open a terminal window and type: defaults write com.apple.x11 wm_ffm true This will enable "focus follows mouse". X11 must be restarted for the change to take effect.

      Don't know if that info is in with the Fink version or not but I imagine it would work exactly the same.

    5. Re:I'm not a GIMP developer by dn15 · · Score: 1

      Excellent advice. It worked like a charm. Thank you!

    6. Re:I'm not a GIMP developer by eraserewind · · Score: 1

      Informative, but why require a system level change to cover an application level shortcoming?

    7. Re:I'm not a GIMP developer by eurleif · · Score: 1

      Because system settings are best left as system settings. Even if it could, why should GIMP arbitrarily override the settings its user has defined?

    8. Re:I'm not a GIMP developer by dan_bethe · · Score: 1

      For those Mac users who don't want to use GIMP in X11, there is this! Aqua-native GIMP for MacOS.

  3. Wouldn't agree by justsomebody · · Score: 0

    I like Gimp just as it is. Do you need screenshot of it???

    I wouln't go back to PShop interface.

    --
    Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
    1. Re:Wouldn't agree by kuka · · Score: 1

      Exactly what problems did you have with the PS interface? I'm just curious, because I used both
      and found the Gimp UI inferior to the PS one.
      Some example:
      I dislike the separate resizeable main Gimp window which is a tool window itself. Tool windows/dialogs are unnecessarily large, they may not be docked, they could be hidden behind the image windows. Undo/redo requires 2 different button combinations, etc

    2. Re:Wouldn't agree by justsomebody · · Score: 1

      I don't know if you'll read but here's the answer:)

      I use 3x22" monitors (:Ok, I'm spoiled:). Photoshop fits on maybe 1 and 1/2 maybe at best. While Gimp works acros all monitors (talking about Linux version). That's why everybody uses 1x22" and 1x15" monitor for PS. More would be a waste. You whine about covering toolbar, I whine about covering pictures :)

      Personaly, I hate MDI approach. It sucks major. First time you'll be able to use some software across 3 monitors you'll know exactly why I hate PS interface and all the troubles that MDI brings.

      Second major bug are toolbar windows. Instead of implementing simple icon, Adobe had to put whole text for name (and even use additional waste space as this wouldn't be enough). And as such you can combine at most 3 toolwindows in one. Otherwise it would take too much space. (Yes, I know you can stack them on top, but what annoyance this is. Having 2GB of RAM , but still... pictures were redrawing always when I pulled down any toolwindow, Unusable. Yes pictures I work on are bigger than 150MB)

      In gimp my favourite layout is havint two full height toolbars. Left and Right. This is the only way to have layers full height and more visible on screen.

      Gimp bugs:
      The only thing that I used to hate was lack of global shortcuts. Before 2.2 version you had to select picture and then press shortcut, now this bug is GONE, Gimp is passing shortcuts to last selected picture.

      p.s. I just couldn't go back to Aplha channels as PS implements them (but first, let me admit I haven't tried 7 or CS). And yes, rotating brushes, roating brushes, rotating brushes

      p.p.s. I don't work on prepress. (if I would, then Gimp wouldn't suit my needs anyway) My job is mostly drawing (using wacom) for my personal pleasure and websites

      --
      Signature Pro version 1.13.2-3 release 83.5 beta3try7 after-breakfast edition
  4. Photoshop by timothv · · Score: 3, Interesting

    At best, it should look almost exactly like the Photoshop UI, with a few annoyances fixed. I don't have too many ideas but I'm sure the GIMP devs can compile Photoshop annoyances and outdo it.

    1. Re:Photoshop by Sentry21 · · Score: 0, Flamebait

      I concur on this part. Photoshop has been developed over the last 14 years to be the world's premiere image-editing program, by professionals for professionals. It has power, extensibility, and ease of use attached to its name, can open more image formats than I'm aware of, processes images surprisingly fast, is stable, can do batch jobs, etc.

      GIMP has all of this except for ease of use. The right-click menus are a pain (I expect right-click to give me a contextual menu, not the only menu), the toolbars-as-separate-windows idea is cumbersome, and the single-document interface is a pain and slows down my working time.

      If the GIMP wants a good interface, the parent has the right suggestion: make it look, work, and feel like Photoshop, minus inconsistancies/annoyances (I can't think of any, but people probably have some I haven't encountered). Copy it feature-for-feature, make it look-alike and work-alike, put menu items in the same-named menus, and then maybe, just maybe, the pros will be willing to switch.

      Then all Linux will need is an InDesign clone, a Final Cut Pro clone, and a few others, and professional graphics and video artists can start switching over.

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

      How the fuck is that a flamebait? the fucktards on /. apparently can't take any criticism of their "beloved" open source. Now if the parent were complaining entirely about Adobe/Jasc/Microsoft/any closed source developer, then that would've been modded +5 Informative/Insightful/Interesting. Talk about a bunch of fucking Hypocrites.

      Oh, that's right, if you can't fucking program, then you're too stupid to use a computer and should be taken out of the fucking gene pool.

      The parent post has it right, the GIMP interface is very hard to use, and not everyone is a fucking programmer. My suggestion is to use a configurable interface system that allows a user to change the interface via modules to make the GIMP operate similar to Paint Shop Pro or Photoshop, or if they prefer, just keep it with the default interface.

  5. survival of the gimpiest by Anonymous Coward · · Score: 2, Insightful

    Open it up... provide an API to the backend and allow anyone to code their own interface.

    1. Re:survival of the gimpiest by bersl2 · · Score: 1

      And include both a traditional GIMP UI and a more Photoshop-like UI.

    2. Re:survival of the gimpiest by Stevyn · · Score: 1

      well, it is open source so everything you need is already there, so I guess you're just saying to make it easier. Not a bad idea. If the gimp people focused on the algorithms and other designers could easily make their own front end, then I think gimp would progress a lot faster than it currently does.

    3. Re:survival of the gimpiest by Anonymous Coward · · Score: 0

      Yes! And they can call one Ggimp and one Pgimp, and then everbody can flamewar over it on Slashdot.

    4. Re:survival of the gimpiest by dr.badass · · Score: 4, Insightful

      well, it is open source so everything you need is already there

      If only that were true!

      other designers could easily make their own front end

      The trouble is that there are no designers. At best, there are programmers that know a little bit about how to make a UI not suck. This will only get you so far. The UI is typically an afterthought, and the most common suggestions for improving it is "themes" or "skins" or "window decorations" or "make it an option", none of which actually address the problem.

      --
      Don't become a regular here -- you will become retarded.
    5. Re:survival of the gimpiest by bay43270 · · Score: 2, Interesting

      The trouble is that there are no designers. At best, there are programmers that know a little bit about how to make a UI not suck. This will only get you so far. The UI is typically an afterthought, and the most common suggestions for improving it is "themes" or "skins" or "window decorations" or "make it an option", none of which actually address the problem.

      I agree completely. Even if there were designers working on this, their opinion would be taken as optional fluff. By the very nature of open source programming, the programmer has the last word. Programmers wouldn't take the word of a designer until the designer had proven to the programmer that his way is better. This is where commercial software has a significant advantage - in a good company, the UI people have pull, and can mandate changes. This isn't to say all (or even most) commercial companies do this, or that all open source software has a bad interface. But I think at this point, we should be happy with what we have: a stable, free program, with lots of options and a fairly decent interface... considering.

    6. Re:survival of the gimpiest by Eideewt · · Score: 1

      We could even have a little anticipatory flame war right now!

    7. Re:survival of the gimpiest by Anonymous Coward · · Score: 0

      from http://wiki.gimp.org/gimp/WhatsNew2

      Technical stuff

      *

      GIMP now can be compiled as a console application, with no dependence on Gtk.

    8. Re:survival of the gimpiest by LuSiDe · · Score: 1

      "make it an option", none of which actually address the problem.

      Frankly, i think the option between the current interface and a Photoshop-like / MDI interface would be Good. Although it would cost more time to maintain both interfaces. Eventually one might drop though, after some 'polls', feedback.

      --
      WE DON'T NEED NO BLOG CONTROL.
  6. What's the point? by Anonymous Coward · · Score: 5, Insightful

    Since day one, GIMP users have been complaining en masse about free-floating tool windows. And since day one, we have all been told "it's a feature not a bug". So why bother with even more feedback? It will only get ignored again.

    1. Re:What's the point? by JustAnOtherCodeSerf · · Score: 1

      You forgot....

      You can do it!, just not on all OS's (Windows)
      You don't contribute, so shut up.
      Write it yourself.
      It's a "feature".
      "Most" people like it that way.

      Which all boil down to basically... Fork Off.

      --
      -=sig=-
    2. Re:What's the point? by schumaml · · Score: 1

      The problem with suggestions of changing this is usually that the one who suggests it declares that the current interface sucks and demands it to be changed "now and forever".

      Coming to a mailing list or irc channel of a project with this attitude doesn't make you many friends. At least, you should listen to the regulars and accept why the UI is as it is, what tools are there to changed the behaviour (Xnest and Deweirdyfier were already mentioned).

      And about the ignoring - the developer's time is limited. And it is unlikely that the main developers will create a seperate UI for a signle one platform. Here's the chance for new developers (and that's the group the "Fix it yourself"s are directed at) to implement new ways for an UI. Of course, changes have to be reasonable - the 12345kB "Hey, I changed the whole UI" patch will be rejected, as will any big changes that should be done on the GTK+ level (and much UI stuff probably should be done or at least prepared there). Again, listen to the regulars.

      OpenSource Software is, at least partly, made by the people who create it for the people who create it. If you want it to be made (more) for you, consider becoming part of the people who create it - "create" isn't limited to "coding".

    3. Re:What's the point? by Anonymous Coward · · Score: 0

      The problem with suggestions of changing this is usually that the one who suggests it declares that the current interface sucks and demands it to be changed "now and forever".

      Perhaps that's the majority of the complaints the developers see. If I can describe it from a user's point of view:

      1. Install it.
      2. Find out that the interface sucks.
      3. Try and find the options to make it sane.
      4. Fail.
      5. Ask where the option is.
      6. Get told "it's a feature not a bug, you are wrong for wanting it this way, you just need to get used to it."
      7. Try to get used to it.
      8. Conclude after months or years that it still sucks.
      9. See everybody else asking for the same thing.
      10. Say, "hey, are you going to implement this or what?"
      11. Get told "it's a feature not a bug, you are wrong for wanting it this way, you just need to get used to it."
      12. Tell the developers "no, the interface really does suck, and people have been telling you for years."

      It's my belief that many, if not most, of the people you claim have a bad attitude have been through this whole cycle by now, and are on the last step. If you look at that step alone, yes, it appears somebody has a bad attitude. But you are ignoring the fact that the people saying this have tried to get used to it, and have tried to point out the problems diplomatically multiple times, only to be told point-blank "you are wrong."

      And about the ignoring - the developer's time is limited.

      As I said before, people have been complaining about this for years and years. Every time the GIMP is mentioned on Slashdot, there are multiple threads about how sucky the interface is. As far as I can tell, the general consensus outside of the developer mailing lists is "It's like photoshop, only with an interface that really sucks. I'll use it but I don't like it."

      If the developers pour all of their energy into writing multiple scripting interfaces (what, we're up to three now?) instead of the things everyone is clamouring for (not just a sane interface, but things like CMKY support), then how long before everyone loses faith in the GIMP? The GIMP seems to be stuck in a halfway point. It's good enough to make forking or starting a new project unattractive, but it's not good enough to stop people being unhappy that this is the best available.

      Of course, changes have to be reasonable - the 12345kB "Hey, I changed the whole UI" patch will be rejected, as will any big changes that should be done on the GTK+ level (and much UI stuff probably should be done or at least prepared there).

      But a change like this is big by its very nature. If you are saying that big patches will be kicked back, then what you are saying is that the GIMP won't ever get a better UI.

      If you want it to be made (more) for you, consider becoming part of the people who create it

      I don't have the time. If I had some special need that wasn't reflected in the community at large, I wouldn't complain so much. But, at the risk of sounding rude, open your fucking eyes. Loads of people are complaining left, right and centre. And for every complaint, there are a dozen more that simply don't use it or stop using it without bothering to say anything.

    4. Re:What's the point? by schumaml · · Score: 1

      In steps 5 and 6, you should have been told about Xnest and Deweirdyfier. And I haven't yet seen a user with a comment like "I use Deweirdifyier, and it has the following things I'd like to see improved", so your assumption might be wrong.

      Your remarks to the limited time... may I quote from your last paragraph? "I don't have the time."

      Your ranting about the scripting interfaces... well, they are an example for features that went in by the "someone needed it and made it happen" principle. Note that except two of the interfaces - Scheme and Python - these aren't maintained in the GIMP source tree. BTW, afaik there are at least 6 interfaces, though one is going to replace the current Scheme one and two are no longer maintained. The plug-in and extension mechanisms make this possible, and you surely don't want to forbid anyone creating plug-ins, do you?

      Aout the patches - if you'd change the UI with one large patch, you would do something wrong. GIMP is modular, so this can be changed one by one - which would be important, otherwise you could seriously delay the development of other features. Smaller patches are more easily reviewed, too.

      My fucking eyes are open, and I see people who don't like the current interface and people who do like it. As people rather complain about things they don't like, and don't care to write about things they like (mentioned in another comment in this thread), I tend to weigh those opinions with different scales.

      However, any changes to the UI have to consider the people who like the current interface. Comments concerning this are found in the bug tracking system at bugzilla.gnome.org, and anyone who is seriously interested in changing anything should read the relevant bug reports there and use the mailing list archives - and show that he has done so in any discussions he takes part in.

  7. This kinda reminds me of Blender by QuantumG · · Score: 4, Interesting

    The UI is non-intuitive, but once people use it they swear that it is better than every other 3d program available. Either Blender has the best UI in the world or it's just a tendancy of human beings to rationalise their decisions after they have invested in them significantly. Either way, Blender's complex non-intuitive UI has done a lot to build the Blender community. I believe the same is true of GIMP but to a slightly lesser extent. Why change anything?

    --
    How we know is more important than what we know.
    1. Re:This kinda reminds me of Blender by Goeland86 · · Score: 2, Interesting

      Well, Blender is kinda hard to learn, and counter-intuitive... However, I've heard alot of people saying that the Gimp is an Opensource Photoshop clone. While I don't think it is one, many people do, and expect to find the same UI in the Gimp that they'll have in Photoshop, or at least relatively similar. I personally think that as was mentionned in another post there should be a completely separate themeing set, where people can create their own designs, specify whether windows are independent or not. I like being able to open various windows on various virtual desktops, and it's a perfect tool for me, but for others it's less than helpful because they have to switch from one window to the other using alt-tab or clicking in the dock or taskbar. This is especially true on Windows, but also for KDE or Gnome users... I think that using something like Enlightenment's Edje library for themeing would be more than perfect to allow various themes for the Gimp, letting people choose how to open menus and whatnot, but unfortunately, Edje is still pre-alpha, and it would probably require a major re-write of the Gimp's code, which I doubt the devs are ready for.

      --
      ---- I am certain of only one thing : I know nothing else.
    2. Re:This kinda reminds me of Blender by Anonymous Coward · · Score: 0

      GIMP is non-intuative to an extent. For example, in pretty much every application there is, the Del key deletes the user's selection. It doesn't in the GIMP. I'm not sure it does anything. You have to use Ctrl+K instead.

    3. Re:This kinda reminds me of Blender by black+mariah · · Score: 0

      I've found that the overwhelming majority of people that actually like the Blender interface haven't used another 3d app in their entire life, or started out using Blender years ago and can't get used to other 3d apps. You can draw a parallel between Blender and BASIC. You start out using it, you're broken for life.

      It's not even a question of cost. Wings 3D has a MUCH better interface for modeling than Blender. I wish they'd work on integrating more than modeling, but that would probably slow it down to unbelieveable levels of sluggishness.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    4. Re:This kinda reminds me of Blender by QuantumG · · Score: 2, Interesting

      No. Wings 3D, although terribly cool, cannot do even 1/10th of what you can do with Blender. 3d studio MAX has probably the worst UI in the world, although it is intuitive on the service, it's really hard to get anything sensible done with it in less than 300 operations. That's why they have training courses for it. Blender on the other hand doesn't even try to be sensible. It's like the Amiga mentality: don't bother standardizing on anything cause everyone who uses an amiga is a zealot so they'll accept anything.

      --
      How we know is more important than what we know.
    5. Re:This kinda reminds me of Blender by black+mariah · · Score: 0

      I'll take this time to point out that I said Wings has a much better interface FOR MODELLING, and that I wished they would implement more tools (animation, real texturing, better rendering).

      3ds max's UI is one of the best among the pro-level 3d apps. People that complain it takes too long to get anything done have most likely not set up their quad menus right (with the tools they use most on their own menu), and not learned their hotkeys. It's similar to Lightwave in that respect. Without complete knowledge of the hotkeys you're pretty much screwed on productivity. Maya and Softimage don't seem to have that problem as much, for whatever reason.

      But don't ask me WTF is going on with Houdini's interface. I still haven't figured that one out.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    6. Re:This kinda reminds me of Blender by Unordained · · Score: 1

      I always found Caligari's TrueSpace to have a rather good GUI for its genre. It didn't take over your workspace, buttons were grouped in ways that make sense ... and it uses fairly standard OS GUI components so it doesn't look totally off-the-wall. I never got the hang of the 3d widgets though, the ones appearing -inside- the workspace as objects. It was an interesting idea, but ... something about having to rotate my view to get the tool I need seems a bit weird. Eh.

      As to users accepting just about anything -- I'm a programmer in the medical industry. From looking at the software we replace or use as examples (get some idea of what the users might want or need, since they're incapable of telling us themselves) ... they really will accept just about anything -- even love it! (I think the love part comes from attending vendor-sponsored workshops and seminars: data-entry ladies just fall in love with their vendors at those events. We need seminars, our data-entry ladies don't love us enough yet.) I've seen a lot of DOS programs (all?) that look better than what most users put up with in the medical industry. I mean really; is it so hard to align controls, use a decent (small) set of colors, standardize on one font (preferably the system one), make menus accessible, and while you're at it make the questions asked of the user be somewhat related to the underlying cardinality problems? It would probably be asking too much for standard window functions (like Ok/Cancel/Save/Undo/etc.) to be in a consistent spot, too ... and out of the question for reports to stop using fixed-width fonts across 80 columns, such that you can barely fit anything on a piece of paper at all ... And Matt, if you read this: no more "four-winds" button placement, k?

    7. Re:This kinda reminds me of Blender by QuantumG · · Score: 1

      Truespace really was intuitive for the simply actions, I actually managed to make some 3d graphics with Truespace and I can't draw for a damn.

      --
      How we know is more important than what we know.
    8. Re:This kinda reminds me of Blender by Eideewt · · Score: 1

      It sure is bizarre, but it does beat, say, 3ds Max in being simple, attractive, and easy to use. It's completely ineffable, but at least it's not ridiculously cluttered like 3ds Max is. I'll take steep learning curve over horrid design any day. All you need is an explanation for each thing you might want to do. I don't actually use either program often (I'm a POV-Ray type -- mmm... scripting), but I know what I kind of like (Blender) and what I really hate and complain about for weeks (Max).

    9. Re:This kinda reminds me of Blender by Whatchamacallit · · Score: 1

      Blender is really really nice. It's main design concept is to use two hands, one on a multi-button mouse or trackball and the other on the keyboard. The numeric keypad is used to change the view, all other major functions are keyboard letter key commands (usually just one key press).

      The Blender interface had a face lift recently to add pull down menus, collapsable toolbars, etc.

      The main reason for portability is the Blender GUI is completely cross platform. It's that grey Unix style layout that you see in other highend 3D packages and media environments. (Apples got a few media tools that look similar).

      These highend interfaces are not meant to be entirely intuitive nor to follow Apple or Windows GUI standards. They are meant to be powerhouses for professionals.

      The views in Blender are highly configurable so you can setup a single view with Top, Left, and 3D views plus a forth window for tools, etc.

      Having gone through tutorials and buying manuals, I find once I understand the GUI, it's really extremely productive. When you get comfortable with it, you can really fly along manipulating the environment with fantastic ease.

    10. Re:This kinda reminds me of Blender by Jacek+Poplawski · · Score: 1

      The UI is non-intuitive, but once people use it they swear that it is better than every other 3d program available.

      And what do you mean by intuitive? Is 3D Max intuitive? Maybe "intuitive" means "similiar to Max"?

      Blender reminds me Vim. Both applications have "different" UI, but both are usable, and both are very important, so what's the problem?

      And yes, floating windows in Gimp are dumb. I agree with "top rated" comment - if you want to convience testers that this is "feature" instead listen opinions and try to fix problems - don't count on good feedback.

  8. innovation by moosesocks · · Score: 4, Insightful

    As much as I'd like for the GIMP team to be innovative in their UI design, I believe that they will find that impossible, as the GMIP's feature-set has come to resemble that of Photoshop so closely that the two UIs will be VERY similar.

    Photoshop and Paint Shop Pro have very different UIs because they are conceptually different (that's not to say that PSP is any good. I'm not a fan). The GIMP and Photoshop were both conceptually similar -- in other words, by copying features from PS, the GIMP team has forced themselves to make their UI very similar to Photoshop. In other words, copying the PS GUI exactly will create the most efficent UI for the gimp. In my mind, this is a bad thing.

    But not all is lost. Here are my suggestions
    1) Implement a darn menu bar and clean up the menus. The right-click system sucks.
    2) Please handle pallettes like every other program does and NOT create an additional taskbar icon for every document, toolbar, and pallette.
    3) Implement a Slices tool like ImageReady has
    4) Rename the program. GIMP does not convey an image of a good, reliable program

    --
    -- If you try to fail and succeed, which have you done? - Uli's moose
    1. Re:innovation by DrMorris · · Score: 1

      1) Implement a darn menu bar and clean up the menus. The right-click system sucks.

      This one is already done.

      4) Rename the program. GIMP does not convey an image of a good, reliable program

      I don't see any advantages in renaming the program.

    2. Re:innovation by cyclop · · Score: 1

      GIMP does not convey an image of a good, reliable program

      Huh?And why PhotoShop does? What do you mean?

      --
      -- Patent no.123456: A way to personalize /. comments with a sig attached to the end.
    3. Re:innovation by Anonymous Coward · · Score: 1, Insightful

      I don't see any advantages in renaming the program.

      Do you really mean that, or do you mean it will make no difference to you personally?

    4. Re:innovation by Anonymous Coward · · Score: 3, Informative
      Every single time I hear "The GIMP", this is what comes to mind.

      A terrible, terrible, terrible name for a program. Almost as bad as "OmniGraffle" (which remindes me of 'scrapple', 'scapie', and other horrible things).

    5. Re:innovation by nathanh · · Score: 3, Insightful
      But not all is lost. Here are my suggestions 1) Implement a darn menu bar and clean up the menus. The right-click system sucks.

      Perhaps you should first use the GIMP before offering suggestions. All image windows have their own menu bar since v2.x. Right-clicking to access the menu is entirely optional.

    6. Re:innovation by D'Sphitz · · Score: 2, Funny

      It always brings a picture of Zed from Pulp Fiction to mind saying "bring out the gimp"

    7. Re:innovation by Bloater · · Score: 0

      1) check

      2) partial check - palettes and tools can be grouped into a single window - images should be separated into tasks but most certainly *not* according to which OS process is handling input and output for that window. Multiple desktops helps though it needs some integration.

      3) dunno

      4) agree wholheartedly. make it something that does not include any indication of what OS/desktop/GUI toolkit it uses or was originally designed to be used with. (I hate Kthis, Gthat, and TuxTheOther).

    8. Re:innovation by Rysc · · Score: 1

      I'll bite: It makes a difference to me, personally. I would personally, deeply object to changing the name.

      --
      I want my Cowboyneal
    9. Re:innovation by dr.badass · · Score: 1

      Huh?And why PhotoShop does? What do you mean?

      Well, for one, Photoshop actually gives some indication as to what kind of program it is. GIMP does not. Secondly, at this point, it doesn't matter much what Photoshop is called because everyone to whom it really matters already knows what it is. Photoshop is Photoshop and has been Photoshop since it was released in 1990.

      --
      Don't become a regular here -- you will become retarded.
    10. Re:innovation by thephotoman · · Score: 1

      The GNU Image Manipulation Program doesn't tell you exactly what the program is for? Come on! PSP has nothing to do with painting, and Photoshop is a really broad name (especially for a program that can't make animated .gifs on its own).

      The name is good. Not to mention fun to say.

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
    11. Re:innovation by thephotoman · · Score: 1

      Er...it's the GIMP because GNU made it, not because it uses the GTK+ toolkit (in fact, GTK+ is named for the GIMP, not the other way around) or Gnome (completely unrelated name, except again to show that GNU made it).

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
    12. Re:innovation by thebagel · · Score: 1

      C'mon! That's the most pathetic thing I've ever heard! When you're describing it to Mom, or Joe User, do you say "The GNU Image Manipulation Program?" No, you say "GIMP." And when you just decide to start talking about it to somebody, you say "GIMP." It gives NO IDEA what the program does! Acronyms are BAD, BAD, BAD ideas for programs that you want people to use.

    13. Re:innovation by some+guy+I+know · · Score: 1
      The GNU Image Manipulation Program doesn't tell you exactly what the program is for?
      Of course!
      It's a program for the manipulation of images of GNUs.
      --
      Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
    14. Re:innovation by cyclop · · Score: 1

      This is what comes to your mind. To me Gimp reminds nothing else than the nice Wilbur icon.

      (By the way, my ex-girlfriend absolutely loved the Gimp name and the association with the icon. She said it looked very nice and friendly)

      Anyway here's what the Merriam-Webster says about the word "gimp":

      an ornamental flat braid or round cord used as a trimming

      -what's so terrible in this?

      (Disclaimer: I don't like the Gimp that much, I think its interface is quite terrible etc. But I always loved its name.)

      --
      -- Patent no.123456: A way to personalize /. comments with a sig attached to the end.
    15. Re:innovation by dr.badass · · Score: 1

      The GNU Image Manipulation Program doesn't tell you exactly what the program is for?

      I didn't say that. I said that "GIMP" tells me nothing about the program, except perhaps that it's creators decided to burden it with an acronym for a name, which itself contains a meaningless recursive acronym.

      Now, acronyms aren't strictly bad. It's much easier to say NASA than National Aeronautics and Space Administration. But one reason why that works is that "nasa" is not, by itself a word (in English anyway). GIMP wouldn't be quite so bad if not for the fact that "gimp" is a word, and a moderately offensive slang one at that.

      PSP has nothing to do with painting

      So should we stop calling the "brush" tool a brush because you can't actually hold it? It's a metaphor, a useful one that's been around for a very long time.

      You should also see my second point above, that it doesn't matter what Photoshop is called, because "everybody" knows what it is. GIMP has not reached that level outside of the geek world, and will undoubtedly have a harder time doing so with it's current name.

      Photoshop is a really broad name (especially for a program that can't make animated .gifs on its own)

      You're firstly ignoring the hojillions of things that Photoshop can do that GIMP cannot, and secondly, why on earth would you want to? I'm just taking it on faith that Photoshop can't do animated GIFs, as I've never even tried.

      More importantly, you're ignoring the fact that GIMP can't open or save GIF at all on its own.

      --
      Don't become a regular here -- you will become retarded.
    16. Re:innovation by Bloater · · Score: 1

      > it's the GIMP because GNU made it

      Yeah, that too.

    17. Re:innovation by Anonymous Coward · · Score: 0

      Why?

    18. Re:innovation by Anonymous Coward · · Score: 1

      Shame that the majority of people associate the term with definition #3.

      What's so hard to understand that the name GIMP, associated by the majority of people to mean cripple (or that brings to mind a scene from Pulp Fiction) might be a bad name to use? Goodie, you don't associate the name with anything but the icon, but is it so hard to realize that you are likely in a minority?

    19. Re:innovation by thephotoman · · Score: 1

      Actually, for animated .gifs, they include ImageReady, which is bundled with PS for that purpose.

      --
      Haec merda tauri est. Ceterum censeo Carthaginem esse delendam.
    20. Re:innovation by Anonymous Coward · · Score: 0

      All image windows have their own menu bar since v2.x.

      And how is that an improvement? Look at Photoshop on the Mac: it has one menu bar, which is always in the same place. The same is true of Photoshop on Windows, though the reason is different (MDI as opposed to standard MacOS behaviour). Therefore, in both cases, you can always access the menus conveniently.

      In GIMP, the menu bar is always in a different place on the screen, so it takes longer to work out where to move your mouse. This gives the (unjust) impression of clunkiness.

      So the people who didn't like right-clicking still don't like it, while the people who did like right-clicking still use that instead. A perfect example of OSS developers implementing their idea of what users want and getting it wrong, instead of actually listening to the users...

    21. Re:innovation by Ace+Rimmer · · Score: 1

      Actually most non-native speakers don't consider 'gimp' as a word to be something odd. They mostly know it as a name of a program and the meaning you mention is not known to them (becouse there is lots of more important words to learn first).

      You also don't care about a foreign names of programs, you just get used to it ;).

      --

      :wq

  9. Text by Chapium · · Score: 3, Interesting

    I can't comment specifically on it, however the text interface and how you deal with text in gimp really needs to be worked on. Moving and manipulating text on that thing is simply confusing and frustrating

  10. Have you actually used GIMP 2.2? by leonbrooks · · Score: 3, Informative

    You can tack together the free-floating tool windows and make them one if you like. Admittedly, this should be one of the first startup tips and isn't.

    So yes, they did respond to that particular feedback, even if you didn't find out about it yet.

    It's also relatively trivial in most WMs to make those floating windows always-on-toppish like the PS ones (only more flexible).

    It could also be stated with much fairness that PhotoShop users form a disproportionate population of those complaining about same. And that if you don't like it, you're at liberty create a fork or a parallel patch set to implement the windows however you like them. Before anyone OMFGs me, compare the amount of effort involved in doing that with the amount of effort involved in creating the whole GIMP in the first place, and remember that with PS it's pretty close to impossible to do anything of this nature.

    BTW, my sister-in-law uses The GIMP heavily, and swears by the floating windows and the tearoff menus.

    --
    Got time? Spend some of it coding or testing
    1. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 1, Insightful

      You can tack together the free-floating tool windows and make them one if you like.

      Yes I have, and that has been possible since 2.0, hasn't it? It doesn't solve the problem, because that window is still free-floating. Put the damn toolbox inside the application window already goddamnit.

      It's also relatively trivial in most WMs to make those floating windows always-on-toppish like the PS ones (only more flexible).

      I do that too. It's still a pain, because the image window knows nothing about this, and so it can't compensate for the toolbox obscuring stuff.

      It could also be stated with much fairness that PhotoShop users form a disproportionate population of those complaining about same.

      Perhaps. I haven't used Photoshop extensively, and I don't see why "has used Photoshop" should disqualify somebody from having a valid opinion about the GIMP's UI.

      BTW, my sister-in-law uses The GIMP heavily, and swears by the floating windows and the tearoff menus.

      Some people do. I wouldn't recommend taking the option for doing so away, but it shouldn't be the default and it definitely shouldn't be the only option.

    2. Re:Have you actually used GIMP 2.2? by mini+me · · Score: 1

      Put the damn toolbox inside the application window already goddamnit.
      Not even Photoshop uses MDI on UNIX. Why would the GIMP want to?

    3. Re:Have you actually used GIMP 2.2? by dr.badass · · Score: 4, Insightful

      It could also be stated with much fairness that PhotoShop users form a disproportionate population of those complaining about same.

      Could it be that Photoshop users (current, potential, or former) are probably the biggest single group that might be drawn to GIMP? I think that if you're building a tool with an implicit goal of having all of the same capabilities of Photoshop, it might be nice if said tool would act something like it.

      --
      Don't become a regular here -- you will become retarded.
    4. Re:Have you actually used GIMP 2.2? by drakaan · · Score: 1

      To one-up Photoshop?

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    5. Re:Have you actually used GIMP 2.2? by Sentry21 · · Score: 4, Insightful

      It could also be stated with much fairness that PhotoShop users form a disproportionate population of those complaining about same. And that if you don't like it, you're at liberty create a fork or a parallel patch set to implement the windows however you like them.

      So essentially, while everyone that swears by the GIMP says I can use it instead of Photoshop, the instant Photoshop users say 'well but this is a pain in the ass' you say 'too bad, fix it yourself'.

      Fantastic attitude there. Open-source won't win the hearts or minds of professionals if the professionals don't like the tools and aren't provided a fix for it. If given a choice between fixing all that I've found wrong with the GIMP or sticking with Photoshop, my historical choice remails: the GIMP can take a flying leap.

      You can't tell professionals to use your software and then tell them you won't fix what they don't like about it. Graphic artists (myself included) will pay $800 for a Photoshop license because Photoshop already works the way they need it to work. Why should we switch if the bugs aren't going to be fixed?

    6. Re:Have you actually used GIMP 2.2? by ibbey · · Score: 2, Insightful

      It's also relatively trivial in most WMs to make those floating windows always-on-toppish like the PS ones (only more flexible).

      Always on top is not equivalent or remotely more flexible then traditional tool windows. The non-file windows should ONLY be active if a file window is, and then they should automatically activated. Always on top means just that-- The windows are ALWAYS on top. Since modern operating systems allow more then one application to be open at a time, there may be times when I don't want them on top. And, yes, I can move my GIMP windows to a seperate desktop, but that's not an acceptable answer. Any application that requires me to change my work style to overcome it's shortcomings is badly designed. This should be an easy thing to fix, and I have yet to hear even a single benefit to the current design. If there is one, I would be happy to hear it.

    7. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 0

      it's shortcomings

      "its".

    8. Re:Have you actually used GIMP 2.2? by BrokenHalo · · Score: 1
      You can't tell professionals to use your software and then tell them you won't fix what they don't like about it.

      And when did the Photoshop developers last embrace the criticisms of users with open arms? I didn't think so.

      Graphic artists (myself included) will pay $800 for a Photoshop license because Photoshop already works the way they need it to work.

      Read: I'm used to using Photoshop now, so that's why I paid $800 for a licence.

      I'm not saying Photoshop sucks, or doesn't suit your purposes. What I am saying is that it is worth learning to use any tool properly, even if you get it free, gratis and for nothing.

    9. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 0

      And when did the Photoshop developers last embrace the criticisms of users with open arms? I didn't think so.

      So in other words "Adobe don't listen to their users, so the GIMP developers shouldn't either"? That's a really mature attitude.

      Photoshop is the defacto standard. Adobe don't need to make any major changes to their interface, because all the books teach Photoshop, all the courses teach Photoshop, and all the professional graphic designers know how to use Photoshop.

      Yeah, it sucks to have a double standard, but it's there. The GIMP developers need to do more to provide the same value to users. Just whining that something with an already acceptable interface isn't changing much is a case of sticking your head in the sand.

      What I am saying is that it is worth learning to use any tool properly, even if you get it free, gratis and for nothing.

      Only if your time is worth nothing, and even if that were the case, it doesn't mean that another type of interface isn't better.

    10. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 0

      Not even Photoshop uses MDI on UNIX. Why would the GIMP want to?

      Even Photoshop uses MDI on Windows. Why doesn't the GIMP?

    11. Re:Have you actually used GIMP 2.2? by CptnQuixar · · Score: 1

      I gave GIMP several months to convince me. Then I went and paid for a full version of PS. GIMP needs more work. It is nowhere near a clean and stable version I would rely on in my design work. When it starts to feel as polished as Firefox, then it will have a chance. I know what it takes to learn software. The GIMP didn't even offer me incentive to learn it. I would use it for image resizing because I had no other alternative at the time, but actual photo/design work? I shudder to recall it. What they have so far is a great advance for open source, but it feels like 0.7 not 2.0.

    12. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 0

      I demand that the GIMP amend its user interface to include hot naked chicks with strong forearms to massage my back while I work.

      I'm a professional, this is what I need, and I'm willing to pay $800 for it. If the Gimp wants to be accepted by professionals, you just have to accept the market reality and implement the hot naked chicks. Dockable ones.

    13. Re:Have you actually used GIMP 2.2? by Anonymous Coward · · Score: 0

      So the GIMP should just become an open source Photoshop clone? Is there not something implicity wrong with that? What is the point of this if every piece of OSS is just a clone of something closed source? Where is the innovation? Development is not supposed to be paint-by-numbers.

    14. Re:Have you actually used GIMP 2.2? by dr.badass · · Score: 1

      Where is the innovation?

      I don't know. Where is it? Is GIMP innovative because it doesn't behave like Photoshop? I'm sure there are arguments for GIMP's interface, but I promise you, "we do it this way because Photoshop doesn't" is not one of them.

      So the GIMP should just become an open source Photoshop clone?

      It already is, basically. I'm merely suggesting that it act more like it, and that doing so would be a good thing for GIMP.

      --
      Don't become a regular here -- you will become retarded.
  11. As It is Now by Unknown+Lamer · · Score: 1

    There's nothing to change. It's fine as it is.

    Sorry, but MDI interfaces are dumb. No one bitches about how Photoshop on the Mac has a very similar UI. GIMP 2.x has menubars on the image windows now (unless you turn them off, as I have) so no one can complain about having to right-click being non-intuitive.

    The menu structure could maybe use a bit of a reorganization, but the interface has no major flaws.

    --

    HAL 7000, fewer features than the HAL 9000, but just as homicidal!
    1. Re:As It is Now by kent_eh · · Score: 1

      There's nothing to change. It's fine as it is.

      < lameness> me too < / lameness >

      Seriously, I fail to see why "everybody" keeps saying The Gimp's interface is ugly, or non-intuitive, or simply bad.
      Please quantify "bad", 'cause I just don't see it.

      --

      ---
      "I can't complain, but sometimes still do..." Joe Walsh
    2. Re:As It is Now by shaitand · · Score: 1

      unique = bad when talking about a software interface and the gimp interface is unique.

      Unique is bad because every piece which is unique is additional learning curve and time required to get into the app.

      Considering what gimp is, this interface should be a sellout conformist look that is something my grandmother will find similar to every other program she's ever used.

      Translation, gimp should clone the Photoshop UI.

    3. Re:As It is Now by peragrin · · Score: 1

      in early Gimp version's right clicking for every menu item really sucked.

      with the new menu system my only complaint is that every window is a task under "Windows" haven't installed it yet for my Mac yet as I have a copy of Photoshop of OS X.

      One point about the OS X display for photoshop. If you click on the desktop the only window that stays visible is the image window all the tool bars hide. They come back when you click on the image(or the photoshop dock icon).

      Whether the gimp does something similar I don't know. If I get bored I might test it out.

      --
      i thought once I was found, but it was only a dream.
    4. Re:As It is Now by mini+me · · Score: 1

      No one bitches about how Photoshop on the Mac has a very similar UI.

      No one bitches about how Photoshop on UNIX has almost the exact same UI.

    5. Re:As It is Now by black+mariah · · Score: 0
      Since some idiot might mod this up, let me quote the site, with relevant passages in bold:
      Caption: Adobe Photoshop 3.0.1 - nekonoko (nekonoko)
      So you're using a 5 MAJOR revision old example running on obsolete hardware to prove a point about software programmed almost TEN FUCKING YEARS LATER. You're right, nobody complains about Photoshop on UNIX having a similar UI... because NOBODY USES IT. Those that do are using it because of either the inherent geek factor of using old software on old systems, or they're hardcore SGI weirdos that can't deal with the face that Indy's are dead.
      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    6. Re:As It is Now by Anonymous Coward · · Score: 0

      "gimp should clone the Photoshop UI." Izzint that unlegil and ill ethickle?

    7. Re:As It is Now by shaitand · · Score: 1

      I should hope not, the entire point of my post is that there is NOTHING unique about the photoshop UI. It's a sellout and conformist piece of work that emulates other apps.

    8. Re:As It is Now by iantri · · Score: 1
      But it WORKS on the Mac -- in the application switcher-menu-thingy (what is it called, anyway?) there is ONE entry for each application -- select Photoshop and ALL of the Photoshop windows surface to the top.

      If you have multiple windows on-screen at once and you click on a different one, the Photoshop palettes disappear until you click on the main Photoshop window again.

      Under Windows/Linux, in the GIMP each palette is treated as a seperate window. They don't all stay on the same plane. This sucks bigtime. It's probably why under Windows Photoshop's palettes are contained within a massive Photoshop window.

    9. Re:As It is Now by Unknown+Lamer · · Score: 1

      I'm using WindowMaker and all of the GIMP windows have one icon. It's called SharedAppIcon mode. It's the default in newer version of WindowMaker.

      When I click on the GIMP AppIcon all of the GIMP windows come to the front. When I alt-tab or manually click on a window only that window comes to the front. NetWM has (IIRC) a hint for specifying if the window is a floating pallet type of window. If GIMP isn't using it now all it has to do is set the hint for its windows (if GDK has support for a compatible hint; if not it should be added and wouldn't be too much work).

      Then we can blame the window managers :)

      --

      HAL 7000, fewer features than the HAL 9000, but just as homicidal!
  12. No worries, just write one by leonbrooks · · Score: 1

    Call it "PhotoShop Masque for GIMP".

    Yes, I am serious. PS users in transition would just love it. And you'll die of old age waiting for a GIMP personality for PS.

    --
    Got time? Spend some of it coding or testing
    1. Re:No worries, just write one by Dysan2k · · Score: 1

      I completely agree. I'd also like to see them replicate the functions/filters available on the layers style buttons. One reason I tend to use PS more than GIMP is I can't get proper bordering to work under GIMP (Yes, I know it's under Script-Fu->Decor->Bevel.) Script-fu seems to lack that nice Preview option, which really turns me off when I'm doing serious work.

      I always state "replicate, then improve" when developing UI's. Take what works and make it better. Having a few themes/masques for GIMP would help in this respect, but don't forget the functional pieces of PS as well which make it so darn nifty.

      --
      -What have you contributed lately?
  13. Naught but developers? by JanneM · · Score: 2, Insightful

    This is simply not true. It's the same old effect that only those who really dislike a feature have the motivation to speak out about it, while those who have no problems with it have better things to do than to post about how they haven't had any problems with it today either.

    Never, _ever_ judge something like this simply based on volume of posts - and the same goes for letter feedback to media and politicians, as well, of course.

    I like the Gimp UI. And you can snap toghether or pull apart the windows in whatever combinations you want, so I don't see why people are still complaining about "free-floating" windows.

    --
    Trust the Computer. The Computer is your friend.
    1. Re:Naught but developers? by Eric+Pierce · · Score: 1

      > It's the same old effect that only those who really dislike a feature have the motivation to speak out about it, while those who have no problems with it have better things to do

      Ditto. I had issues with Gimp's UI back in the 1.x days, but usuabliity really has been a main focus on the 2.0 and 2.2 series. I'm all about keyboard shortcuts, and the improvements in this area have been outstanding (ex. extreme toolbar configurability, way fewer pop-ups, global keyboard shortcuts to name a few). I have no complaints.

      And for power users, you can even wittle down to only one extraneous window like I did: screen

      Just one less window to alt-tab between.

      Keep up the great work, Gimp devs!

    2. Re:Naught but developers? by Anonymous Coward · · Score: 0

      Quality of arguments, not quantity.

      Although with politicians, its all about quantity, because the majority wins...

  14. Simplify, and change the name. by Anonymous Coward · · Score: 3, Insightful

    The best thing they can do is simplify, simplify, simplify. Get rid of all those confusing filters or figure out how to combine them into one.

    Figure out a clean way to handle "floating layers" I never understood that. Photoshop makes the most sense.

    And PLEASE change the name. GIMP is an unprofessional name.

    1. Re:Simplify, and change the name. by Anonymous Coward · · Score: 0
      GIMP is an unprofessional name.
      What is this supposed to mean?
    2. Re:Simplify, and change the name. by Anonymous Coward · · Score: 0

      Posting as an AC is also unprofessional.

      Your friend,
      A fellow unprofessional

  15. Right-click does *not* suck by leonbrooks · · Score: 2, Interesting

    I miss it a fair bit when using PS.

    Have you used GIMP 2.2 (or even a late 2.0)? They have menus on every image window. Purists will complain that it's cluttered, but I find it very handy to have a choice of right-clicking if you happen to be a long way from the menu bar, or clicking on the menu bar if it's not a function you use often (hunt and peck made easier) or the bar happens to be nearest.

    --
    Got time? Spend some of it coding or testing
  16. Screenshot by Anonymous Coward · · Score: 0

    I think the GIMP would be a lot better if it looked like this: GIMP.

  17. I've got a little list! by leonbrooks · · Score: 4, Interesting
    • Add the Free/FixedAspect/FixedSize options from the Rectangular Select tool into the Crop tool.
    • Add a "macro recorder" to make writing Script-Fu easier
    • Add a simple "debug mode" to trace Script-Fu execution and/or hand off to the Script-Fu Console from the invokation dialog box
    • Add a de-red-eye tool that's a bit more intelligent, specifically
      • that identifies round or ovoid red-eyes rather than anything red
      • that uses soft edges rather than doing scalpel-like total excision
    • build a Script-Fu to do this either straight from the camera or with all of the layers in a designated image.
    There's lots more, that's just what's on the tip of my mind right now.
    --
    Got time? Spend some of it coding or testing
  18. Just as it is by metaphor · · Score: 5, Insightful

    Well I for one think The GIMP's UI is fine just how it is. Then again, I learned its UI when I was 13 or so, around the time I got addicted to sloppy/strict mouseover focus. Being able to point at a window and save its document by just striking Control-S is very efficient.

    I thought GIMP was weird at first (I was a Photoshop 2.x user) but I rapidly came to appreciate its advantages. Basically, I love it because it's efficient and lightweight. If I want to do something to an image, I right-click the image. Simple, right? In Photoshop I have to hunt under some menu and I have to care about which image is in the foreground. And of course, in both, I can just use key accelerators -- in GIMP, even assign my own -- to speed things up.

    You can't master GIMP in a day, and you sure as hell can't master Photoshop in a day either. Most of the complaining I hear is Photoshop users pissy about having to think a little differently to use GIMP. Maybe you should write a "tricks of the UI" tutorial for the unadventurous...?

    Now if I were directing the GIMP project, I'd say:

    Never adopt MDI. Well, okay, you can, just make it optional. There are a lot of Windows users who would love it, but a lot of current users who would dump GIMP in a second if it were mandatory.

    Please rip off Photoshop's styles palette. It's one of the main reasons I use Photoshop primarily these days.

    Please add serious ICC profile support wherever you can in the image workflow. Even if you don't support CMYK, good color support would rock, and it would make professionals take GIMP more seriously. Bonus points: add a calibrator like Adobe Gamma/Colorsync/Supercal.

    Yeah... I think that's about all for now. Watch everyone disagree :)

    --

    --
    Keep NOSPAM to reply
    1. Re:Just as it is by Johnathon_Dough · · Score: 1
      You can't master GIMP in a day, and you sure as hell can't master Photoshop in a day either. Most of the complaining I hear is Photoshop users pissy about having to think a little differently to use GIMP.

      I have never actually complained about the gimp, I have only tried to use it once, so I am definitely not in the know about the program. However, I am a regualr photoshop user. I can not take the GIMP seriously because I do not have a reason to. I know photoshop inside and out, I know more than the interface. I know what will cause it to crawl, I know what is most likely to make it crash (on my machine). I know where it falls down on the job from lack of a certain feature. Most importantly (to me) I know how long something will take me to do in Photoshop. All of that is worth the couple hundred bucks it costs me to upgrade every 18 months or so. Especially considering that the upgrade is usually about the same as 2 hours work.

      Having been using photoshop for about 8 years professionally, I figure it will take me 4-8 to gain this competance with GIMP. Not worth it(to me).Now, on the other hand, if you are just starting out, by all means, learn the GIMP, I am sure it is a viable application for what it does. And really, the UI. Who cares, does it work?

      Please add serious ICC profile support wherever you can in the image workflow.

      For ICC to work properly it would have to be included in every step of the workflow. Otherwise, you are just making up numbers at some point.

      Even if you don't support CMYK, good color support would rock, and it would make professionals take GIMP more seriously.

      Prefessional Web developers and film/tv people maybe. However, this is the killer feature for the print world. You can not have an application that is "good enough", oh except for that last bit where we get a file that can not be used with ink on paper.

      --
      If you are one in a million, then there are six thousand people who are just like you.
    2. Re:Just as it is by magefile · · Score: 1

      It took me 30 seconds to figure out how to change an image's resolution in PS, having never touched it before, and 2 weeks to get to the point where I could make humorous spoof software boxes (and this from a non-artist). I've tried GIMP many times, and it's always been painful.

    3. Re:Just as it is by arose · · Score: 1

      2 weeks for what should do >=2 days by RTFM?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    4. Re:Just as it is by arose · · Score: 1

      That should be two or less not two or more.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    5. Re:Just as it is by magefile · · Score: 1

      Given that I have had no exposure to PS, nor am an artist, and that I had very little time to spend on it each day, 2 weeks was expected. The boxes weren't the only thing I did.

  19. focus by danboy · · Score: 2, Insightful

    I would like to see the document window keep focus, the only problem i've had with the interface is when i forget to click on the document window after selecting a different tool.

    of course i don't know how easy this is, and it hasn't stopped me from using the gimp as my primary raster program.. so all in all keep up the good work.

    1. Re:focus by ScriptGuru · · Score: 1

      I think, in 2.2 at the latest, key events in the docks are passed back to the active image.

      --
      Yet another signature that refers to itself. The irony and humor is dead.
  20. Oh, and... by leonbrooks · · Score: 1

    ...put a text-box on the File Open dialog where you can type to choose a file (e.g. hidden files/directories) or give the navigator hints.

    No, I'm not talking about the separate Location box which Ctrl-L brings up (although that is handy for pasting URLs from other programs), I'm talking about a typing target integrated with the existing panel.

    --
    Got time? Spend some of it coding or testing
    1. Re:Oh, and... by arkanes · · Score: 1

      You'll never win. After years of taking well-deserved flack from everyone for the mind-blowing lameness of the file selector, the great minds of the Gtk project sat down and came up with what you're looking at. Yep, thats right, after years of being repeatedly shown what a crappy file selector was, this was what they decided was perfect. Cretins.

    2. Re:Oh, and... by Anonymous Coward · · Score: 0

      Seriously, I don't understand why OSS developers can't do things like everyone else on the usability side at least. If you want to bloat your apps with all kinds of perfect, "clean" coding, fine. At least make the apps nice to work with. Why the hell do I have to make bookmarks so I can easily access the same directory multiple times from within Gimp? Wouldn't it make sense for the app's file selector to start at your home directory when opened for the first time, then remember the last directory opened for future file selections? Seems like I had the same trouble with Openoffice, but at least it had the sense to start me off at my home directory every time instead of the directory of the program binary.

      I would donate to a cause that would fix the stupid interfaces of OSS via patches, among other things. Hint for developers: if people want file selectors that make sense, give the file selectors to them. If people want a Photoshop-like interface, give it to them! You can include both interfaces if you want! If people want the dumbass name changed, change it already! The name couldn't be tied in too closely, could it? It's almost like the developers don't want people to use their software so their geek club doesn't have to accept new members who might rock the boat.

      I know there are plenty of IT project managers out there that could help fix some of the dumb OSS mistakes happening right now, but when it comes down to it, the stubborn programmers still want their geek club to be intact and everyone ends up losing. They may claim that they welcome suggestions, but they will fight anything that isn't purely technical because they fear that outside influence will end up hurting the technical side. Valid to some extent, but when the project's user base suffers, you fix that problem no matter what the technical cost. Err, I forgot...it's open source so people can just change everything themselves. Silly me, I didn't realize that we needed to branch projects to give them a semblance of usability. These people just don't know what battles to fight. I think we've all worked with people like this, and we usually end up letting them have their way because it's a pain in the ass to argue every little point. This doesn't help to ship a good product, though. The vast majority of USERS think the Gimp name is stupid. When even the average /. reader can look past their usual advocacy-at-any-cost stance and realize that the name is, indeed, moronic, there's a problem.

      I will leave you with a link to a recent Gimp bug report regarding the name:

      http://bugzilla.gnome.org/show_bug.cgi?id=160890
  21. Here's my vote. by Ruis · · Score: 2, Funny

    These guys seem to have a pretty nice gui for a graphic editing program.

    1. Re:Here's my vote. by Bill+Kendrick · · Score: 1

      Heheh. Thanks for the vote of confidence. ;)

  22. Slicing tool by leonbrooks · · Score: 1

    2.2 has Guillotine right there in the menus (Image, Transform Guillotine).

    What it lacks is a way to tie image sections to one another to give an effect like ROWSPAN and COLSPAN from HTML. As things stand, you have to manually tack the appropriate image pieces back together again after the guillotine. If there were a simple Merge Pieces tool to do this, it would suffice, but I would be greatly pleased if you could mark sections of a Guide line (between intersecting Guides) and indicate that you didn't want the pieces either side of it separated.

    --
    Got time? Spend some of it coding or testing
  23. I know it's not directly GIMP-related by PinkX · · Score: 4, Interesting

    But a native port of GTK+ to OS X (via quartz/Aqua and not using X11) would be of great benefit.

    I've been a GIMP user since its early days. I was a former Photoshop aficionado, and by far I think the GIMP's UI is easier to use and more intuitive of that of PS. The right-click menu just rocks, the floating and dockable toolbars and panels are really practical.

    Almost 1 year ago I moved from Linux to OS X on the desktop. GIMP is still my favorite image manipulation software, but I would *really really* love to see it more integrated with the OS, as X11 is slow, bloated and unstable and just doesn't looks natural.

    I know the GIMP developer aren't to blame for this, but a native port of GTK+ and its related tools to the OS X framework would be great, to eliminate the dependency on X11 and get a more 'at home' feeling with the app. It was already done for Windows and OS X *should* be easier AFAIK because all the underlying *NIX stuff is already there.

    1. Re:I know it's not directly GIMP-related by Anonymous Coward · · Score: 0

      I know the GIMP developer aren't to blame for this, but a native port of GTK+...

      GTK stands for the GIMP Tool Kit. The GIMP developers are the people most directly responsible for GTK.

  24. allow it to be skinned, to allow a FULL pshop L/F by TheGratefulNet · · Score: 2, Insightful

    since its either illegal or financially unfeasable to create a complete look/feel clone of photoshop, allow the _ability_ to skin it and let 3rd parties (torrents, anyone?) create an exact look/feel of photoshop. gimp guys can't be sued and yet we'd still be able to have a feel-alike photoshop on unix.

    detach legal responsibility this way (like an .so that does 'bad' things yet the framework doesn't, so the framework guys can't be sued) and you have all kinds of new power possible.

    if we could make gimp look and feel very close to what pshop is like, we could get more of the artists who use and know pshop by heart - to give our side a try. and maybe even have an interest in porting the filters over, since that's where the real power lies.

    --

    --
    "It is now safe to switch off your computer."
  25. My Wish? by Anonymous Coward · · Score: 3, Interesting

    I'd like to see an Visual-Studio-like interface (hear me out!) for a graphics program.

    I like things to dock. It's nice to work with the document maximised and not have the palletes cover the document. It's nice to be able to customise menus and toolbars to your heart's content. It's nice to have tear-off menus for common actions, such as tearing off the menu for centring something.

    It's strange how Photoshop isn't nearly as customisable as Word when it comes to interface.

  26. a networking analogy on why same look/feel .. by TheGratefulNet · · Score: 1

    ..MATTERS.

    analogy: cisco IOS command line (CLI). its basically a marketing must-have(*) that any new networking gear have the same look/feel (when possible) to the IOS style ('show' commands, etc). with very few exceptions, its a market reality. I'm not debating its tech merit - just market acceptance (this coming from an enginerd, not a tie wearing guy).

    same idea here. if gimp is to be taken seriously by working professionals in the field (like the way the pros currently have an almost scary allegiance to pshop) then it has to have the same 'skin' (or allow for the same skin, maybe as a plug-in) as pshop. it just has to.

    (*) yes, juniper is an exception. there aren't that many successful exceptions, though.

    --

    --
    "It is now safe to switch off your computer."
  27. User interface design by lezerno · · Score: 2, Insightful

    A good user interface should allow people to do the job they want to do. I think the interface should be so simple that everyone can use it. I have been designing user interfaces for building energy programs that are so easy to use you don't even have to know anything about buildings or energy to use them. Maybe that is a bad thing?
    <URL:http://www.archiphysics.com/>

    1. Re:User interface design by Rysc · · Score: 1

      See this post.

      --
      I want my Cowboyneal
    2. Re:User interface design by Anonymous Coward · · Score: 0
    3. Re:User interface design by Anonymous Coward · · Score: 0

      Stop posting monospaced. It's annoying.

  28. Correction... by Anonymous Coward · · Score: 0

    All image windows have their own menu bar since v2.x.

    That should be:

    All image windows have their own menu bar by default since version 2.x.

    Which just goes to reinforce your first sentence - and since moosesocks hasn't actually used a recent version of GIMP, I think it's prudent to point this out, in case he/she decides to come back with "yeah, but they should be enabled by default."

  29. Palettes... by Muvlo+Redond · · Score: 1

    Personally, I'm a big fan of single-window/palette-based interfaces. Examples are Blender and ZBrush. Though both look quite distinct, they both keep everything in a single window, and keep everything organized for you. Tools can be reorganized by dragging palettes around, but they always fit neatly into shelves and panels, instead of floating over the image you're trying to edit. The key being that the computer is plenty smart enough to take care of managing my windows for me; I'd much rather be doing art than damaging the already sore muscles in my wrist by carefully positioning windows manually. (Incidentally, I've been experimenting with a palette-based interface of my own http://sharp3d.sourceforge.net/, which is probably why I'm so attached to them. ;) )

  30. Re:allow it to be skinned, to allow a FULL pshop L by Anonymous Coward · · Score: 0

    Believe it or not, creative people (like artists) enjoy creativity in their software. What's creative about ripping off Photoshop's interface? Much better to invent a new interface that stresses the GIMP's strengths (besides being intuitive, elegant, and inspirational to one's sense of creativity. I've never sounded so gay).

    Skinning is, at best, a cop-out; it's a way for the developers to wash their hands of the interface when they've realized, too late, they're no good at UI design. This may not always be true, but it would certainly be true in the case of the GIMP.

  31. I just want a simplified version. by Eneff · · Score: 1

    Or rather, an easy-to-learn version rather than something with as steep of a learning curve as the GIMP or photoshop.

    I'd love someone to just strip down the interface and give a good walkthrough. I'm talking something akin to the early paint shop pros.

    I don't use a graphical program every day. I don't want to spend hundreds of hours on a program that I'll only use occasionally for basic stuff.

  32. Re:allow it to be skinned, to allow a FULL pshop L by TheGratefulNet · · Score: 1

    you could look at it that way.

    or, you could look at it as a way of _deferral_. yes, that's right. and its not a bad thing.

    detaching form from function. we've been trying to do that via gui's for a long time now. this is just another level of detachment.

    its usually not worth the effort to abstract an abstraction. otoh, gimp creates gtk (the toolkit) JUST to serve as a basis FOR gimp. so its not hard to stretch to the next level and let gimp invent some new stuff to further abstract the user from the machinery and let gtk ultimately benefit.

    cop-out? in one way, I suppose. I think of it as 'pleasing more people by letting THEM decide'.

    oh, and don't short-change the extreme benefit of not having to relearn a whole new UI just to do the same thing you've been doing for years. don't kid yourself - many artists consider computers DRUDGERY and a chore. not having to learn another UI would be a godsend to them.

    --

    --
    "It is now safe to switch off your computer."
  33. Leave UI overhaul for 3.0 by Kickasso · · Score: 2, Interesting

    Add colour management and 16-bit depth *now*.

  34. That's kinda in its nature by leonbrooks · · Score: 1
    Script-fu seems to lack that nice Preview option
    Translate the Script-Fu to C, and you can have a preview for it just like everything else. Script-Fu is exactly what it says it is: a scripting language, not an extension API. It means that ad-hoc is relatively trivial but it also means that until some genius figures out how to give you previews for stuff which takes seconds-to-minutes, you're out of luck. Quicker to translate little scripts like that into C.

    What I would like to see in the existing previews is a zoom slider.
    --
    Got time? Spend some of it coding or testing
    1. Re:That's kinda in its nature by Dysan2k · · Score: 1

      That's definatly something to look at. I've never written a script-fu piece, but if I could get some speed boosts, preview windows, and such, it'd make a huge difference. I will take you up on the advice.

      --
      -What have you contributed lately?
  35. What SDI? by leonbrooks · · Score: 1

    I have three images open in GIMP now, and can cut, paste, drag and drop between them with impunity. Each has it own set of menus, plus the right-click one.

    If you want a separate context menu, invent one. C is not a difficult language to grasp. Then you can map the existing menu to one of the side-buttons of your mouse and be happy.

    --
    Got time? Spend some of it coding or testing
    1. Re:What SDI? by tverbeek · · Score: 1
      If you want a separate context menu, invent one. C is not a difficult language to grasp. Then you can map the existing menu to one of the side-buttons of your mouse and be happy.

      That's an excellent suggestion. I'll pass it along to the art instructors and graphic design students I work with. They're always looking for tech problems to solve... why, just the other day, one of them asked me for suggestions on how to get his Zip disk out of the drive when it didn't show up on his desktop.

      --
      http://alternatives.rzero.com/
    2. Re:What SDI? by cheesybagel · · Score: 1

      Zip disks? How quaint. I thought anyone would have a DVD or CD recorder by now. Heck they are dirt cheap.

  36. No. See elsewhere in this thread... by leonbrooks · · Score: 1

    ...where I propose a PS personality module. Wouldn't hurt to do an MS-Paint PM either. (-:

    --
    Got time? Spend some of it coding or testing
  37. It depends by G3ckoG33k · · Score: 1

    It depends, as always.

    If you go for the mass market, choose a Photoshop-like GUI. If you want to retain a uniquness, stay with GIMP.

    I have never used Photoshop, and am very satisfied with the current GUI of GIMP. Still, one has to accept that a lot of potential users are scared off because of it.

    Look at how Microsoft upgrade their software's GUI:s, minimally! They know how to make people _feel_ safe; yada-yada-BSOD-yada-crash-yada...

    So, despite people's feelings for GIMP's current GUI, get over it and go for a Photoshop look-alike.

    If not for anything else it may also give you some tips for 'missing' functionalities!

    1. Re:It depends by lachlan76 · · Score: 1

      What you don't mention is that the GIMP interface is a lot like that of Photoshop for Mac.

      Or at least, that was the impression I got in the 5 hours or so I used it at school. I missed the right-click menus though.

  38. I like it. by CaptnMArk · · Score: 1

    Simplifications are welcome, but please do not suggest stuff like window in window or the like.

  39. Yeah, call it FreeTouchUp... by leonbrooks · · Score: 1
    Rename the program.
    FreeTouchUp hints at what you can do with it, sounds vaguely like PhotoShop, and you can be sure that lots of idiots will download "FreeFeelUp" before the difference sinks in. (-:

    I s'pose we could try for something witty like "Frees Frame" or FLIP, for "Free/Libre Image Processor".
    --
    Got time? Spend some of it coding or testing
  40. Re:allow it to be skinned, to allow a FULL pshop L by lachlan76 · · Score: 1

    You have plugins/script-fu/python-fu, why not take out the main UI, and do everything using GIMP's built-in scripting/plugin engine?

  41. Well... n-bit depth by leonbrooks · · Score: 1

    1, 4, 8, 12, 16, 24, 32... the user shouldn't have to care.

    As I understand it, once they shim GEGL in, the rest will be easy.

    Unfortunately, the GEGL domain is off-air as I type, the last contribution to the GNOME repository for itis some testing stuff 9 months ago, and the last "real" code 11 months ago, most of it's a year or two old, all of the recent (in relative terms) changes were done by dsrogers. Not lookin' too sanguine.

    --
    Got time? Spend some of it coding or testing
    1. Re:Well... n-bit depth by arose · · Score: 1

      Not much surprise there; the Gimp developers have been working hard on the 2.* series of Gimp. Do you think that there is a seperate team working on GEGL?

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  42. survival of the gimpiest-Glade. by Anonymous Coward · · Score: 0

    Well my two cents (nonrefundable). One I believe Glade was suppose to address this issue. And two one might want to look into XUL (not just a Mozilla technology. e.g. Luxor).

    BTW Just be glad the interface isn't done in FLEX.

  43. Wish granted... in spades. by leonbrooks · · Score: 2, Informative
    --
    Got time? Spend some of it coding or testing
    1. Re:Wish granted... in spades. by Anonymous Coward · · Score: 0

      An ancient GIMP fork. With an extremely experimental and broken OS X port of an ancient GTK+. Not very useful.

  44. Fork off? It's been done. by leonbrooks · · Score: 1

    Robin Rowe dunnit.

    --
    Got time? Spend some of it coding or testing
    1. Re:Fork off? It's been done. by schumaml · · Score: 1

      Please note that Cinepaint is the continuation of GIMP's HOLLYWOOD branch, which was branched off in the GIMP 1.0 times - so some users might recognize its interface as somewhat familiar.

  45. User interface design-Domain Knowledge. by Anonymous Coward · · Score: 0

    "A good user interface should allow people to do the job they want to do. "

    Is an interface that people refuse to learn, keeping them from doing their jobs?

    "I think the interface should be so simple that everyone can use it."

    An interface is as simple as it's most complex idea.

    "I have been designing user interfaces for building energy programs that are so easy to use you don't even have to know anything about buildings or energy to use them. Maybe that is a bad thing?"

    And how are the two domains related?

    1. Re:User interface design-Domain Knowledge. by Anonymous Coward · · Score: 0

      it's most complex idea

      "its".

  46. It depends-A Vain MS. by Anonymous Coward · · Score: 0

    "Look at how Microsoft upgrade their software's GUI:s, minimally! "

    Like between Windows 3.1 and Windows 9.5? Or Windows 95 and XP? How about when LongHorn comes out?

    "So, despite people's feelings for GIMP's current GUI, get over it and go for a Photoshop look-alike."

    Who's "going for it"? The complainers or the one's doing the actual work?

  47. Well. by Kickasso · · Score: 1

    Looks like GIMP people are not really interested in photo editing. Sad, very very sad.

  48. OPTIONS OPTIONS OPTIONS by Anonymous Coward · · Score: 0

    Why not make it possible to config how it handles the windows instead of saying, no, its fine as it is

  49. Re: MDI vs Floating Windows vs ... by some+guy+I+know · · Score: 1
    [MDI] should be built in... or at least an install time option.
    It should be a run-time user option.
    Almost all windows should be able to be floating (independent) windows, child windows of an MDI window, docked panels within a paned window, or notebook panes in a tabbed notebook.
    This should apply to toolbars, image (editing) windows, tear-off menus, and some (non-modal) dialogs.
    It should be possible to "mix'n'match" windows, so that some windows are MDI, others are floating, etc.

    The mechanics for implementing this are "outside" of the logic for what goes on within the windows themselves, and could be accomplished without too much difficulty by subclassing a few GTK container classes to allow them to change their parents (assuming that GTK allows reparenting of existing widgets, which it should).
    --
    Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  50. Don't click parent link! by Anonymous Coward · · Score: 0

    WARNING: Parent link points to Adobe's Photoshop page! Zealots who follow the link may become enraged. In case of excessive agitation, administer valium or a large wooden mallet.

  51. [frown] by BrokenHalo · · Score: 2, Insightful
    Err... Am I the only one here who actually likes the GIMP UI? (And yes, I do use the GIMP almost every day.)

    OK, I have never tried it on Windows, but on Linux Metacity for all its faults (and they are legion) does a reasonable job of keeping the components where I can find them.

    Seems to me that the main complaint is that the GIMP doesn't follow the conventions set by MS Paint or Photoshop, and as far as I'm concerned, that is unfair. It doesn't follow that just because people are too lazy to learn how to use a tool effectively, there must be something wrong with the tool.

    1. Re:[frown] by Eideewt · · Score: 1

      I like it too. Nothing bugs me more than a window with a bunch of tiny windows within it. It's complicated when you have to worry about nested windows as well as dealing with all the parent windows. Way to modal for my taste. I'll take tabs where possible, and a bunch of happy little windows floating on their own otherwise. In my opinion, graphic design programs like the GIMP need to allow you to sprawl all over your monitor(s). Just like working with traditional media, everyone needs to be able to scatter their tools all over their workspace. It's especially handy when you do have another monitor, and you can put all your tool windows and unzoomed windows (which you use to monitor your work) off to the side.

  52. Do you know what a gimp is? by Anonymous Coward · · Score: 0

    nt

  53. Re:Fristage by the+argonaut · · Score: 0, Offtopic

    Is there a script that automatically mods all first posts down? While I'll admit that the parent post is not the most civil of posts (and includes a gnaa remark), it's a relevant comment.

    --
    fuck you.
  54. It's Obvious by cooldev · · Score: 1

    1) Single outer window with a single menubar and docking toolbars. (No, Deweirdifyer is not good enough.)

    2) Use native dialogs where possible (GIMP's File/Open dialogs are the worst file dialogs I've seen in years, but the bigger issue is the inconsistency).

    Both of these are trivial and constantly requested. If the GIMP developers do not implement them in the next release it will prove they're not interested in listening to their users.

    1. Re:It's Obvious by kaffiene · · Score: 1
      Both of these are trivial and constantly requested. If the GIMP developers do not implement them in the next release it will prove they're not interested in listening to their users.


      If you care so much about it, implement it yourself. The Gimp developers are not your personal slaves.

  55. Re:Have you actually used GIMP 2.2?-Fix It by the+argonaut · · Score: 1

    Okay, I'm now convinced that /. has implemented a new requirement that all moderators be crack addicts.

    Yes, the comment was short, but it said everything that needed to be said. It made a valid point, but apparently one that today's dittohead moderators disagreed with, and therefore decided to moderate into oblivion.

    I can only conclude that the Bushite philosophy of responding to dissent by stifling it is infecting all of society.

    --
    fuck you.
  56. virtual desktops + grey wallpaper by Henriok · · Score: 1

    Put GIMP in a separate virtual desktop and use a grey wallpaper.

    --

    - Henrik

    - when the Shadows descend -
  57. For my personal photos by ErroneousBee · · Score: 1

    I like to do up the best of my holiday photos in one big all-nighter and put them on the web, or send a CD to those who want it.

    What I hate is having to go go here to rotate, there to crop, somewhere else to fix the colours, and somewhere else again to resize and unsharp mask.

    I'd like a single panel that puts all the common photo editing tools in one place. These tools will include:
    o Rotate (90 degrees and a rotate handle)
    o Crop
    o Colour levels
    o Brightness and contrast
    o Desaturate
    o Resize
    o Sharpen filter
    o Unsharp mask filter

    Then I could wizz through the mass edits with only the occasional requirement to go to the layers and spot editing tools.

    --
    **TODO** Steal someone elses sig.
    1. Re:For my personal photos by Eideewt · · Score: 1

      Tearoff menus and hotkeys don't do it for you? I don't see how it could be any easier than hitting a couple keys and clicking an option on the menu that's floating nearby.

    2. Re:For my personal photos by ErroneousBee · · Score: 1

      I cant remember hotkeys for the dozens of apps I use in the various apps I use. I only use ctrl XCV and ctrl T in mozilla.

      Tear offs dont gather the functions I commonly use near each other. I would still have to navigate here to rotate, then close that dialog and colour balance, then close that dialog, locate the next dialog, etc etc etc.

      E.g.
      I open a jpg.

      Align and crop:
      Image -> transform -> rotate 90cw
      Image -> Layers -> Arbitary Transorm ( To tweak the horizon level)
      ( Problem 1, 2 paths to similar functionality, why cant there be a simple dialog that does the 90cw and still allows me to arbitaritly transform from the same place)
      Gimp window (it was hiding under mozilla!)-> Select the select tool
      Image window -> Select the area to crop
      Image -> Crop Image
      (problem 2 - all that navigation between 2 windows for such a simple operation)

      Now for the colours:
      Tools -> (bloody hell, I cant even remember this from 2 seconds ago and have to refer back to the dialog!) -> Colour Tools -> Levels
      Tools -> Colour Tools -> Brightness/contrast
      (problem 3. I was picking tools via Image, but this tool is under Tools. So I'm having to keep a mental map of what Im doing and where the tool I want for it has been placed in the menu hierarchy.)

      Scale image for web reducing from 2048px wide to a max side of 786x800
      Image -> Scale Image
      ( problem 4 - I dont have easy pressy buttons for what I want to do, I have to do the maths to decide which side is going to be maxed, isnt that what computers are supposed to be good at?)
      and I scale the image for the web, or for printing.

      Filters -> Enhance -> Unsharp mask.
      (problem again - at web resolutions the defaults raduis/amount are always too strong. 3px and .25 are better for me.)

      File -> Save as
      Now I get asked all kinds of questions about exporting, to which I always answer yes. Give it a new name (no autosuggest?).

      1 photo edited, 49 to go.

      I think what I really want is some kind of wizard that takes me through the stages one at a time without forcing me to navigate the menus and windows.

      I want a simpler way of leveling horizons and aligning the verticals, pick 2 or more points and tell it to rotate them as the horizon or a vertical.

      I want a simpler colour manager with contrast/brightness/desaturate/levels all done simply and in one place. Perhaps all the colour tools could be 1 big dialog with tabs to get to the specific colour tool I want.

      I never seem to use the current tabs, because that all relate to viewing, and not to tools.

      Now the image has a menu bar, the contextual menu could be a little more useful, containing a better set of option in a pie menu and not a drop down menu that makes Fitts cry.

      I also hate playing hunt the dialog box, but others have mentioned that.

      --
      **TODO** Steal someone elses sig.
    3. Re:For my personal photos by testerus · · Score: 1

      Why do you need GIMP for simple image manipulation? An image viewer that supports KIPI should do all what you need.

    4. Re:For my personal photos by ErroneousBee · · Score: 1

      Mostly cos Ive never noticed it before. Just looked at the homepage and it looks like it may be a bit too simple, but when urpmi completes I will see for myself.

      I occassionally use Gimp under windows at work, and occasioanlly use some of the less common GIMP tools (layers, spot editing), so will probably stick with GIMP.

      --
      **TODO** Steal someone elses sig.
    5. Re:For my personal photos by Eideewt · · Score: 1

      I see. You'd rather you could have all your common photo editing functions accessible in one window so you don't have to open and close a bunch of dialogs, and you'd like easier to use tools. I can understand your trouble. I'd never thought those problems since my GIMP usage is usually for drawing things, and I just remember four or five hotkeys and seldom need to crop and rotate and scale and adjust colors. I guess it's much better for some functions than others.

  58. Nope. by jspoon · · Score: 1

    Read your own link. Gimp.app is just a standalone application that you double click instead of opening in the terminal, I guess the package is also sure to include all the dependancies and such-except X11. And it doesn't use Aqua, except to the extent that any other X11 sits on top of it.

    1. Re:Nope. by dan_bethe · · Score: 1

      WHOOPS. Wrong link! I spent half an hour searching for these just for this thread and got em mixed up. ;) Here is GTK+ ported to Aqua along with assorted apps and screenshots! Thanks.

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

      You mean the port of GTK+ 1 to Aqua? That doesn't help with Gimp 2.2.

  59. I'll bite by Kyouryuu · · Score: 1
    I'm going to refer to aspects of Paint Shop Pro 7 in this.

    First, Gimp can keep the multiple windows thing. I think it's great for those with multiple monitors. The ability to drag windows from one screen to another is quite convenient. The only thing I ask is that Gimp group all windows as one entry on the taskbar. I can't see a good reason why Gimp should spam the taskbar with four to five entries.

    Establish a distinction between vector and raster via Layers. Gimp has a system where Lines are in a seperate tab than Layers, but can get stroked to appear in a Layer. The problem is that if you want to draw with the Pen tool, like if you're outlining something, you have this needless step of periodically hitting the "Stroke Path" button, selecting "Pencil," and hitting okay. In PSP, I can use the Pen tool directly on a Raster layer. If I want to preserve the individual nodes, I can create a vector line in the Pen tool and use a Vector layer to store it.

    Gimp should have a Properties window for each of its tools. The properties window should use sliders for setting options. One of the nuances of the Gimp that annoys me is how you can only pick from pre-created brushes or create your own. To create some non-standard size (like 2x2, for example), you have to walk through creating a whole custom brush. I'd much prefer a slider that ramps from 1 to, say, 255. PSP has sliders for Size, Hardness, Opacity, Step, and Density.

    Gimp should have preview windows for its various filter effects and adjustment tools that offer a side-by-side comparison of pre-change and post-change images.

    I really wish Gimp had a simplified Pen tool. Granted, PSP8 and up, as well as Photoshop, have really sophisticated ones. But the one in PSP7, particularly with regard to Bezier curves, is very simple. Two clicks set the beginning and end of the line. Two drags set the curve. And it automatically renders it to a raster layer. I don't need a fancy node-line-node-line architecture. If Gimp did this, I'd be ecstatic.

  60. How to fix the name by tverbeek · · Score: 1
    To all those here suggesting that the name of the program be changed: It ain't gonna happen. The devs love "GIMP" for all the reasons you hate it.

    But if you really feel strongly about it, you can do it anyway. Ye olde GPL makes it easy. Just pick a better name, download the source code, do a global search-and-replace of "GIMP" with "____", make a new splash screen (I recommend using ____), recompile it, put it on the web at www.____.org, and start promoting the heck out of it. This doesn't require lots of programming expertise (like all the other "fix it yourself" suggestions), but it'll address the problem of the name.

    --
    http://alternatives.rzero.com/
    1. Re:How to fix the name by Anonymous Coward · · Score: 0

      While it does change the version on that one tarball, who's gonna maintain it, add new features, fix bugs? If it ain't in the mainline, merging in patches is a whole lot of work, just to keep a "name change" branch.

    2. Re:How to fix the name by tverbeek · · Score: 1
      While it does change the version on that one tarball, who's gonna maintain it, add new features, fix bugs? If it ain't in the mainline, merging in patches is a whole lot of work, just to keep a "name change" branch.

      I'm not talking about a branch; I'm talking about a repackaging. Whenever you wanted to issue a new release (the target audience for this wouldn't want nightly tarballs; they'd want an annual or maybe quarterly setup.exe), you'd just download the latest STABILE source, apply a few cosmetic changes to "fix" the name (a pretty consistent patch), and you'd be done. Kind of like what AOL's been doing with Mozilla/Netscape.

      Yes, it's a nontrivial amount of work, but if someone really feels that the GIMP's name is a serious drawback, periodically updating a rebranded version of it for a mainstream user base a few times a year shouldn't be that difficult a burden.

      --
      http://alternatives.rzero.com/
  61. Remember My Panels by Anonymous Coward · · Score: 0

    The one complaint I have about the GIMP is about closing it down. (On WinXP, if that makes a difference.) When I fire up the GIMP, I have the three windows: Toolbars, Image and the Layers/Paths/Undo/etc. dialogs.

    When I'm done, I hit the window close button in the upper right of the windows - but sometimes I hit the dialog close first. This causes the dialog to close, but not the program. What's worse is that when I reopen the GIMP, it remembers I closed the dialogs, so I have to spend five minutes setting up the dialogs again - work which gets trashed the next time I close down the GIMP, and accidentally hit the dialog close button.

    Also, I hate how the B/W error window isn't always up, but sometimes pops up later. And then, if you forget and click on the close button of the message window, the whole program shuts down, and not just the messaging window.

  62. tool modifier shortcuts by Anonymous Coward · · Score: 0

    Haven't tried this in GIMP, but a great shortcut in Photoshop I really like is pressing the spacebar in the middle of using a tool, so that either the object can be moved, or the screen can be scrolled without leaving the middle of what you are doing with the tool. eg alternating between dragging the radius of an elipse and moving it in one go. Also the CTRL-ALT-SHIFT keys should modify tools in the same way - or at least be easily configurable to operate this way.

  63. Copy Inkscape and provide a real full screen mode. by testerus · · Score: 1

    First, what I love about Photoshop is that I just have to hit F twice to enable real fullscreen. Then I can pick my tool and the options I need and hide the floating dialogs with Tab. The only thing missing from photoshop is to be able to work at the edge of an image in the center of the screen.

    Second, you should have a look at the interface of Inkscape . IMHO it is much clearer than the one of GIMP.

    And third, please enable voting in bugzilla. There might be a lots of cool ideas hiding.

  64. Economy of UI design by volvis · · Score: 1

    The GIMP UI should be more economic. As a graphic artist, I appreciate how Photoshop UI is designed to step aside and give me as much workspace as I need.

    The toolbox in Photoshop is a sleek lil' creature, about 64 pixels wide. The toolbox in GIMP is at minimum over twice that much.

    The Navigator/Navigation then? I resized them both to about 250px in all sides and put them next to each other. The navigation view in GIMP was approximately half of that in Photoshop.

    In Photoshop, the per centage meter, the slider and the zoom buttons take only one single linebreak, whereas GIMP takes three. That is just wasteful!

    1. Re:Economy of UI design by Synbiosis · · Score: 1

      That's a huge problem with Linux in general, in my experience. Every linux program or even open-source program I've used has been extremely wasteful regarding screen space - compare the size of the OpenOffice toolbars to that of Microsoft word.

      This renders most applications almost unusable on anything less than 1024x768, and forget editing magazine-quality images on that.

  65. Multiple Color Pickers by Xofer+D · · Score: 1

    All I want is to be able to pick three pixels, and watch the colour value (ie, numbers) change as I do other operations, like curve manipulation. As it is I have to write the numbers down and re-check them, which is kind of nuts.

    Now, if this is doable some other way, then let me know how... but the eyedropper tool replaces the colour and never updates it.

    --
    The Signal/Noise ratio can be improved in two ways. Remaining silent is the OTHER way.
  66. Bollocks. by kaffiene · · Score: 1

    I'm not a Gimp programmer, and I like the Gimp interface. I've used both Photoshop and the Gimp professionally and found them both about as much work to learn.

    The Gimp interface is fine. The whinging about needing changes seems to be just from Photoshop uses who want it to be a Photoshop clone. Here's a clue: it's not, it never will be. Get used to it.

    The thing is, once you've invested time in learning an interface you get used to it, you like it and you get resistant to change. This complaining about the Gimp is laziness from the Photoshop croud who can't be bothered learning that the Gimp has its own way of doing things. This is not a problem with the Gimp.

    I repeat, I'm a user of imaging tools, not a producer. Plenty of Gimp users are perfectly happy with it as it is, thank you very much.

  67. Re:Fristage by Anonymous Coward · · Score: 0

    It's probably the "propz to gnaa"

  68. Name Change by lemur337 · · Score: 1

    ... is the thing that stands out me.

  69. Re:Have you actually used GIMP 2.2?-Fix It by KlomDark · · Score: 1

    I totally agree, I've been noticing a "sea change" in moderation results as well. Not sure what the deal is, but it's weird.

  70. Did you tell him to drop it into the trash? by leonbrooks · · Score: 1

    The machine, of course, not any icons.

    Post constructive suggestions. If they really are arts students, get them to draw what they want it to look like and submit that. Too hard? Too obvious? Too constructive? Not sarcastic enough? Stop me when I get close.

    --
    Got time? Spend some of it coding or testing
    1. Re:Did you tell him to drop it into the trash? by tverbeek · · Score: 1
      Sorry, I'll be less figurative and more literal:

      Your suggestion was "constructive" only to someone technologically adept enough to not need the suggestion. For the majority of people who are being told "Try the GIMP; it's a great replacement for Photoshop," them coming back to say, "um, no it isn't," your suggestion was dismissive and useless. "Go learn a skill which you may have no aptitude for, and that you have no other use for (but which I personally found fun and easy, so you will too), so you can fix what's wrong with it yourself." I'm not going to learn carpentry and rebuild my new desk because it turns out to be too big for my office; I'm going to take it back, get a smaller one, and get back to doing the stuff I want to be doing.

      --
      http://alternatives.rzero.com/
  71. Consider me honoured. by leonbrooks · · Score: 1

    And can I recommend the #gimp IRC channel for instant advice?

    --
    Got time? Spend some of it coding or testing
  72. Have you actually tried it? by leonbrooks · · Score: 1
    I thought not.

    Here is a screenshot for you, about a thousand px on a side, 178kB. The background image is a big gumnut, up close and personal.

    Note the following:
    • Menus on each document window
    • colour depths in the File/New dialog
    • room for biiiig numbers in the colour depths
    • more brushes
    There are a lot more improvements but I couldn't be bothered ferreting them out for some random skeptic who probably won't even bother to read what I have posted.

    This is CinePaint 0.18-1, (urpmi cinepaint, pause, done) the current version is 0.18-3.
    --
    Got time? Spend some of it coding or testing
  73. Paint Shop Pro? by xtal · · Score: 1

    I find myself using this program over and over because it's quick and does what I need quickly, and I don't need to use a tutorial or a manual to accomplish it.

    Perhaps some pointers can be taken from there? I'm still looking for a good open-source alternative to PSP for my Powerbook.

    --
    ..don't panic
  74. Re:Have you actually used GIMP 2.2?-Fix It by Anonymous Coward · · Score: 0

    Yes, the comment was short, but it said everything that needed to be said. It made a valid point, but apparently one that today's dittohead moderators disagreed with, and therefore decided to moderate into oblivion.

    No, it didn't. It made the assertion "Photoshop users put up with significant shortcomings in Photoshop", but did not provide any evidence to support this; it did not even attempt to identify ONE such shortcoming that should be a cause for Photoshop users to consider switching to a different product.

    I am disinterested in this debate; I've never used Photoshop and I haven't tried GIMP since the 1.2 days (I guess it's about time I gave it another go, the new snap-together tool windows sound rather nice). Merely asserting that Photoshop has unspecified flaws therefore tells me nothing. I assume that if anyone knew of specific flaws, they would mention them when asserting that flaws exist. I therefore assume that when someone asserts flaws exist without providing examples, they are either making that assertion from ignorance, or they are trolling. In both cases, they deserve modding down, and in neither case is modding down a sign of crack use or "dittohead" status.

    If anyone cares to identify a major flaw in Photoshop that Adobe have refused to fix, and that Photoshop users have to (and do) jump through hoops to work round, then that person would deserve modding up. But the grandparent post did not, and so did not. QED.

  75. Easier UI methods for making most common things by lamikr · · Score: 1

    Nice that you are asking these things. Here are some issues which comes to my mind. 1) Most commonly used simple drawing features. I use Gimp about once in a year for drawing and I have noticed that the first showstopper is always the circle and box drawing. When I select circle tool and draw circle I expect that it will draw me a circle. Unfortunately that does not happen with gimp and now forexample I do not remember how to do that. If I remember correctly it was something related for chaning colors and filling selection but I need to go to web for searching this from the gimp tutorials. (If I remember correctly I spent 2 years ago a half day for searching that info from the web) I have also noticed that circle drawing is one of the first questions also from others to whom I am showing gimp. 2) Help search. Because of the problem 1, I opened gimp help and pressed ctrl-f in order to search "circle" but only after that I noticed that the gimp help does not have any kind of search functionality... 3) Text drawing. When I select "T" tool and click screen for drawing text, text writing dialog opens as expected. I would however be able to change the used font directly from that same dialog where I write the text. 4) Is it afterwards possible to select certain text from the gimp image and change the font used? (Possible by clicking right mouse button over the text?) 5) If I put all three gimp icons together they should "snap" together in a way that hiding/displaying/minimizing/maximizing one would hide/display/minimize/maximize all.

    1. Re:Easier UI methods for making most common things by arose · · Score: 1

      1) If you want to draw cirles and boxes use Inkscape, Gimp is not optimized for that. 3) I don't agree, font selection is no different from colour selection and other options, I don't want all of them in the dialog. 4) Left click your text with the Text tool and change the font in the tool window. 5) You mean taskbar icons? If so Gimp is not a WM.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
  76. Re:Copy Inkscape and provide a real full screen mo by arose · · Score: 1

    Won't work. You can't work with several images with a Inkscape like interface, but you usualy need more then one when working with bitmaps. A fullscreen mode with tools and menus arranged allong the edges (in one row, clickable on the edge) would rock though.

    --
    Analogies don't equal equalities, they are merely somewhat analogous.