After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 665952 - Document how gmenu is extensible (e.g for plugins)
Document how gmenu is extensible (e.g for plugins)
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Class: GtkApplication
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks: 665312
 
 
Reported: 2011-12-11 16:32 UTC by Matthias Clasen
Modified: 2016-03-06 00:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthias Clasen 2011-12-11 16:32:34 UTC 
The need for this has come out clearly in the initial review of gmenu on gtk-devel-list. The 'plugman' example explores this topic. 
Basically: it works, we just need to document how to do it.
Comment 1 Matthias Clasen 2011-12-15 20:24:08 UTC 
Things we probably want to document:

_DBUS_APPLICATION_ID(UTF8_STRING) = "org.gtk.Test.bloatpad"
_DBUS_UNIQUE_NAME(UTF8_STRING) = ":1.120"
_DBUS_OBJECT_PATH(UTF8_STRING) = "/org/gtk/Test/bloatpad/windows/0"

What do these X properties mean ?

/org/gtk/Test/bloatpad
/org/gtk/Test/bloatpad/menus/AppMenu
/org/gtk/Test/bloatpad/menus/MenuBar
/org/gtk/Test/bloatpad/windows/0

What can I do with any of these paths ? (Answer: for the first/last is g_dbus_action_group_get, for the middle ones is g_dbus_menu_model_get)

What does one use the application id (well-known name) for ?
What should one better use the unique name for ?
Comment 2 Matthias Clasen 2011-12-16 16:02:54 UTC 
Grr, Comment 1 was meant for bug 665314