summaryrefslogtreecommitdiff
path: root/protocol
diff options
context:
space:
mode:
authorJonas Ådahl <jadahl@gmail.com>2015-05-05 15:35:14 +0800
committerBryce Harrington <bryce@osg.samsung.com>2015-05-21 18:56:26 -0700
commitca13f7ed8f93cb3c5d227e77978dd78db16a1244 (patch)
tree0b8210776673c40f7d4c06a8c75bf79ecfd07a22 /protocol
parenta7e199147a1951fa27781c9a379d4f068a6aa2df (diff)
downloadweston-ca13f7ed8f93cb3c5d227e77978dd78db16a1244.tar.gz
xdg-shell: Clarify the meaning of app ID and give example
Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
Diffstat (limited to 'protocol')
-rw-r--r--protocol/xdg-shell.xml9
1 files changed, 9 insertions, 0 deletions
diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml
index 1629bd00..07206627 100644
--- a/protocol/xdg-shell.xml
+++ b/protocol/xdg-shell.xml
@@ -189,6 +189,15 @@
the surface belongs. The compositor can use this to group multiple
surfaces together, or to determine how to launch a new application.
+ For D-Bus activatable applications, the app ID is used as the D-Bus
+ service name.
+
+ The compositor shell will try to group application surfaces together
+ by their app ID. As a best practice, it is suggested to select app
+ ID's that match the basename of the application's .desktop file.
+ For example, "org.freedesktop.FooViewer" where the .desktop file is
+ "org.freedesktop.FooViewer.desktop".
+
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.