[PATCH weston 10/17] xdg-shell: Clarify the meaning of app ID and give example

Jonas Ådahl jadahl at gmail.com
Tue Apr 7 02:01:25 PDT 2015

Signed-off-by: Jonas Ådahl <jadahl at gmail.com>
 protocol/xdg-shell.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml
index 3db76ab..c2e1443 100644
--- a/protocol/xdg-shell.xml
+++ b/protocol/xdg-shell.xml
@@ -197,6 +197,18 @@
 	the surface belongs. The compositor can use this to group multiple
 	surfaces together, or to determine how to launch a new application.
+	When applicable, a client should set the app ID to the basename of the
+	.desktop file associated with the application, for example
+	"org.freedesktop.FooViewer" where the .desktop file is
+	"org.freedesktop.FooViewer.desktop".
+	For D-Bus activatble applications, this will also be D-Bus service
+	name used for activation of the application.
+	It is not a hard requirement to specify a well formed (as described
+	above) app ID, but the compositor shell may group the surface
+	inadequately if the client fail to do so.
 	See the desktop-entry specification [0] for more details on
 	application identifiers and how they relate to well-known D-Bus
 	names and .desktop files.

More information about the wayland-devel mailing list