From b69196aafaff037df7a4aad9bb9ac97281d10511 Mon Sep 17 00:00:00 2001 From: Isaac Freund Date: Wed, 3 Jun 2020 01:44:07 +0200 Subject: [PATCH] Define the river status protocol This is a refinement of the now obsolete river-window-management protocol which has been deleted. --- protocol/river-status-unstable-v1.xml | 54 +++++++++++++++++++ .../river-window-management-unstable-v1.xml | 47 ---------------- 2 files changed, 54 insertions(+), 47 deletions(-) create mode 100644 protocol/river-status-unstable-v1.xml delete mode 100644 protocol/river-window-management-unstable-v1.xml diff --git a/protocol/river-status-unstable-v1.xml b/protocol/river-status-unstable-v1.xml new file mode 100644 index 0000000..fb597ce --- /dev/null +++ b/protocol/river-status-unstable-v1.xml @@ -0,0 +1,54 @@ + + + + Copyright 2020 Isaac Freund + + Permission to use, copy, modify, and/or distribute this software for any + purpose with or without fee is hereby granted, provided that the above + copyright notice and this permission notice appear in all copies. + + THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES + WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR + ANY SPECIAL, DIRECT, 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 protocol allows clients to receive information about the current + windowing state. It can be used to implement, for example, a status bar + displaying information specific to river. + + + + + Sent once for each output on binding the interface and again whenever + the tag focus of an output changes. + + + + + + + + Sent once for each output on binding the interface and again whenever + the state changes. + + + + + + + + This event is sent for each output on binding the interface and when + the focused view or title thereof changes. The title may be an empty + string if no view is focused or the focused view did not set a title. + + + + + + diff --git a/protocol/river-window-management-unstable-v1.xml b/protocol/river-window-management-unstable-v1.xml deleted file mode 100644 index 1b6b2a0..0000000 --- a/protocol/river-window-management-unstable-v1.xml +++ /dev/null @@ -1,47 +0,0 @@ - - - - Copyright 2020 Isaac Freund - - Permission to use, copy, modify, and/or distribute this software for any - purpose with or without fee is hereby granted, provided that the above - copyright notice and this permission notice appear in all copies. - - THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES - WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF - MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR - ANY SPECIAL, DIRECT, 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 protocol allows clients to recieve information about the current - windowing state. It is useful to implement, for example, a status bar - displaying information specific to the river compositor. - - - - - - - - - - - - Sent whenever the windowing state of an output changes. The output_name - argument is the same as the name returned by the xdg-output protocol. - Tags are sent as a bitfield, if a view has one of the focused tags set, - then it is displayed on the output. - - - - - - -