Commit b1d631cf authored by Simon McVittie's avatar Simon McVittie

Entry points concept: promote X-Apertis-ParentEntry to recommended

I have an implementation of this that I'm happy with.
Signed-off-by: Simon McVittie's avatarSimon McVittie <smcv@collabora.com>
Reviewed-by: André Magalhães's avatarAndré Magalhães <andre.magalhaes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6335
parent 50d07874
......@@ -213,6 +213,13 @@ implementation.
The following additional keys are defined in the `[Desktop Entry]` group.
* `X-Apertis-ParentEntry` (string): For situations where multiple
menu entries start the same program in different modes, all but one
of those menu entries set `X-Apertis-ParentEntry` to the entry point ID of
the remaining menu entry. See [](#multiple-view-applications) and
the [D-Bus Activation][Bundle spec D-Bus activation] section of the
Apertis Application Bundle Specification.
* `X-GNOME-FullName` (localestring): The human-readable full name of the
application, such as `Rhayader Web Browser`. This key is already used
by the GLib library, and by desktop environments based on it (such as
......@@ -228,10 +235,6 @@ group.
chosen from `highest`, `high`, `normal`, `low` or `lowest`. As a future
extension, numeric priorities could be added, with those strings mapped
to reasonable values.
* `X-Apertis-ParentEntry` (string): For situations where multiple
menu entries start the same program in different modes, each mode sets
`X-Apertis-ParentEntry` to the entry point ID of the program as a whole. See
[](#multiple-view-applications).
#### Audio roles
......@@ -421,8 +424,8 @@ The running instance of Frampton would always identify itself as
`org.apertis.Frampton`, and the other three `.desktop` files use
`X-Apertis-ParentEntry=org.apertis.Frampton` to link them to that name.
If we move to a model that uses [D-Bus activation][Desktop Entry D-Bus
Activation] for applications (which is recommended), then Frampton
When using [D-Bus activation][Desktop Entry D-Bus
Activation] for applications (which is recommended), Frampton
would have separate D-Bus `.service` files for all four names, would
take all four bus names and their corresponding object paths at runtime,
and would export the `org.freedesktop.Application` API at all four paths;
......@@ -446,6 +449,7 @@ Categories=Audio;Player;Music;
MimeType=audio/mpeg;
NoDisplay=true;
Icon=music
X-Apertis-ServiceExec=/usr/Applications/org.apertis.Frampton/bin/frampton --gapplication-service
```
```
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment