RSS Feed
  1. Gimp 2.8 native download – Mac OSX Lion

    May 13, 2012 by admin

    EDIT: THIS IS BARELY BETA, MORE LIKE PRE-ALPHA. THIS IS NOT A FINISHED PRODUCT. YES, A LOT OF THE FUNCTIONS AND FEATURES WORK. HOWEVER, BE AWARE THAT CRASHES ARE NOT MY FAULT, AND WE ARE WORKING HARD TO GET A BETTER MAC RELEASE AVAILABLE. PLEASE LOOK FORWARD TO GIMP 2.8.1.

    Stable, yet unstable.

    But if you’re willing to lose at best some data, at worst a hard drive, then go ahead. Please read the release notes below. Lion only.

    But no, seriously. It’s pretty stable unstable, just beware of the things listed below, and note that the tablet driver is known to be unstable.

    Download it here.

    Release notes:

    *Contains tablet pressure patch (WARNING: Using tablet may at best crash your tablet driver, at worst your Mac) To enable, go “gimp-2.8 – Input Devices” and for each “Quartz _x_”, set to “Screen”.

    *All paths lag due to glib’s atomic operations (according to mitch)

    *Crashes (sometimes) on Open – Recent

    *Crashes (sometimes) on loading an image via dragging

    *Crashes when canceling a few plugins

    *Crashes on refreshing scripts

    *Doesn’t include python/pygtk

    *Includes Zukitwo Murrine theme

    *Various plugins open a new icon in dock, don’t come to foreground – Need to be clicked on manually


  2. Gimp 2.8 on Mac OSX Lion

    May 9, 2012 by admin

    So, after 3 days of hard work, I finally have Gimp 2.8 running on my Mac.

    I don’t think I’ll be able to get a .app anytime soon, but this is just so that everyone knows that it’s actually possible.

    EDIT:

    Well ok then. Say hello to themes and tablet pressure support. Also, the startup time is around 8 seconds. Much less than the X11 version.

    EDIT2:

    Gimp 2.8 (slightly unstable) available from here.


  3. How to make libraries relocatable?

    May 7, 2012 by admin

    Use the option “–enable-relocatable” during the configure phase, you can create dynamic libraries, which is useful for creating Mac .apps which can be run from anywhere.

    Or is it “–enable-shared”?


  4. /bin/sh: bad interpreter: wait, what?

    May 6, 2012 by admin

    With an upgrade to Lion, I’ve been seeing “/bin/sh: bad interpreter: Operation not permitted” quite a bit.

    According to the guys from this thread, Lion quarantines various bash scripts created in TextEdit, or ones moved from other locations.

    To use ./run-script.sh again, simply unquarantine it:

    xattr -d com.apple.quarantine run-script.sh

    Or unquarantine the whole damn directory:

    xattr -dr com.apple.quarantine them-scripts/

    Works for me.


  5. Double Post! New version of gedit for Mac

    January 26, 2012 by admin

    So, as I was saying, there has been quite a bit of work with gtk+osx recently, one of them being a new release of gedit for Max OSX! Check out this screenie:

    Would you look at that beauty. I do believe gtk3+quartz is coming along well.

    A few things to note: For some reason, a lot of the gtk3 stuff is now build around jhbuild, a program that supposedly takes the pain out of compiling and installing unix tools on Mac OSX. (MacPorts, anyone?) The problem is… well, there are a lot of problems. And it’s difficult to set up. And it really doesn’t like MacPorts. So I probably won’t be touching it for a while.

    Until then, download and try gedit! It’s free, of course! And while you’re at it, check out some of the other programs that have been ported to Mac.

    EDIT: Here’s a screenshot of the older version for comparison.


  6. MyPaint on Mac News

    January 26, 2012 by admin

    A few people have been wondering about tablet support for MyPaint on the Mac, and if it even works. The short answer is yes, it can, but you have to use XQuartz/X11. <rant>

    The thing is, XQuartz/X11 isn’t as bad as some people (read as: me) would like you to believe. Really, it’s not. The thing is, complete Mac integration is not and never was in the scope of the project. The idea is to have a functional X.Org server that doesn’t crash, and can handle most of what you throw at it. And it performs marvelously. Until you try to involve users who don’t understand what XQuartz/X11 is.

    For example, take me, 3 years ago. I was just learning about Blender, and the gems of open-source software. At that time I found Gimp, an amazing piece of graphics software. The problem was, I had to install X11, as well. Not only that, but X11 had to be running while I was using Gimp! What was this blasphemy, I said to myself. As it turned out, Gimp required X11 because gtk (its graphic toolkit) could not run natively (using system calls, not native cocoa) on Mac OSX. The problem behind this was that it simply didn’t feel like a native Mac application. Windows arranged themselves into obscure places, got lost behind others, and clicking-through wasn’t an option at the time. Even though XQuartz/X11 has gotten better over the years, it still doesn’t quite feel like a native Mac application.

    Hence the need for Gtk+Quartz. Recently, there have been quite a few commits to the latest version of Gtk on Mac, signaling an increased interest from developers. The problem is, Gtk+Quartz HAS NO TABLET SUPPORT. In fact, there is NO multi-input device code _anywhere_. This means, that while other applications are getting better support on Mac (see gedit and Banshee), graphics applications which rely hugely on input support from tablets are being left out. That is not to say that the developers are refusing to add tablet support, it’s just that current drawing programs (like MyPaint and Gimp) don’t have support _yet_.

    Here’s an interesting note, while writing this, I decided to check and see if there was a new update for gedit. It had recently been upgraded to gtk3, and there wasn’t a Mac application available yet. Turns out someone had created a Mac app just a few days ago, with gtk3 support and everything!

    Now let’s try to get back on track. Gtk+Quartz currently doesn’t support tablets, while XQuartz/X11 does. It pretty much comes down to personal preference. Would you prefer something with more functionality and (warning, bias imminent) less usability/integration, or something with less functionality, but more usability/integration?

    </rant>


  7. MyPaint For Python 2.7 Fixed

    December 22, 2011 by admin

    So, the devs finally issued a change that allows MyPaint on the Mac to build via Python 2.7, without having to modify the SConstruct. Good news! Also, there’s a new “move individual layer” feature which allows the user to move a layer, and MyPaint will update seamlessly. There are a few visual artifacts, although they aren’t intrusive. I’ll be uploading MyPaint 1.0.1 as soon as it’s released!


  8. Compiling MyPaint with Python 2.7 and not 2.6

    December 5, 2011 by admin

    So far, all of the methods of compiling MyPaint on the Mac required using Python 2.6, however, 2.7 was also required for compiling. Upgrading MyPaint on the Mac to compile with Python 2.7 was therefore the obvious step. After a quick google search of the error I was receiving, I found this thread on the MacPorts bug page. Conveniently, all of the work was done for me! After they decided whether or not the patch will stay, I’ll see if I can’t get the non-MacPorts changes into MyPaint master. Until then, enjoy a screenshot of MyPaint running on Python 2.7!

    Further notes: I may or may not release an updated installer with Python 2.7 installed. I don’t know how much of a real difference it would make. Also, MyPaint 1.0.0 actually includes a file-save dialog bug. It didn’t crash the program, but it shouldn’t have shipped with the big One-Oh version.


  9. MyPaint 1.0.0 Mac Release

    November 30, 2011 by admin

    So, I finally updated this blog (I’ve been swamped with school work), and I have a new version released. While it still doesn’t support tablet pressure, and there are a few graphical bugs (all related to various GTK2 issues, some fixed, others not), it is still quite functional. Anyways, the link is on my Downloads page. Compressed it’s around 30MB and uncompressed it’s around 95MB. Meaning it’s even smaller than it was before. Also, I include a simple GTK2 theme, ClearLooks, by default.

    Note: This version CAN be installed alongside MacPorts. As long as the MacPorts prefix isn’t /opt/mypaint/ that is…

    Once again, report bugs and have fun!

    Version history:

    V1: Initial MyPaint 1.0.0 installer. Large size. Wouldn’t install correctly.

    V2: Very small size, installed correctly. Export to png before saving as an .ora first produced an error.

    V3: Very small size, installs correctly. No (apparent) bugs. Theme included.


  10. Gimp Native on MacOSX

    November 19, 2011 by admin

    Today I was talking to mitch on the Gimp irc channel, and apparently he’s been doing a lot of work with Gimp on the Mac. No build instructions yet, because of the issues I was facing, namely, it’s inability to find my tiff/jpeg/jasper/aa libs. I probably got some of my includes wrong. But that’s for another time. Because, hey look, Mac Gimp native! It works!

    Essentially, I used MacPorts to download all of the libs, (I copy/pasted all of gimp2′s libs) and installed them. Then downloaded the gimp source via git, and configured it to run without the libs it couldn’t find. After a bit of compiling, I was left with a semi-functional build of Gimp.