GIMPshop


Someone has taken
the Gimp
and
hacked its UI to be similar to PhotoShop.
From the posting about it:

The Gimp’s menu structure and naming conventions had been a constant source of frustration for me because I was so used to Photoshop. So, I did what any hardcore graphics geek would have done. I hacked GIMPshop together. It’s a proof of concept and it’s a little buggy, so don’t expect too much.

[..]

My original purpose for GIMPshop was to make the Gimp accessible to the many Adobe Photoshop users out there. I hope I’ve done that. And maybe along the way, I can convert a Photoshop pirate into a Gimp user.

If you’ve never used Photoshop before, you may not appreciate my GIMPshop hack. What I’ve done is renamed and reorganized GIMP’s tools, options, windows, and menus to closely resemble Adobe Photoshop’s menu structure and naming conventions. Many of the menu options and even whole menus were recreated to faithfully reproduce a Photoshop-like experience. After running my GIMPshop hack, you’ll find that Photoshop and the GIMP are strikingly similar.

So if you use PhotoShop, you might want to check this out.
Wouldn’t it be nice not to spend hundreds of dollars on this kind of thing?

Published by

rae

Mac developer

6 thoughts on “GIMPshop”

  1. From http://docs.gimp.org/en/ch02s04.html#id3309740:

    In Gimp, every color channel, including the alpha channel, has a range of possible values from 0 to 255; in computing terminology, a depth of 8 bits. Some digital cameras can produce image files with a depth of 16 bits per color channel. Gimp cannot load such a file without losing resolution. In most cases the effects are too subtle to be detected by the human eye, but in some cases, mainly where there are large areas with slowly varying color gradients, the difference may be perceptible

    Oddly, I am a person who can instantly hear and see the differences in:
    stereo vs. mono
    stereo vs. 5.1 channel sound
    128k bps vs. 256k bps .mp3
    VHS vs. DVD
    DVD vs. HD-TV
    1 Megapixel vs. 3 Megapixel (on screen)
    and also 8 bit vs. 12 bit color

    It’s enough to make me believe in solipsism. It seems to be related to my political views, but I won’t go there. The philosophical point, simply put, is “What is wrong with this picture?” I should upload an example, but I have a picture of a B-52 taken in the Arizona desert. I made a point out of taking a RAW-mode picture of it and I played with the 12 bit color afforded to me by knowledge of this issue. A novice looking at the picture sees a “B-52”. A person who’s looked at a few books says, “Oh it’s a B-52 painted in a Vietnam paint scheme”. A photographer says “Ah, it’s a B-52 in a Vietnam paint scheme and some of it is in dark shadow”. A person who knows the difference between an 8 bit color depth and 12 bit colour depth (that’s me, btw), looks at the picture and says “Ah! It is but the .jpeg that shows dark shadow!”. The novice then says “shadows are dark, you cannot see into them”. The photographer says “If only I had a daylight fill-flash”, and then Nikon says, “Let there be 12 bits!”, and then all could see the paint scheme as if the plane was photographed in a portrait studio. Then a voice says, “Say, isn’t this the place where B-52 # 56-666 was chopped up?”

    Anyhow, the new Nikon D70s is coming out in a few weeks too. I’m tempted to upgrade for the focusing speed. There has never been anything like this in the history of photography (except for the Canon EOS-20D, that is) … although I have some good ideas for the SONY HDRFX1, if I could afford it. [In a nutshell, it could be considered a 30 frames-per-second 1 megapixel 12x zoom camera — nice for in-flight birds, air-shows, and probably sports, although I’m worried about the losses of “HDV” encoding.]

  2. r.e. The Gimp being only 8-bit; they do plan to change this, or so claims this page:

    GIMP Versions 1.x and 2.0 are natively RGB 8-bits per channel (24bpp)(This is why we set the monitor to 24bpp too). Native 16-bit and CMYK support coming in the future.

    Also, apparently someone already extended The Gimp to 16 bits and renamed it CinePaint:

    CinePaint is a 16 bit version of GIMP 1.0 designed specifically for this purpose. There are no plans currently to merge CinePaint and GIMP and both projects are happily extending their features on their own.

  3. Like, oh my god. I installed Cinepaint on the Athlon 64 in 64 bit mode. wow.
    First I needed a display driver, and then.. er, it’s been 4.5 hours now of installation bliss, I forget — oh yeah here are the dependencies:
    1. Cinepaint (obvious)
    2. lcms color management (sourceforge)
    3. OpenEXR (industrial light and magic)
    4. Latest nVidia driver (and after all this work, it only goes up to 1600×1200! It’s missing 2048×1536)
    5. Kernel 2.6.11.7
    6. Kernel configuration (Hey, this one is getting easier all the time! If only I’d compiled it with udf & ntfs support… crap I thought I did)
    7. I still need to get that .NEF -> .TIFF converter. I had it running once before though.

    Wahoo, and after all that, Cinepaint doesn’t seem to do too much. However, as an added bonus, Gimp 2.0.5 is working. It is more like Adobe Photoshop Elements in terms of features.

    Does someone know how to emulate the Adobe “Fill Flash” histogram adjustment with Cinepaint?

  4. Man it just gets better. Ultimately, I got a copy of ufraw (for linux), which is based on dcraw the raw file reader. It can do histogram and shadow work with the raw files (Yahoo!) and I am playing with the B52 picture right now. But to get this far! Hooolllly:
    1. A kernel rebuild for the dvd driver and ntfs was foiled by 2 bugs, a Fedora udev issue and the fact that you’re supposed to rebuild the NVIDA drivers every time you build the kernel. This lead to:
    2. An unbootable linux! Fortunately, I learned on the net that getting stuck at “Configuring kernel parameters” because of either udev or the nvidia build issue can be resolved by selcting “a” in grub and adding the kernel parameter “level 3” so you can get into a command-line shell and fix everything up.
    3. Anyway, now gimp is broken.

  5. gimp was broken because of old gimp 2.0 libs. I deleted them all and now it works. My linux can also read but not yet write NTFS file systems. The RAW image editing is not too painful to do exactly what I wanted to do. ufraw has a cool histogram slider and other controls for obvious things one does with RAW images. Sure to provide hours of fun.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax

This site uses Akismet to reduce spam. Learn how your comment data is processed.