From 0d13ee3193dbbecaccaa91fb126bd063c5b21cb2 Mon Sep 17 00:00:00 2001 From: "Anna (navi) Figueiredo Gomes" Date: Tue, 10 Oct 2023 14:51:41 +0200 Subject: action-binder: rename to ext-action-binder Signed-off-by: Anna (navi) Figueiredo Gomes --- staging/action-binder/README | 4 - staging/action-binder/action-binder-v1.xml | 122 --------------------- staging/ext-action-binder/README | 5 + staging/ext-action-binder/ext-action-binder-v1.xml | 122 +++++++++++++++++++++ 4 files changed, 127 insertions(+), 126 deletions(-) delete mode 100644 staging/action-binder/README delete mode 100644 staging/action-binder/action-binder-v1.xml create mode 100644 staging/ext-action-binder/README create mode 100644 staging/ext-action-binder/ext-action-binder-v1.xml diff --git a/staging/action-binder/README b/staging/action-binder/README deleted file mode 100644 index 07fe7d4..0000000 --- a/staging/action-binder/README +++ /dev/null @@ -1,4 +0,0 @@ -action binder protocol - -Maintainers: -Quentin Glidic diff --git a/staging/action-binder/action-binder-v1.xml b/staging/action-binder/action-binder-v1.xml deleted file mode 100644 index 545b917..0000000 --- a/staging/action-binder/action-binder-v1.xml +++ /dev/null @@ -1,122 +0,0 @@ - - - - Copyright © 2015-2017 Quentin “Sardem FF7” Glidic, 2023 Anna "navi" Figueiredo Gomes - - 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 interface is exposed as global - - - - - The client no longer wants to receive events for any action. - - - - - - Bind an action to the object. Multiple actions can be bound at the same - time. That means any combination of events can occur. - After calling bind, the "action_bound" event is fired by the compositor - with the status of the request. - - - - - - - - - - - Removes a specific binding to the object. if the client does not hold any - binding to the namespace:name combo, no operation is performed. - - - - - - - - - - - - - - After the compositor processes a bind request, it should call this - event to notify the client of the result, as well as the trigger, in - case of success. - - - - - - - - Depending on the user configuration, an action can be either one-off or - sustained. The client must handle all the three event types and either make - sense of them or ignore them properly. - - - - - - - - - This event is sent when actions are triggered. - If a binding would trigger both triggered and started events, the - started event must be sent first. - - - - - - - diff --git a/staging/ext-action-binder/README b/staging/ext-action-binder/README new file mode 100644 index 0000000..5ad827c --- /dev/null +++ b/staging/ext-action-binder/README @@ -0,0 +1,5 @@ +action binder protocol + +Maintainers: +Anna (navi) Figueiredo Gomes +Quentin Glidic diff --git a/staging/ext-action-binder/ext-action-binder-v1.xml b/staging/ext-action-binder/ext-action-binder-v1.xml new file mode 100644 index 0000000..545b917 --- /dev/null +++ b/staging/ext-action-binder/ext-action-binder-v1.xml @@ -0,0 +1,122 @@ + + + + Copyright © 2015-2017 Quentin “Sardem FF7” Glidic, 2023 Anna "navi" Figueiredo Gomes + + 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 interface is exposed as global + + + + + The client no longer wants to receive events for any action. + + + + + + Bind an action to the object. Multiple actions can be bound at the same + time. That means any combination of events can occur. + After calling bind, the "action_bound" event is fired by the compositor + with the status of the request. + + + + + + + + + + + Removes a specific binding to the object. if the client does not hold any + binding to the namespace:name combo, no operation is performed. + + + + + + + + + + + + + + After the compositor processes a bind request, it should call this + event to notify the client of the result, as well as the trigger, in + case of success. + + + + + + + + Depending on the user configuration, an action can be either one-off or + sustained. The client must handle all the three event types and either make + sense of them or ignore them properly. + + + + + + + + + This event is sent when actions are triggered. + If a binding would trigger both triggered and started events, the + started event must be sent first. + + + + + + + -- cgit v1.2.3