Slashdot Mirror


GIMP's Next-generation Imaging Core Demonstrated

brendan0powers writes "GIMP developer Øvind Kolås gave a public demonstration of the Generic Graphical Library (GEGL) on Friday at the Piksel 06 festival in Bergen, Norway. GEGL has long been slated to replace the core image processing framework of the GIMP, bringing with it entirely new data models and operations — but development had languished to the point where many critics had written the project off entirely." Linux.com and Slashdot are both part of OSTG.

71 of 482 comments (clear)

  1. It's about time by Salvance · · Score: 5, Interesting

    It's rather amazing that after years GIMP hasn't been improved to a point where it is a serious contender for graphic designers and photo editors. I love using open source products where I can, but GIMP has always seemed subpar. Maybe I'm underestimating the difficulty of creating such tools, or am just too used to Photoshop. I can't wait to check it out!

    --
    Crack - Free with every butt and set of boobs
    1. Re:It's about time by ben+there... · · Score: 4, Interesting

      I see that a lot. But hardly ever with any real examples of what it is missing that you need for professional graphics work. I'd love to hear specifically what is missing, as I'm sure the devs would too. Is it just the color management for print design, or something else?

    2. Re:It's about time by Anonymous Coward · · Score: 2, Insightful

      Yes, the color management is an issue (unless we were to make a gimp-non-US), but not a technical one - until the USA stops travelling down the copyright/patent path of infofascism, the gimp team can't _legally_ implement certain features. Sigh.

      But the main problem with adoption is the name. Nobody who has seen "Pulp Fiction" (an american film) can take the GIMP entirely seriously. A simple name change would massively increase adoption in pro circles, if you ask me. Yes, arty people are that picky.

    3. Re:It's about time by Frumious+Wombat · · Score: 4, Interesting

      Well, there's 16-bit color support, non-destructive image editing (adjustment layers), CMYK and good profiling tools for RGB (lightjets) devices. Text mode could do a better job kerning as well (the third German example on their screenshots web page illustrates the issue), and some of the tools need a little polish. Maybe the problems will go away with 16-bit color, but it tends to posterize images easily if you do harsh curves adjustments.

      From over here, I'd like to see the X11 dependence on the Macs go away. Pitch the GTK base and use QT, which is already efficiently cross-platform on Macs, Linux, and Windows.

      As for the interface, so be it. If the other issues are fixed, the interface can be learned quickly enough. I used to use it for web images, and still have a certain fondness for 0.54, which ran on our SGI workstations. Maybe someone can ressurect that code-base and issue it as LIMP (Light Image Manipulation Program).

      --
      the more accurate the calculations became, the more the concepts tended to vanish into thin air. R. S. Mulliken
    4. Re:It's about time by Cinder6 · · Score: 5, Informative
      From over here, I'd like to see the X11 dependence on the Macs go away. Pitch the GTK base and use QT, which is already efficiently cross-platform on Macs, Linux, and Windows.
      I'll agree there shouldn't be an X11 dependency on Macs, but I think the odds of the GIMP, of all things, being ported to Qt are rather slim. After all, it's the original source of GTK.
      --
      If you can't convince them, convict them.
    5. Re:It's about time by creepynut · · Score: 4, Funny
      Pitch the GTK base and use QT, which is already efficiently cross-platform on Macs, Linux, and Windows.
      Yes! Let's have the GIMP pitch the GIMP Toolkit for QT. :)
    6. Re:It's about time by MadUndergrad · · Score: 3, Funny

      That you're neither rich nor a graphic artist?

    7. Re:It's about time by fossa · · Score: 4, Insightful

      Linux is a vastly superior name than GIMP. The word GIMP could easily offend some. Linux is a made up word. I've installed GIMP on many a windows users machine as a free image editor, and depending on who it is I feel uncomfortable calling it by name. Sure, it's probably not the biggest reason for the lack of popularity, but I don't think it's insignificant. libcaca is another one. Cool library, but seriously, libcaca? And the Do Whatever the Fuck You Want License? The name has honestly made me less interested in the library, as lame and irrational as that is. I don't paint my walls dissonant colors; I don't want my apps with unsightly names.

    8. Re:It's about time by gutnor · · Score: 2, Insightful

      Look stupid saying it like that, but Color management seems important enough for professional to pay for Photoshop (500$-ish) instead of the much cheaper Photoshop Element (50$-ish)

      Graphic professional are color matching paranoid. A problem between a color of a design and the output from the output company cost lots of money and finding what is wrong in the flow requires the same sort of approach as finding a bug in an application.

      What is also missing is maybe that Adobe build its tools closely with their professional customers while Gimp looks like developed by developer for enthousiast/developer. I just imagine that the situation would be the same if some graphic professional created a uber-powerful new programming language for other graphic pro, with a completely different syntax that also just happen to miss only one essential feature for pro developers (can't think of one good example but let's take 'no debugger' or 'no string manipulation function'): whatever the intrinsic merit of the product, it would have more difficulties to take off in dev circles.

    9. Re:It's about time by killjoe · · Score: 2, Insightful

      The question is why would you want this guy to use GIMP? If he refuses to a product based solely on name without even bothering to learn anything about it he will probably hurt the community more then helping it.

      Think about it. This guy will whine non stop at the developers. He will yell and scream at people for not helping him enough. He will fill the IRC channels with vitriol and he will not lift a finger to help anybody, will not file a bug report, will not write one line code, will not write one line of documentation, will not submit one icon or even an idea towards making anything better.

      I honestly don't see why the GIMP community needs people like him. This is not a product, nobody is making money. Is the loss of a guy who laughs at the name and refuses to use the product a loss or a gain?

      I say it's a gain, I say it's a huge gain because the guy is going to end up being a drain on the morale and the productivity of everybody else.

      --
      evil is as evil does
    10. Re:It's about time by springbox · · Score: 4, Interesting
      I don't know what the problem is. The WTFPL is pretty straight forward:

      DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
      Version 2, December 2004

      Copyright (C) 2004 Sam Hocevar
      22 rue de Plaisance, 75014 Paris, France
      Everyone is permitted to copy and distribute verbatim or modified
      copies of this license document, and changing it is allowed as long
      as the name is changed.

      DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
      TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

      0. You just DO WHAT THE FUCK YOU WANT TO.

      When free means completely free!

      I wouldn't be too concerned about the name if the software does something useful

    11. Re:It's about time by xrayspx · · Score: 3, Informative

      Layer grouping is one of the biggest gripes I've gotten so far. Dealing with a 120MB image with 60 layers isn't easy when they're not grouped in some hierarchy. I think the rest was general "I hate this because it's different from what I know", rather than actual lack of function, but honestly, the artist involved was...unmotivated...to give Gimp a fair shake. At the risk of having to hire a food taster to test my meals, I decided to let it go.

    12. Re:It's about time by killjoe · · Score: 2, Insightful

      I think firefox is a special case because an increase in share in the browser market will discourage people from writing IE only web sites. The photo editing industry does not have a similar situation. Whether GIMP has one user or a million only makes a difference in so far as those users help or hurt the community. I say a community of 10,000 active helping users is better then a community of one million whining ones.

      --
      evil is as evil does
    13. Re:It's about time by Raffaello · · Score: 2, Insightful

      Sometimes in arguments such as these the truth is not halfway between the two sides - sometimes one side is just wrong. In this case, the cross-platform side is just wrong. Why? Because the number of people who use many different applications all on one platform is a couple of orders of magnitude larger than the number of people who use the same application on more than one platform. This being the case, it is far more important for application GUIs to be consistent across applications on a single platform than it is for the GUI for any one application to be consistent *across* platforms.

      In the big picture, this is why foss apps and oses still languish - foss advocates don't actually bother to count these numbers because they don't rely on large numbers of users actually *paying* for their product. Commercial software developers pay close attention to these numbers because they won't have anything to pay their mortgages and their kids' orthodontia bills with if they don't.

    14. Re:It's about time by JohnnyBigodes · · Score: 2, Insightful

      A proper GUI. Repeat after me, "a proper GUI". I've tried using GIMP in the past, first on Linux, then on Windows, every time that it seemed to show some advance, and the GUI didn't seem to change, if at all.

      It's misplaced options everywhere, needless mini-windows everywhere (instead of combining several within one), the whole retarted concept GUI (sorry guys, but outside the UNIX window manager world, that simply *does* *not* *work*), the non-standard file and print dialogs (GTK on Windows was always a kludge and never an integrated concept, for samples of this, see Eclipse and Firefox), etc etc etc. Never mind the fact that the UI doesn't even look the same as other apps. Basically, it's little problems anywhere and everywhere that come together to form a big big problem.

      And now I'm bracing for the impact of a thousand replies stating that 1) it's meant to be learnt / 2) use a proper window manager / 3) the options are there if I want to find them (why should I "find them"? they're supposed to "be found"), and all of the other mantras that will kept being chanted over and over again.

      Oh and by the way, even though I don't think it's a problem per se, the "GIMP" name isn't also the best choice. If anything, it's not catchy or easily remembered.

      As a final note: I would absolutely LOVE if the GIMP became a proper, standard, polished, full-bodied app. I use several OSS apps by choice and I love those, but unfortunately the UI (or lack of) problem common with many free/OSS apps is definitely present.

    15. Re:It's about time by sakusha · · Score: 2, Insightful
      actually the problem is that PANTONE exploits loopholes in trademark law to make money selling a list of colors

      No.

      The Pantone Color System is a system of ink formulas, based on about 12 Pantone inks with patented chemical formulas. You can mix any Pantone color with the Pantone primary colors plus CMYK. But you cannot mix any Pantone color with CMYK. For example, there is no way to achieve an intense orange like Pantone Orange 21 with CMYK, because it is beyond the gamut of CMYK inks. That's why Pantone Orange 21 is a primary color in their ink set. There are clones of the Pantone inks, but they aren't quite the same formula, so they don't always mix to the same colors. Nobody's going to risk an expensive print campaign with hundreds of thousands of dollars of printing on imitation Pantone inks.

      But if you want to use a system that is solely based on CMYK, you can use a non-Pantone scheme. Guess what? Most pro designers that don't use the Pantone CMYK specs use TruMatch, and they buy the TruMatch swatch books, oh my god, another licensed color scheme, they're making money selling a list of colors! Yes, designers prefer using a commercially licensed color system like TruMatch because it is a standard, every designer either has the swatch book, or can walk into any art store and buy one if they need one.

      These are the realities of professional design and print work. If GIMP cannot pay for licenses for the standard tools of the trade, they will never gain acceptance. Professional designers use Photoshop because it uses the conventional, widely accepted systems like Pantone and TruMatch. Professionals lead the market, and if you can't gain acceptance with professionals, you have only amateurs as your market. Good luck with that.
    16. Re:It's about time by stuuf · · Score: 2, Insightful

      Well, since The Gimp's developers are commited to keeping the program free, if one of those technologies is available only under an NDA or other restrictive license, they effectively can't use it.

      --

      Everyone is born right-handed; only the greatest overcome it

    17. Re:It's about time by the_olo · · Score: 4, Informative

      I'd love to hear specifically what is missing, as I'm sure the devs would too. Is it just the color management for print design, or something else?


      Let's try:



      • Support for various additional color spaces in addition to grayscale and RGB, e.g. CMYK, LAB, HSB. I'm not speaking about the color chooser, which AFAIR lets you pick colors using CMYK already. I'm talking about the image being stored in memory (and on disk in .xcf) and processed using particular color space representation, e.g. for CMYK the image is stored with 4 channels (look at them like color planes) representing the intensity of Cyan, Magenta, Yellow and blacK pigments in a subtractive model (RGB on the other hand, is additive). Some color corrections are done most easily when working in LAB color space Read some books by Dan Margulis to get an idea.
      • Support for color separations (including various settings like dot gain, black point compensation, additional spot colors beside CMYK) and color management is an essential feature for any professional wanting to print the results of one's work and have them match the screen representation.
      • Support for 16-bits or more (32-bit, floating point etc.) per channel for color spaces, integrated through all the workflow (possibly from the camera RAW files, through all the color curve corrections, levels, filters, hue mappings, up to the output file) so the dynamic range is high and minimal information is lost during colors / tones manipulation
      • adjustment layers
      • needs lots of usability fixes, like:
        • panning with a single keypress + mouse drag (one cannot simply press space and pan around the image with the mouse)
        • ability to scroll the image window beyond the image border regardless of zoom level (GIMP doesn't let you scroll beyond the image's edge which is quite irritating)
        • more GUI manipulation flexibility - ability to reorganize the whole UI into single MDI window similar to Photoshop or Corel PhotoPaint; but not at the expense of usability - it should be extremely hard to reorganize the GUI unintentionally (no tear-off toolbars like in MS Office - it's a usability disaster)
        • support for "workspace themes" - named sets of window positions, docker layouts, and so on. There should be 2 predefined themes available: "GIMP standard" and "Photoshop-like" - this would help the photoshoppers make the switch and do their first steps in GIMP.

    18. Re:It's about time by arose · · Score: 2, Informative

      1-4 all depend on GEGL.

      panning with a single keypress + mouse drag (one cannot simply press space and pan around the image with the mouse)

      Will be in 2.4.

      more GUI manipulation flexibility - ability to reorganize the whole UI into single MDI window similar to Photoshop or Corel PhotoPaint

      AFAIK the developers believe this will be much work with little benefit, because Windows is neither the platform they use nor their main "market". By analogy: is the Macintosh version of Photoshop MDI capable?

      support for "workspace themes"

      Someone would have to keep this up to date and evidently the GIMP developers would rather concentrate to improve user expierence for GIMP users then to conventrate on Photoshop switchers. As I see it if there actualy is demand for a Photoshop like GIMP then Gimpshop will flourish, time will tell.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    19. Re:It's about time by pilkul · · Score: 2, Informative

      My point is that scrapping and rewriting the entire UI (which is probably 2/3 of the code) for the sake of one minority platform is ridiculous. A more sensible request would be for Mac GTK to be improved to use native Mac APIs.

  2. Krita by barkholt · · Score: 5, Insightful

    They need to get this integrated before http://www.koffice.org/krita/ runs them over :)

    --
    - barkholt
    1. Re:Krita by archen · · Score: 4, Interesting

      Krita is already set to run them over, it's just a matter of time. The application has gone to a crash prone app with a barely useful featureset, to fairly stable with a modest featureset in a very short timespan. And it seems like it's just gaining more momentum as it goes on. For now development will probably slow as everyone works hard on porting to KDE4, but make no mistake that this app is the graphical interface many have been begging for on Linux. Many of us use the Gimp because there's no other option (or we don't feel like using photoshop in wine), but there will soon be a point where the gimp is going to end up a rather orphaned application as far as their userbase goes. With QT being cross platform, I might even be a bit conserned if I were Corel - the {now} owners of PaintShop Pro.

    2. Re:Krita by PitaBred · · Score: 2

      Does Krita work on Windows? GIMP is still my image editor of choice for all the "need more power than Paint but not enough to buy Photoshop" image work I have to do at work. And I'd run Linux, but I need to support Windows users, so I can't very well not run what they're running.

  3. The difference between The Gimp and Excel.. by QuantumG · · Score: 5, Interesting

    Ever tried to do basic drawing in The Gimp? Like, say, drawing a circle? Ask any Gimp developer why this is such a bitch and they'll tell you something like: The Gimp is an image manipulation program, not a drawing program, go use Inkscape or something if you want to draw circles. What's this got to do with Excel? Well, Excel is a spreadsheet program. It's ment for making reports or doing accounting or playing "what if" games with money. About 10 years ago the developers of Excel went and did a survey of what their customers were using Excel for. Turns out the vast majority of people were using Excel to make lists. Shopping lists. Laundry lists. People to Kill. That sort of thing. Did the Excel developers say "hey, Microsoft Word has better support for making lists, go use that!" .. no, obviously. What they did was study the way people use the software and make it better for what they are doing. They made it so you could hide the cell lines when you print and so you can print the numbers of the cells if you want. They made it so when you enter something really long into a cell it automatically overlaps the cells next to it, and so it would print that way. That's how software should be made, with a focus on what the user wants out of the software.

    --
    How we know is more important than what we know.
    1. Re:The difference between The Gimp and Excel.. by Blakey+Rat · · Score: 2, Insightful

      With a lot of open source projects, your thinking would be embraced to make a great product. See Firefox, for instance. The problem is that the GIMP developers just don't give a flying crap about it what-so-ever, so give up now. Photoshop Elements is only $90, does everything GIMP does but better, and is about 10 times easier to use.

    2. Re:The difference between The Gimp and Excel.. by ben+there... · · Score: 2, Informative
      Ever tried to do basic drawing in The Gimp? Like, say, drawing a circle?

      That's actually a really old version that those instructions are for, as evidenced by the fact that Shift constrains circles now, not Ctrl. You can either select a circle, then use Edit->Stroke Selection and select the width of the line, or Select->Border after selecting a circle, then fill it with a color or pattern. Neither option is as simple as a circle tool, but both are easier than those old (1.x?) instructions.
    3. Re:The difference between The Gimp and Excel.. by swillden · · Score: 4, Insightful

      Ever tried to do basic drawing in The Gimp? Like, say, drawing a circle?

      First, there's a much easier way to draw a circle than the one you linked to. To draw a circle: use the ellipse select tool, holding down the shift key, then use Edit->Stroke Selection. Done. You can adjust the width, color, pattern, etc. of the circle on the Stroke Selection tool that pops up.

      Second, if even that seems like too much effort, well, I'm with the developers on this one: The GIMP is a photo manipulation tool, not a drawing tool. As a fairly heavy GIMP user, I don't want the interface cluttered up with additional drawing-related tools, not when (a) there's a perfectly good, if non-obvious, way to accomplish the task and (b) it's not the tool's primary job.

      That's how software should be made, with a focus on what the user wants out of the software.

      Which user? You can't be everything to everyone. In this case, people editing photos very rarely have any need for drawing circles, and it's a bad idea to clutter the UI up with stuff that they aren't going to use much anyway.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    4. Re:The difference between The Gimp and Excel.. by MobileTatsu-NJG · · Score: 4, Insightful

      "Ask any Gimp developer why this is such a bitch and they'll tell you something like: The Gimp is an image manipulation program, not a drawing program, go use Inkscape or something if you want to draw circles."

      That's the sort of answer that, if used frequently, could kill OSS. If the aim is to replace commercial software with 'free' software, then the 'customer is always right' motto still applies.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    5. Re:The difference between The Gimp and Excel.. by chill · · Score: 5, Insightful

      I see your "the customer is always right" cliche and raise you one "use the right tool for the right job".

      --
      Learning HOW to think is more important than learning WHAT to think.
    6. Re:The difference between The Gimp and Excel.. by ottffssent · · Score: 3, Interesting

      That's only half the story. It's equally correct to say that the Gimp is not a drawing program, and that the Gimp developers should not duplicate the work of a drawing program's developers. Unix has been successful with a large array of small tools that do one thing and do it well (and play well with others). Microsoft has been successful throwing more features onto the fire when the flames burn low. To say that Microsoft's success with their method invalidates the Unix way is shortsighted.

      It would be nice to have one app that has excellent drawing tools, excellent retouching tools, excellent compositing tools, costs nothing, and makes toast. But even Adobe splits these tools into multiple apps, and they don't have to do it for free. So while "use Inkscape" isn't the answer you want, and it isn't the ideal answer, it's also not an unreasonable answer.

    7. Re:The difference between The Gimp and Excel.. by koreth · · Score: 4, Insightful
      If the aim is to replace commercial software with 'free' software
      Which it isn't for a lot of OSS developers; the aim is to have software that does a particular job well enough. If other people find it useful too, great. If other people find it so useful that they can avoid purchasing a commercial software package or two, that's nice too. But if not, that's also fine; they're welcome to stick with the commercial packages, no harm done.
    8. Re:The difference between The Gimp and Excel.. by Mark_Uplanguage · · Score: 2, Insightful

      Please mod parent up. Please use the right tool for the right job. If all you want to do is create circles stick with MSPaint or MSOffice/OpenOffice or Inkscape (highly recommended). If you want to do Photoshop stuff, use GIMP. If you want to disagree - fine. If you want to understand see http://gimp.org/about/ and read the threads about what the developers were trying to accomplish. Drawing circles was never on the list. Peace

      --
      "The difference between stupidity and genius is that genius has its limits." -- Albert Einstein
    9. Re:The difference between The Gimp and Excel.. by nick.ian.k · · Score: 2, Insightful

      Balderdash. It's got nothing to do with the success or failure of OSS. Rather, it's a general problem that plagues the application software industry and lowers the productivity of the hundreds of thousands of people out there using the wrong tool for the job. Look, you might be able to pry a crate open with the other end of a clawhammer, but it's a hell of a lot less effective than a crowbar: you're going to break a heavier sweat because you've got less leverage, the prying end is the wrong shape, and you're probably going to bust the crate to pieces with the hammer; use the right tool and you're done in a shorter amount of time, have exerted a hell of a lot loss effort, and you can reuse the crate. Similarly, you can use a butter knife instead of a flathead screwdriver, because they're vaguely alike, but there's no arguing that one approach is right (efficient, won't strip the screw) and the other is 100% hamfisted and should only be done in the case of an emergency situation where the appropriate tool isn't available.

      The primary motivation in having a huge, over-reaching featureset in a proprietary application seems to be to justify the (usually) ungodly charge for the end user license. This doesn't work so great, however, because it means the developers have to create said feature and try to integrate it into the package. This means their employers either have to compensate them accordingly so that the extra features work really well, or be satisfied that the feature is there enough to list in on the box or in marketing materials; as such, the price either goes up or the company allows itself to take a loss in not charging extra or shipping a product with sub-par features. In any event it's a real bitch to integrate limited functionality for a particular task that goes beyond the scope of the application without it seeming half-assed, incomplete, or confusing the real purpose of the application. This is why you see people doing things like using Photoshop for page layout or Excel in lieu of a database; the results speak for themselves.

      This whole Swiss Army Knife approach for *complex applications* needs to be nipped in the bud, and that's in both proprietary and free solutions. Anything less is accepting the approach simply because of precedent and ignoring evidence to the contrary.

    10. Re:The difference between The Gimp and Excel.. by femto · · Score: 2, Insightful

      It's a difference in philosophy.

      The philosophy you describe is the "bloatware" philosophy, where a single tool (program) tries to do everything. What happens is the program starts off not being able to do anything, it then grows to do something well. As circle drawing and shopping list features are added it grows to become unwieldy. Eventually it becomes unmaintainable and falls into decay, at which point someone starts a new project to write a "simpler tool". This bloats and the cycle repeats again forever. It's ideal if your aim as a developer or company is is to keep yourself in a job and make money for life.

      The Unix approach is that one tool does a single job and does it well. For example: tar bundles mutiple files into one, compress makes files smaller and gimp does photo editing. Indeed under the Unix philosophy, gimp should really be seen as a graphical user interface wrapped around a bunch of other tools. One tool might do thresholding, another might do convolutional filtering and so on. The idea with the "one tool one job" philosophy is that each tool gets written once and is simple to maintain and upgrade. Whenever that job needs to be done a program calls the relevant tool rather than trying to do a mediocre job itself.

      The unix approach is IMO the better. It leads to less needlessly replicated effort and gives higher quality results. Modularisation is one of the fundamental tools of computer science, used to reduce complexity to the point where a persoan can handle it.

      Asking gimp to draw pictures is a bit like asking a plumber to paint your house and expecting a first class job of it. It's just not gimp's job to be a drawing package. If you want a drawing/photoediting tool maybe the right way is to write a new supertool, which does its work by calling gimp and inkscape, rather than trying to make gimp and inkscape do each other's job? You as the customer gets what you what, and gimp continues to do its job well.

      Note: The customer might be allowed to demand a result, but I contend that the customer has no right to dictate the method of arriving at the result. That is for the experts. For example, if the customer wants a drawing and photoediting program the customer has no right to demand that the solution be provided by modifying gimp to do the job.

    11. Re:The difference between The Gimp and Excel.. by Blakey+Rat · · Score: 2, Informative

      Yes, but in graphics editing, you can get the best results by combining vector (draw) and bitmap (photo manipulation) in the same document using different layers. Otherwise, vector-only apps are crap with bitmaps, and bitmap-only apps are crap at dealing with vectors. The best way of handling this in this case is to have both in the same application, which GIMP does not do. (But its competitors do.)

    12. Re:The difference between The Gimp and Excel.. by Waffle+Iron · · Score: 3, Interesting
      They do?

      Of course they do. I've used the GIMP off and on over the years, and I wasted quite a bit of time searching for circle/rectangle/etc. tools before I came to terms with the idea that someone would bother to write such an elaborate program and leave those simple features out.

      So what it's a photo manipulation program: people need to stick circles and rectangle into photos sometimes. The menus are already cluttered with dozens if not hundreds of obscure tools and scripts. Surely adding a set of shortcut commands to do a very common basic task in a non-ass-backwards fashion wouldn't make the clutter significantly worse.

    13. Re:The difference between The Gimp and Excel.. by MobileTatsu-NJG · · Score: 2, Interesting
      Why does everyone want to use GIMP to draw with, given that it's a bitch and a half to do so, and the developers refuse to add it in? I suspect the answer is "because you can in photoshop!" Is inkscape really that bad?


      "Because you can in Photoshop!" is synonymous with "I'm more productive in Photoshop." I am not a 'painter' in Photoshop, but I use the paint brushes on a daily basis to generate textures. If I had to run out to another app just to paint a mask, not only would I lose a great deal of time, but I'd also lose all the benefits that Photoshop provides for me. Paintbrushes can be used for darned near anything. Inkscape could be the best drawing app in the world, it'd still be a huge PITA to not have those features integrated into GIMP.

      Answers like "use a drawing app!" only hurt the users, especially when it's been proven to work so well in Photoshop.
      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

    14. Re:The difference between The Gimp and Excel.. by radtea · · Score: 2, Interesting

      In this case, people editing photos very rarely have any need for drawing circles,

      One of the tasks I perform with the GIMP is annotation of photos--you know, the kind of image that no one ever sees anywhere that has a particular feature circled with some text describing what it is, and maybe a line connecting the text to the circle.

      I'm sure I'm the only person on Earth who ever has to do this with any photo so I guess I can completely understand why "people" never what to do this.

      But I do, and the GIMP makes it a great big pain in the ass.

      --
      Blasphemy is a human right. Blasphemophobia kills.
    15. Re:The difference between The Gimp and Excel.. by QuantumG · · Score: 2, Insightful

      You, like The Gimp developers, have absolutely no concept of UI design. Providing simple tools for common tasks and leaving complex tools for advanced users is a fundamental element of good UI design. Sigh.

      --
      How we know is more important than what we know.
    16. Re:The difference between The Gimp and Excel.. by QuantumG · · Score: 2, Insightful

      That's the usual argument given by The Gimp developers. Drawing a circle is a perfectly reasonable thing to expect a bitmap manipulation program to do. Especially seeing as every other bitmap manipulation program does it.

      --
      How we know is more important than what we know.
    17. Re:The difference between The Gimp and Excel.. by kcbrown · · Score: 3, Insightful
      I see your "the customer is always right" cliche and raise you one "use the right tool for the right job".

      Can you cut and paste from Inkscape into the GIMP?

      No?

      Then STFU about "the right tool", because the right tool or set of tools that gives you the combination of features you need doesn't exist in the Linux world. And until that changes, people are right to ask for easy-to-use drawing functionality in the GIMP.

      And even if it were possible to cut and paste between Inkscape and GIMP, there's another reason they're right to want easy-to-use drawing functionality in the GIMP: because it's not uncommon that you'll need to perform some drawing on a photo or other complex image, and using another program for that isn't possible because the nature of the drawing operation requires that the drawing dimensions be taken from the photo itself. That's trivial to do if the drawing functions are in your image manipulation program, and difficult to do if they're not.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    18. Re:The difference between The Gimp and Excel.. by Overly+Critical+Guy · · Score: 2, Interesting

      Maybe someone should clue you into the fact that drawing a circle also counts as manipulating an image. Hey, if GIMP doesn't want to provide braindead basic features that every basic user would need every day, that's fine. But don't expect any respect in return.

      For crying out loud, you're actually arguing that providing a simple circle primitive tool is UI clutter. It's this kind of dismissal of user demands that has cause so many people to turn against GIMP. "You just don't understand what the focus of the program is, therefore your needs don't matter. Go use something else and don't clutter my interface." Yeah, and fuck off to you to...

      --
      "Sufferin' succotash."
    19. Re:The difference between The Gimp and Excel.. by Jesus_666 · · Score: 2, Insightful

      However, the Unix way of using small tools that perform one single function only works so well because you have easy communication between those tools. Imagine you could not pipe one program's output into another program - every single nontrivial task would require you to juggle temporary files.

      However, that's the situation with graphics editing. The GIMP has no vector editing capabilities worth mentioning, but it's good for raster images. Inkscape does vectors but not it's not good for raster stuff. The Unix way would be to combine them, of course.

      There is no direct communication between the programs, but if there was copy and paste support between them we'd at least have something resembling easy communication. But in fact if you want to create a somewhat complex vector/raster image you have to do all raster editing in the GIMP, then save the stuff to (a) temporary file(s), then import the file(s) in Inkscape. You can't tell how a vector edit looks in the image until you have exported that "layer" to Inkscape. That's not the flexibility of a Unix shell, that's using no pipes and one command per line - in other words, completely inadequate. Thus, there is no decent way to use the GIMP if you want the image to have a vector component.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  4. Re:Maybe now the UI by QuantumG · · Score: 2, Funny

    Yeah, like Blender has improved.. oh wait.

    --
    How we know is more important than what we know.
  5. GIMP needs fresh developers by Speare · · Score: 5, Insightful
    GEGL was first proposed in 1999, but the GIMP's existing code base has remained in place over several revision cycles since then. As recently as summer 2005, GEGL appeared for all practical purposes dead in the water.

    I see this as a confirmation of the stagnant GIMP developer pool, led by a few who are not interested in growing that community at all.

    If the GIMP team would foster new blood, help new hackers learn the large and intimidatingly complex codebase, give any other reply besides a gruff "you want it, you code it" response to any artist who dreams of a good core feature, give specific progress feedback about modern image demands like 32bits-per-channel, CMYK, or fully functional ICC, then maybe we'd see a real alternative to Photoshop in the OSS world, not a Photoshop 1993 clone.

    The only other path is "fork it," but with any complex project, it's very tough to fork away from the few experts.

    It's clear the GIMP captains still see GIMP as a pet project, just as some major tech news sites see themselves as a pet blog, and refuse to take on the responsibility of being a leader or even trying to become a leader.

    --
    [ .sig file not found ]
    1. Re:GIMP needs fresh developers by swillden · · Score: 2, Informative

      If the GIMP team would foster new blood, help new hackers learn the large and intimidatingly complex codebase

      Look at the GEGL web site. They provide pretty good support for new developers interested in helping, and the IRC channel is pretty friendly.

      Hopefully this announcement will generate some interest in GEGL, and provide some new blood in that project. And since lots of work has already gone into preparing the GIMP for the new engine, things should move very quickly in the GIMP world once the new engine is in place. The new architecture will make GIMP development much more accessible, too. In spite of lots of cleanup work, the existing codebase is very crufty, which is a lot of the reason it's hard to understand.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:GIMP needs fresh developers by Trogre · · Score: 2, Insightful

      Agreed. The terrible way they handled the FilmGimp/Cinepaint fork should be enough to convince anyone that the leadership does not have its users at heart.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  6. Re:Maybe now the UI by swillden · · Score: 4, Insightful

    Maybe now he can give The Gimp a decent UI instead of the trash it's had for the last 10 years

    In the first place, the GIMP's UI has changed a great deal in the last few years, so much so that it doesn't make much sense to call it one UI. Second, the GIMP's current UI is very powerful and very usable. Personally, I prefer it to Photoshop's UI, mainly for the ease with which it can be customized to fit exactly the thing I need to do right now. Then, later, when I'm doing something different, I can flip a couple of hotkey assignments, tear off a different menu or two, and have a UI that is perfectly suited to what I need at that moment. For those who know it well, the GIMP's UI rocks. Much like PS, actually. The biggest difference is that there are a lot more people who know Photoshop's UI well.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  7. Gimpshop! by BeeBeard · · Score: 4, Informative

    Ahem:

    Gimpshop. It's a great attempt at making The Gimp more comprehensible to people with a Windows/Photoshop background. And like The Gimp, it too is free.

    1. Re:Gimpshop! by QuantumG · · Score: 2, Insightful

      But its a fork. If we have to fork The Gimp every time we wanna do something that the current people with power over the source code repository don't like, all we're going to do is fragment the userbase. That divides our community, causes wastage, and disgruntles developers.

      --
      How we know is more important than what we know.
  8. Yes, it is forked up by BeeBeard · · Score: 2, Insightful

    Yes, good point. Forking isn't always the best way, but it does demonstrate the power of determined people to turn open source products into exactly what they want or think other people want--for whatever that's worth. I mean, next thing you know, we'll be forking Firefox because of its logo. Hmm bad example...

  9. Oh, for the Good Old Days... by ewhac · · Score: 2, Insightful
    Call me a retrograde philistine, but I'm still pining for a functional equivalent to Deluxe Paint.

    Schwab

  10. modularization is the key by voisine · · Score: 2

    I think as various parts of gimp are better modularized and seperated, which is the direction things are moving, you'll see more progress. This is similar to the path that mozilla took. They abstracted out the rendering engine and then other projects are able to make clean fast native ui's on top of it.

  11. Re:Maybe now the UI by raddan · · Score: 2, Insightful

    The problem is that the GIMP's UI is not consistent with any other UI I've ever come across. Sure, it's probably easy-to-use once you already know it. But why not make it the same as other apps? Photoshop, among many other apps, has a bounding window-- this helps keep your workspace organized. Photoshop has palettes that actually float, instead of getting lost behind numerous other windows. You don't have to navigate through menu hell just to apply a filter. And so on. I'm sure these points have been flogged to death on lists before, but IMHO, until the GIMP changes these very simple UI items, most graphics professionals will stay away. Which is too bad-- the GIMP is otherwise a great program.

  12. Re:Maybe now the UI by swillden · · Score: 4, Funny

    The problem is that the GIMP's UI is not consistent with any other UI I've ever come across. Sure, it's probably easy-to-use once you already know it. But why not make it the same as other apps?

    Because all of us who know the GIMP would then have to learn a new UI.

    ;-)

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  13. ØØØØØØØhhhs and by BeeBeard · · Score: 4, Funny

    Pardon my American sensibilities, but I like Øvind Kolås based solely on the difficulty of typing and pronouncing his name. Woo woo alien character set!

  14. Re:Why I'm not satisfied with Gimp by Blakey+Rat · · Score: 2, Informative

    Are you using MS Paint? Or Paint.NET? PLEASE tell me it's Paint.NET... once you tried that, you may find that you don't miss GIMP at all.

  15. Re:Why I'm not satisfied with Gimp by Bagels · · Score: 2, Informative
    What I want is a program that is as intuitive as MS Paint and lets me create in 3-D.

    You're wanting Sketchup, then, I think. For creating in 3D, that's about as intuitive as it gets.

    --
    --- Bwah?
  16. Re:Drawing layers and bitmap layers in one documen by QuantumG · · Score: 2, Interesting

    Integrating The Gimp and Inkscape would be interesting.

    --
    How we know is more important than what we know.
  17. Gtk for Mac by ghutchis · · Score: 3, Informative

    I haven't used it myself, but it's certainly for real (as in, contributed code back to the gtk trunk)

    http://developer.imendio.com/projects/gtk-macosx

    Cheers... -Geoff

  18. Re:Why I'm not satisfied with Gimp by Nicholas+Bishop · · Score: 2, Informative

    Hiya, I happen to be the developer of SharpConstruct. SharpConstruct is no longer under active development; I've been moving the source code into Blender over the summer (Google Summer of Code 2006) and the sculpting tools will probably be in the next version of Blender. I don't plan to develop SharpConstruct any further as an independent app.

  19. Re:Maybe now the UI by Ferzelic · · Score: 2, Insightful
    Photoshop, among many other apps, has a bounding window-- this helps keep your workspace organized.

    I personally prefer to the fact that I can access all the windows I need the same way -- from the task bar, or by alt-tabbing. Once I'm in an MDI application, I have to change to its window-switching method, and identify what documents I have open in a different way. If I've got a maximized document in most MDI applications, I have to minimize it or go to a menu to see what else is open.

    Excel 2003 actually has the worst of both worlds. It's an MDI application that pretends to be an SDI application, with its default maximized documents. Each document shows up in the task bar, but if you do the logical thing and close the current window (instead of the subtle and nonstandard 'document close' button below it), it closes the whole application instead!

    Photoshop has palettes that actually float, instead of getting lost behind numerous other windows.

    I have a dislike for permanent floating palettes, particularly when working with images. In MDI apps I tend to work maximized, as the document frame clutters the already limited space. This means palettes are floating on top of the page I'm trying to draw on -- and unless I'm zoomed in, I often can't pan the page past them. I have to keep moving palettes around, or close them entirely (and then have to go menu hunting when I want them back). The GIMP lets me bring the document in front of the palettes when working.

    There are however plenty of legitimate complaints about the GIMP GUI, but they don't seem to be the ones people usually make. It's insistence in popping up operation windows (scaling, cropping, filters etc) in front of the image, for example. I've already got a Tool Settings palette docked under the main palette; they aren't modal prompts, so why can't these things be shown there? (It looks like the development version is looking at this, but they've made some other annoying decisions, like overloading ctrl, alt & shift during selection. I'll be providing some feedback on that front...)

  20. What about the User Interface? by filesiteguy · · Score: 2, Informative

    I think GIMP is a fantastic cross-platform photo manipulation tool. I had been using and advocating it for awhile now. In fact, all the logos on my sites were done with the GIMP Script-Fu routines.

    HOWEVER - I am still sick of the horrendous UI that is presented to me. No matter how many times I argue with the developers and the "holier than thou" Gnome community, I cannot see their reasoning for a trashy un-comforting UI. Make a MDI interface and they will come. I see no reason why they couldn't have a two-option interface. SDI for the really geeky people and MDI for us normal users.

    GIMPShop was a nice step in the right direction. Now, fix the bloody UI and the File Open/Save dialog (talk about garbage!) and you'd have a decent app.

    Oh, wait - Krita is out. Oh - it doesn't work on Windows, and I still use Windows once in a while. Bummer.

    Okay, guys, mark me down as a troll. I've said what I feel. GIMP could be a great tool, if only the developers would get off their respective high horses and listen to us normal users.

  21. Major reason why GIMP will not replace Photoshop by pjludlow · · Score: 2, Informative

    I have a degree in graphic design. I currently work at a photography studio doing Photoshop work full-time. I've used Photoshop for around 10 years now. That is my background.

    Let's assume for all purposes that GIMP can do everything that Photoshop can do (yes, I know it can't). For me to learn the GIMP UI and become as proficient as I am now in Photoshop would take some time. If it took me more than 8 hours (which is pretty much assured) then it makes no sense for me to use GIMP. I could buy a Photoshop upgrade for less then the productivity time I lost learning GIMP. Even if I had to buy a full new version the time lost learning the new program would be more and would actually cost me quite a bit. Although GIMP may appear to be be free, it really is not to anyone who uses a image editing program such as Photoshop to make a living. It may be great for the hobbyist, but not for the professional.

  22. Total Bullshit by Nicolay77 · · Score: 2, Insightful

    I use Paint Shop Pro 9 and I sometimes have to use both things, shape drawing tools and photo manipulation tools in the same file.

    The shape drawing tools adds what... One button to the toolbar? And are easy and intuitive to use.

    Having said that, I like the way you describe Gimp doing the same task, as long as I can edit the circle properties at any time afterwards, like stroke width and color.

    --
    We are Turing O-Machines. The Oracle is out there.
  23. Gimp's problem are ideological by wysiwia · · Score: 5, Insightful
    I'd love to hear specifically what is missing, as I'm sure the devs would too.

    I don't think the developers really want to know, else they would have responded long before since I've already told it several times. While the graphic drawing power of Gimp isn't disputed, Gimp sports the most uncommon GUI an application could have. This (and only this) GUI leaves a bad taste in the users mind so they start looking for other minor annoyances one finds in any application if looked for. Yet since most users a pre justice because of the bad taste they won't forgive any other annoyance.

    This is all known in the Gimp community yet they don't want to acknowledge this simple fact but prefer to discard this as a flame bait. So it's now wonder Gimp gets flamed at all the time, rightfully or not. On the other side it's incredible easy for Gimp to drop off this flaming, they simply should change their GUI to the one outlined in wyoGuide (http://wyoguide.sourceforge.net/). All it needs is some willingness on the Gimp side and a little work. It might be that wyoGuide isn't the best but it certainly is good enough for Xara (http://wyoguide.sourceforge.net/projectlist.php) and many other fine applications.

    You see Gimp's problems aren't technological, they are ideological.


    O. Wyss
    PS. You are free to rate this as flame bait but that won't help Gimp.
    --
    See http://wyoguide.sf.net/papers/Cross-platform.html
  24. Re:Major reason why GIMP will not replace Photosho by PitaBred · · Score: 2, Interesting

    Let me tell you a little story, a story about the little school kid who used Gimp (which was functionally equivalent to Photoshop) while all his buddies used Photoshop. When they all become professionals, the Gimp user still has free software, updated regularly for free, which is very powerful and useful. The other kids all use Photoshop, which is expensive, updates cost a lot, and it's not as easily scriptable, nor are the developers as approachable for feature requests. Who is wasting more money keeping their technology up to date now?

    What you're bitching about is that you're basically too lazy to learn something new, because different is bad. Still using an abacus to calculate your finances, because them newfangled calculators use numbers, and they aren't what you're used to and it'd take you more time to learn how to use 'em?

  25. Re:Gimp UI and how it could be even better by CandyMan · · Score: 3, Insightful

    I too like the GIMP interface in many places, and use it exclusively for retouching my photographs (professionally published, as for instance in the Spaish edition of Rolling Stone). I export my results to a Photoshop .psd file, including a layer with the untouched photo for the editors to have a reference of what came out of the camera, and I send it to the photo editors. I don't miss CMYK or colour matching because, you know, they have that at the magazine.

    However, it would be good to have a completely tweakable interface. I have already commented somewhere that right now many 3D modeling apps are configurable to work like other apps, and that you have a vi mode for Emacs and Emacs bindings for vi, and nobody finds it strange that people like it that way. Problem is, vi and Emacs are used by coders, and coders can build their damn interface themselves. Most users of GIMP (and certainly most advanced graphics manipulators) can't. But they are right in saying they work better the way they do. Users are not idiots, and they know how they work better. What we need is not really "reskinning the Gimp, and more", but just the ability to tweak what really matters to you.

    Not all features are equally important, or used equally frequently. Right now one can reassign shortcuts and move menus around, but modificator keys (keys that act as a "shift" to active tools) are still hard-coded, or were last time I looked. (Caveat: I haven't tried to configure it in a Photoshop way in a long time, as I am already used to the GIMP's UI, so I don't miss Photoshop's that much).

    The thing I would love to have in GIMP is the space-alt-ctrl trio of modificators to invoke the hand tool and the zoom-in and zoom-out tools while in any mode. This is so powerful a way of working that I am almost religious about it, despite having retrained my muscular memory not to hit the spacebar with my thumb every time I want to readjust the working area. Also, later versions of Photoshop has evolved really nifty docked option palletes for tools (like the search feature in Firefox) that I haven't really used (as I am now a GIMP user), but they look fantastic.

    Finally, some of us liked the MDI interface behaviour: sometimes, when you are editing photos, it is all you are doing (see below for single-app computing), and the focus behaviour of Photoshop is much saner than the Gimp's in many places. I know this is not the Gimp but the X11/WindowManager combo that provides window management; maybe what some users need is a PhotoGimpWM.

    Contrary to popular Slashdot opinion, some of us who ask for certain Photoshoppy-features in Gimp don't want a clone of Photoshop. What want is the ability to really customise the way we work in a Photoshop-like app (and, like it or not, Gimp is Photoshop-like, see below) in the features that matter to us. Other people would like a Gimp preference option that adds a complete "behaviour" of the most-used and learned photo editor in the world. Think PhotoGimp on steroids, and if I were a coder working on the Gimp (sadly I am only a punter), this would be my first feature to add for propietary-software refugees' sake. Free Software being coded by volunteers, we can't make them do what we want... but that doesn't make our needs and wishes irrelevant or wrong. Just unenforceable ;)

    I have worked in TV with people using the Quantel series of graphical pallettes (concretely the superb HAL), and their gestural interface had nothing to do with Photoshop and Gimp's WIMP paradigm. However I would love the Gimp to have support for its dedicated clicker [note] for my left hand while I work with the pen in my right hand. I wouldn't mind to try the HAL's gestural interface either: it seems like a right timesaver, although I don't know how it would fare in a multi-purpose computer running other programs at the same time. In non-windowed environments where the only thing running is the graphics editor, however, gestural interfaces to be the right thing for bringing up pallett

    --
    http://barrapunto.com/ - News for nerds, en español
  26. patented and otherwise non-free technologies by BigSven · · Score: 2, Informative

    GIMP explicitely allows non-free plug-ins and the main reason for doing that is to allow such technologies to be added. Someone just needs to do it.

  27. Re:Gimp UI and how it could be even better by BigSven · · Score: 2, Informative

    Yes, you can use a gamepad with GIMP, assuming that a driver exists that makes it available as a Linux Input device. Otherwise you could also write your own GIMP input module. That's a pretty small well-defined interface and there's example code that you can base your module on.

    On a related note, see ahref=http://gimp.org/unix/howtos/gimp-midi.htmlre l=url2html-27183http://gimp.org/unix/howtos/gimp-m idi.html> for a HOWTO on controlling GIMP with MIDI devices.

    Gestures might be a nice idea for the future. Perhaps you want to try to come up with a more detailed proposal on how this would work?

  28. Re:Why I don't use the Gimp by Ant+P. · · Score: 2, Informative

    The GIMP:
    1. Use one of the selection tools to select an area.
    2. Use the fill tool to fill the area.
    3. Shrink the selection.
    4. Delete the contents of the selection box.
    5. Write text using text tool and style it appropriately.
    6. Adjust colors / transparency.


    Looks like you've been reading bad instructions.
    1. Draw shape using appropriate selection tool.
    2. Choose whatever paintbrush tool and options you want the shape drawn with. (optional)
    3. Edit -> stroke selection.
    4. Write text using text tool and style it appropriately.
    5. Adjust colors / transparency.