diff options
| -rw-r--r-- | protocols/desktop-shell.xml | 138 | ||||
| -rw-r--r-- | protocols/gamma-control.xml | 57 | ||||
| -rw-r--r-- | protocols/server-decoration.xml | 94 | ||||
| -rw-r--r-- | protocols/swaylock.xml | 18 |
4 files changed, 0 insertions, 307 deletions
diff --git a/protocols/desktop-shell.xml b/protocols/desktop-shell.xml deleted file mode 100644 index 581f0c5d..00000000 --- a/protocols/desktop-shell.xml +++ /dev/null @@ -1,138 +0,0 @@ -<protocol name="desktop"> - - <interface name="desktop_shell" version="3"> - <description summary="create desktop widgets and helpers"> - Traditional user interfaces can rely on this interface to define the - foundations of typical desktops. Currently it's possible to set up - background, panels and locking surfaces. - </description> - - <request name="set_background"> - <arg name="output" type="object" interface="wl_output"/> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - - <request name="set_panel"> - <arg name="output" type="object" interface="wl_output"/> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - - <request name="set_lock_surface"> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - - <request name="unlock"/> - - <request name="set_grab_surface"> - <description summary="set grab surface"> - The surface set by this request will receive a fake - pointer.enter event during grabs at position 0, 0 and is - expected to set an appropriate cursor image as described by - the grab_cursor event sent just before the enter event. - </description> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - - <!-- We'll fold most of wl_shell into this interface and then - they'll share the configure event. --> - <event name="configure"> - <arg name="edges" type="uint"/> - <arg name="surface" type="object" interface="wl_surface"/> - <arg name="width" type="int"/> - <arg name="height" type="int"/> - </event> - - <event name="prepare_lock_surface"> - <description summary="tell the client to create, set the lock surface"> - Tell the client we want it to create and set the lock surface, which is - a GUI asking the user to unlock the screen. The lock surface is - announced with 'set_lock_surface'. Whether or not the client actually - implements locking, it MUST send 'unlock' request to let the normal - desktop resume. - </description> - </event> - - <event name="grab_cursor"> - <description summary="tell client what cursor to show during a grab"> - This event will be sent immediately before a fake enter event on the - grab surface. - </description> - <arg name="cursor" type="uint"/> - </event> - - <enum name="cursor"> - <entry name="none" value="0"/> - - <entry name="resize_top" value="1"/> - <entry name="resize_bottom" value="2"/> - - <entry name="arrow" value="3"/> - - <entry name="resize_left" value="4"/> - <entry name="resize_top_left" value="5"/> - <entry name="resize_bottom_left" value="6"/> - - <entry name="move" value="7"/> - - <entry name="resize_right" value="8"/> - <entry name="resize_top_right" value="9"/> - <entry name="resize_bottom_right" value="10"/> - - <entry name="busy" value="11"/> - </enum> - - <!-- Version 2 additions --> - - <request name="desktop_ready" since="2"> - <description summary="desktop is ready to be shown"> - Tell the server, that enough desktop elements have been drawn - to make the desktop look ready for use. During start-up, the - server can wait for this request with a black screen before - starting to fade in the desktop, for instance. If the client - parts of a desktop take a long time to initialize, we avoid - showing temporary garbage. - </description> - </request> - - <!-- Version 3 additions --> - - <enum name="panel_position"> - <entry name="top" value="0"/> - <entry name="bottom" value="1"/> - <entry name="left" value="2"/> - <entry name="right" value="3"/> - </enum> - - <enum name="error"> - <entry name="invalid_argument" value="0" - summary="an invalid argument was provided in a request"/> - </enum> - - <request name="set_panel_position" since="3"> - <description summary="set panel position"> - Tell the shell which side of the screen the panel is - located. This is so that new windows do not overlap the panel - and maximized windows maximize properly. - </description> - <arg name="position" type="uint"/> - </request> - - </interface> - - <interface name="screensaver" version="1"> - <description summary="interface for implementing screensavers"> - Only one client can bind this interface at a time. - </description> - - <request name="set_surface"> - <description summary="set the surface type as a screensaver"> - A screensaver surface is normally hidden, and only visible after an - idle timeout. - </description> - - <arg name="surface" type="object" interface="wl_surface"/> - <arg name="output" type="object" interface="wl_output"/> - </request> - - </interface> -</protocol> diff --git a/protocols/gamma-control.xml b/protocols/gamma-control.xml deleted file mode 100644 index e6e33265..00000000 --- a/protocols/gamma-control.xml +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<protocol name="gamma_control"> - - <copyright> - Copyright © 2015 Giulio camuffo - - Permission to use, copy, modify, distribute, and sell this - software and its documentation for any purpose is hereby granted - without fee, provided that the above copyright notice appear in - all copies and that both that copyright notice and this permission - notice appear in supporting documentation, and that the name of - the copyright holders not be used in advertising or publicity - pertaining to distribution of the software without specific, - written prior permission. The copyright holders make no - representations about the suitability of this software for any - purpose. It is provided "as is" without express or implied - warranty. - - THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS - SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND - FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY - SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES - WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN - AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, - ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF - THIS SOFTWARE. - </copyright> - - <interface name="gamma_control_manager" version="1"> - <request name="destroy" type="destructor"/> - - <request name="get_gamma_control"> - <arg name="id" type="new_id" interface="gamma_control"/> - <arg name="output" type="object" interface="wl_output"/> - </request> - </interface> - - <interface name="gamma_control" version="1"> - <enum name="error"> - <entry name="invalid_gamma" value="0"/> - </enum> - - <request name="destroy" type="destructor"/> - - <request name="set_gamma"> - <arg name="red" type="array"/> - <arg name="green" type="array"/> - <arg name="blue" type="array"/> - </request> - - <request name="reset_gamma"/> - - <event name="gamma_size"> - <arg name="size" type="uint"/> - </event> - </interface> -</protocol> diff --git a/protocols/server-decoration.xml b/protocols/server-decoration.xml deleted file mode 100644 index 8bc106c7..00000000 --- a/protocols/server-decoration.xml +++ /dev/null @@ -1,94 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<protocol name="server_decoration"> - <copyright><![CDATA[ - Copyright (C) 2015 Martin Gräßlin - - This program is free software: you can redistribute it and/or modify - it under the terms of the GNU Lesser General Public License as published by - the Free Software Foundation, either version 2.1 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU Lesser General Public License for more details. - - You should have received a copy of the GNU Lesser General Public License - along with this program. If not, see <http://www.gnu.org/licenses/>. - ]]></copyright> - <interface name="org_kde_kwin_server_decoration_manager" version="1"> - <description summary="Server side window decoration manager"> - This interface allows to coordinate whether the server should create - a server-side window decoration around a wl_surface representing a - shell surface (wl_shell_surface or similar). By announcing support - for this interface the server indicates that it supports server - side decorations. - </description> - <request name="create"> - <description summary="Create a server-side decoration object for a given surface"> - When a client creates a server-side decoration object it indicates - that it supports the protocol. The client is supposed to tell the - server whether it wants server-side decorations or will provide - client-side decorations. - - If the client does not create a server-side decoration object for - a surface the server interprets this as lack of support for this - protocol and considers it as client-side decorated. Nevertheless a - client-side decorated surface should use this protocol to indicate - to the server that it does not want a server-side deco. - </description> - <arg name="id" type="new_id" interface="org_kde_kwin_server_decoration"/> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - <enum name="mode"> - <description summary="Possible values to use in request_mode and the event mode."/> - <entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/> - <entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/> - <entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/> - </enum> - <event name="default_mode"> - <description summary="The default mode used on the server"> - This event is emitted directly after binding the interface. It contains - the default mode for the decoration. When a new server decoration object - is created this new object will be in the default mode until the first - request_mode is requested. - - The server may change the default mode at any time. - </description> - <arg name="mode" type="uint" summary="The default decoration mode applied to newly created server decorations."/> - </event> - </interface> - <interface name="org_kde_kwin_server_decoration" version="1"> - <request name="release" type="destructor"> - <description summary="release the server decoration object"/> - </request> - <enum name="mode"> - <description summary="Possible values to use in request_mode and the event mode."/> - <entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/> - <entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/> - <entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/> - </enum> - <request name="request_mode"> - <description summary="The decoration mode the surface wants to use."/> - <arg name="mode" type="uint" summary="The mode this surface wants to use."/> - </request> - <event name="mode"> - <description summary="The new decoration mode applied by the server"> - This event is emitted directly after the decoration is created and - represents the base decoration policy by the server. E.g. a server - which wants all surfaces to be client-side decorated will send Client, - a server which wants server-side decoration will send Server. - - The client can request a different mode through the decoration request. - The server will acknowledge this by another event with the same mode. So - even if a server prefers server-side decoration it's possible to force a - client-side decoration. - - The server may emit this event at any time. In this case the client can - again request a different mode. It's the responsibility of the server to - prevent a feedback loop. - </description> - <arg name="mode" type="uint" summary="The decoration mode applied to the surface by the server."/> - </event> - </interface> -</protocol> diff --git a/protocols/swaylock.xml b/protocols/swaylock.xml deleted file mode 100644 index c7a102dd..00000000 --- a/protocols/swaylock.xml +++ /dev/null @@ -1,18 +0,0 @@ -<protocol name="lock"> - - <interface name="lock" version="1"> - <description summary="create lock screen UIs"> - The Weston desktop-shell protocol's locking functionality depends more - on the behavior of the compositor than of a screen locking client, so - another protocol is necessary. - </description> - - <request name="set_lock_surface"> - <arg name="output" type="object" interface="wl_output"/> - <arg name="surface" type="object" interface="wl_surface"/> - </request> - - <request name="unlock"/> - - </interface> -</protocol> |