Slashdot Mirror

← Back to Stories (view on slashdot.org)

First Preview of GIMP 2.0 Ready for Testing

Posted by michael on from the my-precious dept.

molnarcs writes "The first preview of GIMP-2.0 is available. It can be installed side-by-side with GIMP 1.2 - so there is no need to uninstall 1.2 to test it. According to this README, some parts (gimp-perl and GAP) were removed from the main package, and will be released as separate modules. Use the mirrors listed on the homepage to download the source code. (Also available for FreeBSD via ports)." Apparently the GIMP is finally adding CYMK support, for those of you working in the print world.

5 of 563 comments (clear)

  1. Ready for printing? Don't think so. by AnriL · · Score: 5, Insightful

    Having CMYK support is all fine and dandy but it won't get you far in the printing world without support for colour profiles and colour calibration. Linux sadly lags behind others (Windows, MacOS) in this area, and having Gimp support CMYK is like fitting racing wheels onto a horse and shoving it onto the Indycar track ...

    Mod away...

    1. Re:Ready for printing? Don't think so. by Raphael · · Score: 4, Insightful
      Isn't native CMYK going to be in 2.0?

      No, the plans have changed last year. There was a debate among the developers about whether the next stable release should be called 1.4 or 2.0, and the decision was to call it 2.0. It does not have the native CMYK support (only export), but it has many other new features. Also, the internal structure of the program has changed so much that a major change in the version number was considered useful. Even if the end users do not see some of these changes, they are very significant for script and plug-in authors and the improved structure and documentation of the code should make it easier for new developers to contribute to the GIMP.

      A bit of background (if you are interested): after the GIMP developers' conference in 2000, the plans were to have CMYK support in GIMP 2.0. These plans for "the future of the GIMP" were published and were often refered to (in newsgroups, mailing lists and even here on Slashdot), until the middle of last year. At that time, the discussion started about how the new version should be called and it was decided to call it 2.0. This decision was confirmed at the 2003 edition of the GIMP developers' conference. Even if those who were expecting native CMYK in 2.0 will have to wait until the next release, I think that most users will be very happy with the new GIMP.

      --
      -Raphaël
  2. Re:Difficult to use or? by rusty0101 · · Score: 4, Insightful

    "The GIMP" (proper name include "The") takes some time to learn. You can use many of the skills you learn in using Photoshop, however getting to the tools you are familiar with is an exercise in creative thinking. The Interface is different, so if the tool you are looking for is (as an example) adjusting the gama for a layer, you have to navigate through different menus than you would under Photoshop, or PSP.

    Whether that makes it "harder" than the other tools is a matter of interpretation.

    The largest problem with learning The GIMP right now is that if you go to a bricks and mortar book store, you will be hard pressed to find a "Teach yourself" or "24 hours" type book, especially for the current version. There are tutorials online, and some of the techniques documented in earlier books (look at the online used books) are still useful.

    Photoshop has been around longer, and has more marketing muscle behind it because Adobe has earned quite a bit of money off the product. As a result of those two factors (and perhaps a dozen others I am not aware of) it is easier to find people willing to earn money teaching you how to use the product. If you drop over $200 on a piece of software, wouldn't you want to make sure you had some pretty good ideas on how to use it?

    The GIMP on the other hand is more of a play with this tool, and see what you can do, how about that tool, etc.

    Just my thoughts, others may think otherwise.

    -Rusty

    --
    You never know...
  3. Re:The problem with gimp... by Boing · · Score: 5, Insightful
    The problem with gimp...is its User interface... What happened to the MDI model.

    Someone responded saying the problem has been partially solved in later versions of gimp, with "docking" ability. But I think Photoshop and its imitators have shown that a true MDI workspace is ideal for image editing.

    For the story of why MDI wasn't adopted earlier, read the following:
    http://bugzilla.gnome.org/show_bug.cgi?id=7379

    Putting my own personal bias into it, attitudes like Sven's (for example, an exerpt from a message on 2002-12-10 08:31: "WiW is evil! Why do you want to put a large window all over your screen that hides everything but your application? Because your desktop sucks? Then get a better one.") are what I see as the big imediment towards adoption of open source. If someone in a commercial project vocally complained that the customers of that project wanted dumb things and that their environments were inferior, he or she would be fired.

    I understand that these people have given freely of their time to improve GIMP, but they also claim to want widespread adoption of it; something that won't happen if they establish a mental wall between their personal agendas and the desires of other users.

  4. Re:Difficult to use or? by MobyDisk · · Score: 4, Insightful

    Are you takign the course to learn image manipulation, or to learn the UI. If you are taking it for the UI, then no, it won't help. You will have to learn that on your own. To learn the tools - yes, you will have to translate that knowledge though. Allow me to give my experience as a Photoshop user moving to Gimp

    I find Gimp hard to use. The Slashdot & Linux community will say that it just takes "getting used to" but I suspect that is the same crowd who will tell you that applications don't need to look & act in a consistent manner. I think the cause is that Gimp uses a number of old-skool interface concepts that fewer and fewer apps use these days.

    Gimp uses the multiple-dynamic-windows approach, rather than the docking toolbar approach. This is the biggest headache, and probably the only one that it is impossible to "get used to." When you click on a tool, tool windows may appear, disappear, or resize. They may appear or resize right in front of another window that you need to see. Sometimes running a filter opens one or more windows, but you don't realize it because they open on top of each other and you may see only one of them, or none of them. Compare to MS Office, OpenOffice, or Photoshop, where the existing tool windows simply change their content.

    Because Gimp "tool" windows are "top-level" windows, you cannot use alt-tab to switch between Applications anymore since you will have 5-10 more windows to go through. It also clutters the taskbar. (Some environments can group windows to help with this, but this causes other problems) If another window obscures Gimp, you can't simply click on one Gimp window and they all are visible. You must click on each window, or you must minimize the other application. Essentially, it has to have it's own desktop.

    Gimp has a "main" window which has a menu for commands like File and Help. The image manipulation options (File, Edit, Select, Filters, ...) are a right-click menu on the image. This saves screen space by not displaying the menu at all times, but is confusing at first.

    Gimp options are powerful and highly technical. For example, Photoshop has a median filter that asks you for the radius. Gimp has a median filter that asks you for radius, adaptive Y/N, recursive Y/N, black level, and white level. It is an excellent filter, but it is confusing at first.

    It's tough to imagine these things without seeing it. I hope that Gimp 2.0 offers a more toolbar approach that is more consistent with the way most applications work. I think that will really help to make it more mainstream.