From: Ross M. <rmm-haskell@z.odi.ac> - 2008-11-16 21:15:28
|
I do have it all set up and wouldn't mind doing this, though I have a few architecture-ish questions: 1) What's the best way to put it in the build so it doesn't break non-mac versions (especially important, I think, because I don't have any non-macs to use this on right now) 2) Where in the module hierarchy should it go? Graphics.UI.Gtk.Mac and finally are there any special caveats I should know about? You've seen the depth that I've gone in gtk2hs, that is to say just tweaking existing signatures and export lists. Also, the mac port of gtk2hs, or of GTK+? Thanks, -Ross Axel Simon wrote: > > On Nov 16, 2008, at 20:45, Ross Mellgren wrote: > >> Hi all, >> >> Reading up on the GTK+ Quartz port, it seems there are special >> additional functions for making the integration to the mac tighter (in >> particular making the menu bar be the one at the top of the screen, >> instead of per-window). >> >> On the page >> http://developer.imendio.com/projects/gtk-macosx/integration, it >> mentions using functions like ige_mac_menu_set_menu_bar(...). I did a >> quick find/grep on gtk2hs and couldn't find this referred to. >> >> Is there currently any binding for making the mac integration tighter >> like this, or would I have to wire in some new bindings? >> > > No, unfortunately not. The mac os port has also been idle for over a > year now after the guy finished his Master thesis. In principle there > would be no problem to bind these few functions that set the menu bar on > OS X, albeit I haven't gone through the trouble of trying the Gtk-Mac OS > port at all yet. If you've set it all up, I think adding the few extra > functions would be trivial, and I'd be happy to help you writing those. > > Cheers, > Axel. > > |