From 64716493d19bc0f7c875b3f907b37e3c530558f8 Mon Sep 17 00:00:00 2001 From: "Anna (navi) Figueiredo Gomes" Date: Mon, 19 Jun 2023 13:48:29 -0300 Subject: action-binder-v1: move to staging and the ext namespace Signed-off-by: Anna (navi) Figueiredo Gomes --- unstable/action-binder/README | 4 - .../action-binder/action-binder-unstable-v1.xml | 121 --------------------- 2 files changed, 125 deletions(-) delete mode 100644 unstable/action-binder/README delete mode 100644 unstable/action-binder/action-binder-unstable-v1.xml (limited to 'unstable') diff --git a/unstable/action-binder/README b/unstable/action-binder/README deleted file mode 100644 index 07fe7d4..0000000 --- a/unstable/action-binder/README +++ /dev/null @@ -1,4 +0,0 @@ -action binder protocol - -Maintainers: -Quentin Glidic diff --git a/unstable/action-binder/action-binder-unstable-v1.xml b/unstable/action-binder/action-binder-unstable-v1.xml deleted file mode 100644 index a0e086b..0000000 --- a/unstable/action-binder/action-binder-unstable-v1.xml +++ /dev/null @@ -1,121 +0,0 @@ - - - - - Copyright © 2015-2017 Quentin “Sardem FF7” Glidic - - 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. - - - - - This interface is designed to allow any application to bind - an action. - - An action is an arbitrary couple of a namespace and a name describing the - wanted behaviour. These two strings are not meant to be user-visible. - Some namespaces are well-known and shared by applications while each - application can have its own namespaces for internal actions. - It is possible to have the same action in several namespaces, e.g. to - allow application-specific bindings in addition to global actions. - - It is left to the compositor to determine which client will get events. - The choice can be based on policy, heuristic, user configuration, or any - other mechanism that may be relevant. - Here are some examples of dispatching choice: all applications, last - focused, user-defined preference order, latest fullscreened application. - - This object is a singleton global. - - - - - Informs the server that the client will not be using this protocol - object anymore. You must destroy any wp_action_binding created from the - wp_action_binder before. - - - - - - Creates a binding object. It will be used by the application to bind - one or more actions and get the corresponding events. - - - - - - - - - This interface represents a binding to a set of actions. - - Depending on the user configuration, an action can be either one-off or - sustained. The client must handle all the three events and either make - sense of them or ignore them properly. - - - - - - - - - The client no longer wants to receive events for these actions. - - - - - - Bind an action to the object. Multiple actions can be bound at the same - time. That means any combination of events can occur. - If the action is reserved by the compositor a protocol error is raised. - - - - - - - - - This event is sent for one-off actions. - - If a binding would trigger both triggered and started events, the - started event must be sent first. - - - - - - This event is sent when a sustained action is started. - - - - - - This event is sent when a sustained action is stopped. - - - - -- cgit v1.2.3