The state of global menus

flying sheep · 2013-11-05 18:17:20

more info for gnumdk: https://wiki.gnome.org/GApplication/DBusAPI

flying sheep · 2013-12-12 10:41:27

also there’s this now: https://launchpad.net/qmenumodel

Thaodan · 2013-12-12 17:50:56

why is there now need for extra bindings? the old modul required no changes or a like, why this?

flying sheep · 2013-12-13 12:02:45

Thaodan wrote:

why is there now need for extra bindings? the old modul required no changes or a like, why this?

i didn’t exactly parse your sentence, but i assume you asked why the old way of doing global menus (i.e. the canonical-created dbusmenu protocol) isn’t sufficient anymore?

that’s because people from Canonical and GNOME met up and decided to create GMenuModel, which is easier for GTK developers but bound to GTK (it still uses DBUS internally, but the protocol isn’t fixed and an “implementation detail”, so it’s a moving target that can become different and incompatible at any time)

teekay · 2013-12-13 12:16:30

Thaodan wrote:

why is there now need for extra bindings? the old modul required no changes or a like, why this?

Because Canonical folks decided to drop the current implementation of exporting the menus via DBus in favour of the GMenuModel API approach + a Gtk+ module that export old-style menus through GMenuModel (unity-gtk-module).
For Qt you now need bindings to Gtk+ and its GMenuModel API in order to interact with the menu stuff.

gnumdk could give a more detailed explanation on the Qt side of things, I guess.

The dbusmenu/appmenu stuff still works fine for Qt applications and most Gtk+2 stuff (with gtk2-appmenu from AUR), for Gtk+3 stuff you would need to use an outdated Gtk+3 (still on AUR, but I do not recommend to use it).

Thaodan · 2013-12-13 15:31:00

This is retarted,its the usual GTK centered think model.
A glib thing with a qt binding (so that it works like today )would be ok but pulling GTK for a Qt application is laughable.

teekay · 2013-12-13 19:47:44

Thaodan wrote:

This is retarted,its the usual GTK centered think model.
A glib thing with a qt binding (so that it works like today )would be ok but pulling GTK for a Qt application is laughable.

GMenuModel is a glib thing, the Gtk plugin part is only required for old Gtk apps that do not yet make use of GMenuModel and maybe never will.

But I agree that it's weird to depend on glib for getting global menus in Qt. Qt has appmenu support since 4.8, I don't see why changing kded-appmenu to use GMenuModel would make sense, extending it to support it sounds good though.

Last edited by teekay (2013-12-13 19:59:59)

Thaodan · 2015-01-25 05:25:41

I know this is old but are they any news on this topic?

ewaller · 2015-02-12 04:29:40

https://wiki.archlinux.org/index.php/Fo … bumping.22

I am sorry, this thread was dead the last time it was kicked. Closing.

Arch Linux

#26 2013-11-05 18:17:20

Re: The state of global menus

#27 2013-12-12 10:41:27

Re: The state of global menus

#28 2013-12-12 17:50:56

Re: The state of global menus

#29 2013-12-13 12:02:45

Re: The state of global menus

#30 2013-12-13 12:16:30

Re: The state of global menus

#31 2013-12-13 15:31:00

Re: The state of global menus

#32 2013-12-13 19:47:44

Re: The state of global menus

#33 2015-01-25 05:25:41

Re: The state of global menus

#34 2015-02-12 04:29:40

Re: The state of global menus

Board footer