The folks at http://www.wilber-loves-apple.org/ are pretty involved in this. Unfortunately they did not release some kind of beta yet. I think to get rid of the X11 emulation on OS X will be a revolution for GIMP @ OS X.

I hardly can wait to see it happen.

Greetings, lexA

2008/2/7, Sven Neumann :

Hi,

has anyone lately tried to build and use GIMP on Mac OS X using GTK+ with the native Quartz backend?

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

As far as I can see there have been lots of fixes there lately, all of which seem to have been merged to the GTK+ 2.12 tree. So it would be interesting to know how well GIMP 2.4 works on Mac OS X using a recent gtk-macosx build.

Sven

_______________________________________________ Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Hi,

I'm a http://www.wilber-loves-apple.org/ member. I am regularly building latest GTK and GIMP, and have produced a first self-contained binary some time ago (see thread on said website).

For now it's looking very promising. There are a few reasons why it was not released yet :
* There's a few major showstopper bugs, and we're waiting on GTK folks to fix them. The most important one is that keyboard shortcuts currently do not care about the open window and can catch keys randomly - for instance if you try to type a S in the text editor tool, the S key down event will be stolen by the toolbox window, and used to select whatever tool uses shortcut S. * Packaging it is currently very painful. The current X11 package uses a launcher. We could still use a launcher for the native version and have it easy, but it doesn't feel right, and there's up to 3 icons in the dock for GIMP (while usually a dock should only have one icon per app. in this case, it's one for the launcher, one for GIMP, one for script-fu). So the procedure I have written about some time ago does work just fine without launcher, but has only minimal functionnality, is very long and painful, unreliable, and requires patching GIMP. I currently am planning to work on improving the process. Another bit of problem, is that it while requires patching GIMP, the patches would be very specific to my build method and in no way universal to all possible mac ports, so this is why I never submitted anything (plus, they are very ugly and hackish, many improvements still needed). I will continue looking into it, and probably get back to this mailing list when I have done a bit more work.

The native menu bar does an awesome job. Sometime in the future, the GTK team plan to add open document event catching capabilities to the menu bar package, and when they do it would be great to implement this feature (I'll try to do it but my gobject and GIMP internals knowledge is so bad I'm not sure I'll be able to - if it's the case, and mitch doesn't have time to add this feature like he did with the menu bar, I can perhaps for help again here) (on mac, open document are always events, so there's no need for stunts like gimp-remote. even though I think you're moving away from that on linux too?)

But, the good news is that it's sure going to work :) Not yet sure how, but working on it.

On 2/7/08 9:18 AM, "M Gagnon" wrote:

* Packaging it is currently very painful. The current X11 package uses a launcher. We could still use a launcher for the native version and have it easy, but it doesn't feel right, and there's up to 3 icons in the dock for GIMP (while usually a dock should only have one icon per app. in this case, it's one for the launcher, one for GIMP, one for script-fu). So the procedure I have written about some time ago does work just fine without launcher, but has only minimal functionnality,

I'm not sure I understand fully your packaging mechanism, but would it be possible to have script-fu and the launcher as faceless background apps? I know it's possible to disable the dock presence (for a given app) -- but I am not sure if it's really needed a UI for the extra 2 processes in your new scheme. If I understand the intentions of the project (make GIMP a seamless first-class citizen on OS X), in theory the user shouldn't need to worry about those technical details: so I'm thinking, maybe any config-related UI elements could be removed or moved somewhere else and have the 2 additional processes as background daemons.

Ettore

On Fri, 2008-02-08 at 09:14 +0100, Sven Neumann wrote:

Hi,

On Thu, 2008-02-07 at 12:18 -0500, M Gagnon wrote:

* There's a few major showstopper bugs, and we're waiting on GTK folks to fix them. The most important one is that keyboard shortcuts currently do not care about the open window and can catch keys randomly - for instance if you try to type a S in the text editor tool, the S key down event will be stolen by the toolbox window, and used to select whatever tool uses shortcut S.

Has this been reported upstream?

It is exactly the same issue we fixed by having a custom key event handler on docks (gimp_dock_key_press_event), and the proposed fix seems inspired by this solution. Basically you would have to call a function from your app to get the menu events handled at the right time.

The upstream bug is here: http://bugzilla.gnome.org/show_bug.cgi?id=473822

The complete GDK patch is here: http://ardour.org/files/patches/gtk.patch

Gimp would simply call gdk_quartz_possibly_forward() (badly named) from the right spot in the dock key event handler.

ciao, --mitch

Hi everyone,

I'm not sure I understand fully your packaging mechanism, but would it be

possible to have script-fu and the launcher as faceless background apps? I
know it's possible to disable the dock presence (for a given app) -- but I am not sure if it's really needed a UI for the extra 2 processes in your new
scheme. If I understand the intentions of the project (make GIMP a seamless
first-class citizen on OS X), in theory the user shouldn't need to worry about those technical details: so I'm thinking, maybe any config-related UI
elements could be removed or moved somewhere else and have the 2 additional
processes as background daemons.

Actually the goal at the moment is to get rid of the launcher, only this way can GIMP be a true mac app (this includes the ability to open documents by dropping them on its icon, all general interaction from the dock, using application switchers, etc. none of these native features could be performed properly with a hidden launcher. That's why I'm working towards removing the launcher altoghether and itneraction directly with the gimp executable. Making script-fu a faceless background process is probably possible but I still need to experiment.

Also, keep in mind removinf the launcher IS possible, I've already done it, I just need to refine my instructions. I am thinking about creating some sort of GTK binary distribution for mac (anyway if I don't someone else will do. such a distribution would ease the process A LOT).

You would also have to do this (or something like this) for all plug-ins. Script-Fu just happens to run as an extension. But there might be other GIMP extensions and since all plug-ins are separate processes, they would probably all show up in the dock when they are being run.

Ok. Well I will first try to figure out the appropraite code to do that (I have sample code I think could work but I still have to test it). When I figure that out, we can think about polishing things. Also, just removing the launcher would already improve the interaction a lot so I may start with that instead.

Has this been reported upstream?

It has, and it might even be fixed, I don't know, I need to update my GTK version and test again (I'm doing it at the moment but it takes a rather long time to compile everything on my computer)