1 <?xml version="1.0" encoding="UTF-8"?>
2 <protocol name="agl_shell">
4 Copyright © 2019, 2022 Collabora, Ltd.
6 Permission is hereby granted, free of charge, to any person obtaining a
7 copy of this software and associated documentation files (the "Software"),
8 to deal in the Software without restriction, including without limitation
9 the rights to use, copy, modify, merge, publish, distribute, sublicense,
10 and/or sell copies of the Software, and to permit persons to whom the
11 Software is furnished to do so, subject to the following conditions:
13 The above copyright notice and this permission notice (including the next
14 paragraph) shall be included in all copies or substantial portions of the
17 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
18 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
19 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
20 THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
21 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
22 FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
23 DEALINGS IN THE SOFTWARE.
25 <interface name="agl_shell" version="3">
26 <description summary="user interface for Automotive Grade Linux platform">
27 Starting with version 2 of the protocol, the client is required to wait
28 for the 'bound_ok' or 'bound_fail' events in order to proceed further.
30 In case the client gets a 'bound_fail' event then it should consider that
31 there's another client already bound to the agl_shell protocol.
32 A client that receives a 'bound_ok' event should consider that there's
33 no other client already bound to the interface and can proceed further.
35 If the client uses an older version of the protocol it will receive
36 automatically an error and the compositor will terminate the connection,
37 if there's another client already bound the interface.
39 If the client receives the 'bound_fail' event and attempts to use the
40 interface further it will receive an error and the compositor will
41 terminate the connection. After the 'bound_fail' event was received the
42 client should call the destructor, which has been added with version 2
43 of the protocol. The client is free to try at a later point in time to
44 see if it will receive the 'bound_ok' event, but there's no explicit way
45 of finding out when that event will be delivered.
46 It is assumed that it can infer that information through other
51 <entry name="invalid_argument" value="0"/>
52 <entry name="background_exists" value="1"/>
53 <entry name="panel_exists" value="2"/>
57 <entry name="top" value="0"/>
58 <entry name="bottom" value="1"/>
59 <entry name="left" value="2"/>
60 <entry name="right" value="3"/>
63 <enum name="app_state" since="3">
64 <entry name="started" value="0"/>
65 <entry name="terminated" value="1"/>
66 <entry name="activated" value="2"/>
67 <entry name="deactivated" value="3"/>
70 <request name="ready">
71 <description summary="client is ready to be shown">
72 Tell the server that this client is ready to be shown. The server
73 will delay presentation during start-up until all shell clients are
74 ready to be shown, and will display a black screen instead.
75 This gives the client an opportunity to set up and configure several
76 surfaces into a coherent interface.
78 The client that binds to this interface must send this request, otherwise
79 they may stall the compositor unnecessarily.
81 If this request is called after the compositor has already finished
82 start-up, no operation is performed.
86 <request name="set_background">
87 <description summary="set surface as output's background">
88 Set the surface to act as the background of an output. After this
89 request, the server will immediately send a configure event with
90 the dimensions the client should use to cover the entire output.
92 The surface must have a "desktop" surface role, as supported by
95 Only a single surface may be the background for any output. If a
96 background surface already exists, a protocol error is raised.
98 <arg name="surface" type="object" interface="wl_surface"/>
99 <arg name="output" type="object" interface="wl_output"/>
102 <request name="set_panel">
103 <description summary="set surface as panel">
104 Set the surface to act as a panel of an output. The 'edge' argument
105 says what edge of the output the surface will be anchored to.
106 After this request, the server will send a configure event with the
107 corresponding width/height that the client should use, and 0 for the
108 other dimension. E.g. if the edge is 'top', the width will be the
109 output's width, and the height will be 0.
111 The surface must have a "desktop" surface role, as supported by
114 The compositor will take the panel's window geometry into account when
115 positioning other windows, so the panels are not covered.
117 XXX: What happens if e.g. both top and left are used at the same time?
118 Who gets to have the corner?
120 Only a single surface may be the panel for an output's edge. If a
121 surface already exists on an edge, a protocol error is raised.
123 <arg name="surface" type="object" interface="wl_surface"/>
124 <arg name="output" type="object" interface="wl_output"/>
125 <arg name="edge" type="uint" enum="edge"/>
128 <request name="activate_app">
129 <description summary="make client current window">
130 Ask the compositor to make a toplevel to become the current/focused
131 window for window management purposes.
133 See xdg_toplevel.set_app_id from the xdg-shell protocol for a
134 description of app_id.
136 If multiple toplevels have the same app_id, the result is unspecified.
138 XXX: Do we need feedback to say it didn't work? (e.g. client does
141 <arg name="app_id" type="string"/>
142 <arg name="output" type="object" interface="wl_output"/>
145 <event name="bound_ok" since="2">
146 <description summary="event sent if binding was ok">
147 Informs the client that it was able to bind the agl_shell
148 interface succesfully. Clients are required to wait for this
149 event before continuing further.
153 <event name="bound_fail" since="2">
154 <description summary="event sent if binding was nok">
155 Informs the client that binding to the agl_shell interface was
156 unsuccesfull. Clients are required to wait for this event for
161 <request name="destroy" type="destructor" since="2">
162 <description summary="destroys the factory object">
166 <event name="app_state" since="3">
167 <description summary="event sent when an application suffered state modification">
168 Informs the client that an application has changed its state to another,
169 specified by the app_state enum. Client can use this event to track
170 current application state. For instance to know when the application has
171 started, or when terminated/stopped.
173 <arg name="app_id" type="string"/>
174 <arg name="state" type="uint" enum="app_state"/>
179 <interface name="agl_shell_ext" version="1">
180 <description summary="extended user interface for Automotive Grade Linux platform">
181 This interface allows another client bind to the agl_shell interface in
182 case there's another shell client already present.
184 The client should first bind to this interface and then inform the
185 compositor with the 'doas_shell_client' request and it wants to bind to
186 the agl_shell interface. The client is still expected if using a new
187 version of the agl_shell interface to wait for the 'bound_ok' and
188 'bound_fail' events before issueing any other requests/events.
190 Note that this interface has its limitations, and the compositor would
191 still refuse the act for 'set_panel' or 'set_background' requests
192 of the agl_shell interface if there's already a client that used them. Any
193 other requests or events should be delievered and handled as it would
194 a client bound to the agl_shell interface.
197 <enum name="doas_shell_client_status">
198 <entry name="success" value="0"/>
199 <entry name="failed" value="1"/>
202 <request name="destroy" type="destructor">
203 <description summary="destroys the factory object">
204 Call the destructor once you're ready with agl_shell_ext interface.
205 This would reset the state and would make any requests made
206 on the agl_shell interface null. The client would need to bind again
207 the agl_shell_ext and issue a 'doas_shell_client' request.
211 <request name="doas_shell_client">
212 <description summary="Informs the compositor it wants to bind to agl_shell interface">
213 Prior to binding to agl_shell interface, this request would inform
214 the compositor it wants to gain access the agl_shell interface. The
215 client is expected to wait for 'doas_shell_client_done' event and check for
216 a successful status before going further with binding to the agl_shell
221 <event name="doas_done">
222 <description summary="event sent as a reply to doas_shell_client">
223 The client should check the status event to verify that the
224 compositor was able to handle the request.
226 <arg name="status" type="uint" enum="doas_shell_client_status"/>