On Tue, May 22, 2012 at 3:57 PM, Niels Grewe
<niels.grewe@halbordnung.de> wrote:
Hi Fred and Ivan,
Am 22.05.2012 08:32, schrieb Fred Kiefer:
> I don't think that libdbusmenu-glib is the way to go. We have a
> excellent DBUS interface in GNUstep and should build on that when
> implementing a theme that wants to handle menus that way.
I second that, especially since the DBusMenu stuff has been on my todo
list for quite some time (though not at a very high priority). Basically
what you would need is a proxy that exposes the menu using the
com.canonical.dbusmenu interface [0] and instead of having
gnustep-gui/back doing the drawing and event handling for the menu,
you'd register that proxy with the com.canonical.AppMenu.Registrar D-Bus
service [1]. The global menu will then issue callbacks that drive the
menu. (At least that's my superficial working theory of how it should work)
DBusKit would definitely be the cleanest way to go.
However, an issue is possible breakage of the DBus interface on Canonical's part. libdbusmenu-glib is probably less likely to be break.