Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
The Gimp

Gimp 1.2 Preview 65

Lunglet writes "There's a nice preview of the features Gimp 1.2 is probably going to contain over at " So many things to compile and segfault... so little time. The new path stuff especially looks sweet as hell.
This discussion has been archived. No new comments can be posted.

Gimp 1.2 Preview

Comments Filter:
  • GEOPaint on Commodore 64 GEOS! 300-something by 100-something black and white windowing, using a cheap joystick for a pointer..

    It would take five seconds to cross the screen!
  • by Anonymous Coward
    Any word on when the Gimp will get a photoshop-like interface like the Kimp? I think the interface is unduely giving the Gimp a bad name.
  • Wow, I work at one of the country's largest pre-press companies...doing packaging and ads for major clients and advertising companies and we never use seperation tables in our color corrections.

    We use straight Photoshop (I'm in the PhotoMac department) and ArtPro, Illustrator and Quark...all standard packages running on standard Brisque RIPS. Now, we have special curve functions on the Brisques when we make final films (or if everything is going to the CREO direct-to-plate process...which is a whole other can of worms), but we don't use anything special on Photoshop.

    Which leads me to think that The Gimp could in fact get CMYK support without having to sell the farm to get it. But I could be wrong because I'm not on the development end other than doing beta testing and stuff like that. I'm not a programmer or have any idea how hard it would be to implement CMYK or other color spaces to a program.

    I remember when Photoshop didn't do CMYK...then only did it as a save function (couldn't work directly in it), then finally a full CMYK version. So I can only guess on how hard it was for Adobe to program all that in there. Before that, we used ColorStudio...which went the way of the dinosaur after Photoshop got CMYK. But I digress...
  • by Anonymous Coward
    filter factory filters are already supported under gimp from what i've seen, or you can easily port the code even if you don't know an ounce of code via the custom plugin.

    since filter factory comprises the vast majority
    of plugins, i'd say gimp's off to a good start.

    as for comercial stuff like
    kai's power mean tools
    , i guess we shall have to wait and


  • Yeah, I did read something about it in a book
    called Printer's Pal or something like that but...
    Isn't Photoshop or whatever supposed to be able
    to do CMYK? How does that work?
  • So the only thing I miss from the GIMP as it stands now is polygon/ellipse/rectangle drawing tools. Paths are nice, and I'm glad they've been added... but I'd really like to be able to just draw a circle.
  • CMYK support. I believe that this is the biggest hurdle in the way of GIMP being adopted as a widespread alternative to photoshop right now.
    (I suppose I could always sit down one day and code it myself, I guess, but really it'd be better for all concerned if it was done by someone who could actully wasn't stupid :)
  • It would be nice though if someone would try atleast to add support for photoshop plugins (emulation or whatever if necessary if they are win32 specific)
  • kimp won't happen unless a free qt is ever released.
  • The problem still remains that Qt 2.0, while free, isnt GPL compatible, which means that all authors have to consent to a license addition to allow linking against Qt.
  • Is there such a thing as "Kimp"? I don't think so. Work has just started on KImageShop which will use the ImageMagick libs.

    I agree that although Gimp is a great program, its interface is really holding it back.
  • > Rumours has it that they will begin making the Gimp core toolkit independent

    It's kind of ironic, when GTK stands for Gimp Tool-Kit. It'd be nice to have the choice.
  • HAM being based on encoding was almost like lottery. You draw and wonder when color will change or stuff like that. Neverthless it was usefull for images and like. Good old days ...
    ( I still ocasionally use Deluxe Paint under DOS ..)
  • This likely falls under stupid questions, especially since I don't have GIMP (what with not having X), but how is GIMP allowed to support the .gif format? The GNU website [] says that it can't be done, since IBM and Unisys hold the patent for LZW compression.
  • What's this 'Preview Month' you're talking about?

    The Gimp development has always been open to the public. At some time less than at other times, but CVS has always been open to the brave ones. If you want to stay in touch with development I strongly advice you to play around with the Gimp releases or to pass by on

    And, yes I'll update that site tomorrow to reflect the fact that 1.1.6 has been released.
  • by scrutty ( 24640 ) on Sunday June 06, 1999 @08:09AM (#1864797) Homepage
    1)Right Click on image

    2)Filters -> Render -> Gfig

    3)Select New and then draw a circle or any other polygon that takes your fancy
  • Rumours has it that they will begin making the Gimp core toolkit independent. This should make it easier to port to KDE/Qt and Windows. There are some KDE developers who are interested in porting to KDE.
  • Looks sweet. I will have to get it right away. The 1.1 devel series was pretty nice, damn instability was the only problem. I like the gimp more than photoshop now after ive used it so much.
  • Um... I used DeluxePaint IV + PersonalPaint 7 on the Amiga for years (HAM mode was really wierd, wasn't it?). I really like GIMP, and I use it for retouching/compositing raytraces, photos, and the like, but for pixel-painting, I miss the DPaint-style interface. The GIMP (and Photoshop) though undeniably more powerful really, feel much more "clunky" (IMHO) for pixel work onto a blank bitmap, like (euro)demo pics... Also, the DPaint IV animation stuff was really good.

    So what's my point?

    Ideally, I'd like to have an alternate UI for the GIMP engine. Seems to me an implementation of the dpaint interface, interfaced through script-fu, that worked on a single layer, or even a UI that "felt" like DPaint, but had support for GIMPy features, would be possible. I was just wondering if a) one exists and I've missed it or b) if there would be any demand beyond myself for such an alternate interface?

  • AFAIK, CMYK support is one of those patent minefields. In that case, you won't be seeing the gimp support CMYK any time soon...
  • No, it's not out yet, the article was a _preview_. So you'll have to stick with 1.1 for a while.
  • Being an avid Photoshop user, I was tremendously impressed with the Gimp version that came with Slackware 96 when I first started using Linux (I forgot the version release). I have since convinced friends of mine (Other Photoshop users) to take a look at that version of Gimp, and they were impressed as well. (Not only by the features, but the price tag as well.)

    This new release looks great. While the older releases were excellent, they were thirsty for the features that have now been implemented. (Such as the improved "New Image" window, Brush Adjustments, etc.) I've switched to using Gimp for my image needs, because the feature set of the Gimp matches, if not defeats Photoshop. The interface tweaks in the new release of Gimp help out a lot (it took a bit of searching to find the menus in the older one). And it doesn't cost $600 to have the privelege of using it. :)

    Peter, Spencer, Thanks for this wonderful software.

    -- Give him Head? Be a Beacon?

  • by Anonymous Coward mp.html
    User Filter will allow you to use Photoshop "filter-factory" plug-ins.
  • Well, one needs to have a color separation table which maps the RGB input to CMYK output, plus one needs to ``screen'' the image which is to say convert it from transparent blocks of light (pixels) to opaque-semi-transparent dots/areas of ink. This conversion must also include information on how to handle colrs which can be shown in RGB, but are ``out of gamut'', which is to say, not printable with four-color process printing.

    Screening isn't the biggest block, since that's typically done by a PostScript RIP, but the conversion into CMYK is.


  • Try Satan Paint. It may be just what you are looking for.

    Find it at: aint.tar.gz

    (maybe... could be an old link.)
  • by Analog ( 564 )
    IIRC, it was version 0.54 or somesuch; based on Motif, not GTK (which I think you are correct about not being around yet).
  • I thought the Gimp followed the photoshop interaface pretty closely. A friend of mine who uses Photoshop a lot noticed the considerable similarites betweent the two programs. What kind of functionality are you looking for in a KDE version of the Gimp anyway?

    On a side note, ImageMagick needs some serious work on its interface. IMHO it needs to behave with Windowmanger options like focus-follows and autoraise before I can consider using it. Whenever I try to select something in that dialog box, it autorases whatever window is below it, which obscures not on the control panel, but the main window as well. Very frustrating, especially if you are going back and forth between that window and ImageMagick. On a final note, ImageMagick seems slower than the Gimp in most operations (save starting up).
  • This probably isn't worth the trouble. For all the effort that would be extended we could have native versions of the best plugins.
  • Is there some good documentation, a good book or
    website that really explains well CMYK vs RBG?
    Sometimes the hardest part of writing a piece of
    software is getting a good spec.
  • Yup. One thing that keeps GIMP from being truly usefull is its rather unusuable interface. I wonder why don't they change it - I mean, in this kind of programs it interface is half the success.
    Even GTK programs are getting better and better every day ( IglooFTP looks very nice .)
  • ...since it's the version that will have support for 16-bit images, and I could _really_ use that. Think scientific imaging.
  • I thought it might simply involve ignoring patents. Good work, then. If I ever put together a Linux box with a HDD greater than 130Mb, I'll try out X and GIMP. But I'll be sticking with a GIMP that does .gifs, because I'm a web designer, and as much as I appreciate the added features of .pngs, customers tend not to when their horribly outdated browsers can't display them. Ah, the fun of the lowest common denominator.
  • 1. Select the surface around which you want to draw, using the circular selection or whatever.

    2. Use Edit->Stroke in the menu.

    This will stroke around the current selection.

    Everybody, including Gimp developer, has seen that it is an unduly convoluted way to draw a circle and that many would-be users simply think you can't draw circles. A more user-friendly interface is being worked on.
  • You might try doing it with gradients, too, using the shape-following options of the fill tool (can't remember their names, but they're there). That'll let you make your circle with whatever kind of border you want!
  • I'm replying to myself, because I only want one reply here...

    I did not know that.. Thanks!

    ...all I wanted to say. :)
  • I second and third that one! I can only imagine that SGI has some unreasonably strict patents on their onscreen menus to stop the rest of the world copying them...

    Oh, and I quite like the GIMP interface too, though it'd look a lot better if I had a bigger monitor!
  • To reply to your reply, I must disagree. Photoshop is a very nice program (although I think 4 is superior to 5, with the exception of the magnetic lasso tool), however, it took time to learn it, no? If you learn how to use Gimp, and use it efficently, you can do it in the same amount of time as Photoshop.

    -- Give him Head? Be a Beacon?

  • first, make the dialogs customisable, and make it so that you can bundle and pair them anyway you want (yes, like photoshop)

    Yes, this would be cool. I'm sure such patches would be gladly accepted.

    And yes, as someone else mentioned earlier this does stink for people of small resolutions

    Well.. if you really work on graphics you need a bigger screen no matter what program you happen to use. The images alone need space :)

    thirdly, why not have "always on top" functionality for them?

    This is more a windowmanager thing. You can configure any windowmanager to do this for you.

    but what the heck is that ugly yellow and black border around my image?

    That is the layer border, you can turn it invisible with Ctrl-T. Visible borders are handy if you have layers that are smaller than the image.

    gimp is one step ahead with it's menus though, i have to say that. having everything off the rightclick menu is somewhat nice, so that i don't have to travel 5,000 miles across the screen every time i want something.
    ...might i add that the menus go too many sections

    Yes, I personally agree. The right-click menu is IMHO one of the best things in gimp - although it IS very deep. But blah, there are lots of plugins there that fill it up. I think that is a good thing. I dont find the menus SO hard.. You can always assign the dynamic shortcuts to often needed stuff (go to a menu and press a key combination like alt-z and see it getting assigned to that menu item.)

    And, after all, Photoshop on a Mac is not that different from Gimp interface, the 'one big mother window with all the stuff inside' is just an evil hack that windows uses because you dont have a virtual screen or anything like that.. I really dislike it. This is X. :)


  • Color separation tables are expensive to create and require a fingerprint of the press in question as well as an understanding of colorspace and theory.

    Here're some basic books on the subject:
    Blatner, David and Steve Roth. Real World Scanning and Halftones (Berkeley, California: Peachpit Press, 1993). ISBN 1-56609-093-8, second edition 0201696835.

    Nyman, Matties. Four Colors/One Image: Getting Great Color Output with Photoshop, QuarkXPress, and Cachet (Berkeley, California: Peachpit Press, 1993). ISBN 1-56609-083-0.

    Tapscott, Diane and Lisa Jeans, Pat Soberanis, Rita Amladi and Jim Ryan. Professional Studio Techniques: Production Essentials (Mountain View, California: Adobe Press, 1994). ISBN 1-56830-124-3

    I've links to Amazon to purchase these books on my web page at:
    (obligatory disclaimer, I'll make money if anyone does purchase through said links)

    My company spends ~$100,000 a year creating test plates for our customers to fingerprint their presses for color matching purposes. Like I said, it's expensive.


  • After this preview of Gimp 1.2 and that last The Future of KDE rticle, we should have a Preview Month every summer. It could be fun, finding out what the developers have been working on the previous year. Think of it like a holiday.


  • you're damn right!! and this is true not only for the Gimp, but for many other applications...
  • No. I am not just talking about the Gimp. I am talking about all the projects. I don't know of many people who have the time or the desire to go through all the projects, download from CVS, compile it, just to see whats gonna be around in a half a year. Articles like this are nice because, even though I am not an avid Gimp user, I still have an idea what's happening. Id like to see more preview articles like these.


  • by Anonymous Coward
    I have discussed with several Gimp authors about creating a KDE UI. Most core developers could care less about the GTK/Qt/KDE/Gnome debate and simply want to create the best software possible. There is a segment of those who feel the users would be best served by being able to select the user interface. Restricting choice is never good for the user. As far as a free open-source Qt you can download the Qt2.0 beta from

Porsche: there simply is no substitute. -- Risky Business