|
[-]
[+]
|
Added |
_service:tar_git:wayland-protocols.changes
|
|
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols.spec
^
|
|
|
|
[-]
[+]
|
Changed |
_service
^
|
| @@ -1,6 +1,6 @@
<services>
<service name="tar_git">
- <param name="url">https://git.merproject.org/r0kk3rz/wayland-protocols.git</param>
+ <param name="url">https://git.merproject.org/mer-core/wayland-protocols.git</param>
<param name="branch">master</param>
<param name="revision">HEAD</param>
<param name="token"/>
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/.gitmodules
^
|
| @@ -1,3 +1,3 @@
[submodule "wayland-protocols"]
path = wayland-protocols
- url = git://anongit.freedesktop.org/wayland/wayland-protocols
+ url = https://git.merproject.org/mirror/wayland-protocols.git
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/Makefile.am
^
|
| @@ -16,6 +16,7 @@
unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml \
unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml \
unstable/xdg-output/xdg-output-unstable-v1.xml \
+ unstable/input-timestamps/input-timestamps-unstable-v1.xml \
$(NULL)
stable_protocols = \
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/configure.ac
^
|
| @@ -1,7 +1,7 @@
AC_PREREQ([2.64])
m4_define([wayland_protocols_major_version], [1])
-m4_define([wayland_protocols_minor_version], [12])
+m4_define([wayland_protocols_minor_version], [14])
m4_define([wayland_protocols_version],
[wayland_protocols_major_version.wayland_protocols_minor_version])
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/stable/xdg-shell/xdg-shell.xml
^
|
| @@ -29,7 +29,7 @@
DEALINGS IN THE SOFTWARE.
</copyright>
- <interface name="xdg_wm_base" version="1">
+ <interface name="xdg_wm_base" version="2">
<description summary="create desktop-style surfaces">
The xdg_wm_base interface is exposed as a global object enabling clients
to turn their wl_surfaces into windows in a desktop environment. It
@@ -115,7 +115,7 @@
</event>
</interface>
- <interface name="xdg_positioner" version="1">
+ <interface name="xdg_positioner" version="2">
<description summary="child surface positioner">
The xdg_positioner provides a collection of rules for the placement of a
child surface relative to a parent surface. Rules can be defined to ensure
@@ -359,7 +359,7 @@
</request>
</interface>
- <interface name="xdg_surface" version="1">
+ <interface name="xdg_surface" version="2">
<description summary="desktop user interface surface base interface">
An interface that may be implemented by a wl_surface, for
implementations that provide a desktop-style user interface.
@@ -528,7 +528,7 @@
</event>
</interface>
- <interface name="xdg_toplevel" version="1">
+ <interface name="xdg_toplevel" version="2">
<description summary="toplevel surface">
This interface defines an xdg_surface role which allows a surface to,
among other things, set window-like properties such as maximize,
@@ -555,7 +555,7 @@
<request name="set_parent">
<description summary="set the parent of this surface">
Set the "parent" of this surface. This surface should be stacked
- this above the parent surface and all other ancestor surfaces.
+ above the parent surface and all other ancestor surfaces.
Parent windows should be set on dialogs, toolboxes, or other
"auxiliary" surfaces, so that the parent is raised when the dialog
@@ -750,6 +750,30 @@
keyboard or pointer focus.
</description>
</entry>
+ <entry name="tiled_left" value="5" since="2">
+ <description summary="the surface is tiled">
+ The window is currently in a tiled layout and the left edge is
+ considered to be adjacent to another part of the tiling grid.
+ </description>
+ </entry>
+ <entry name="tiled_right" value="6" since="2">
+ <description summary="the surface is tiled">
+ The window is currently in a tiled layout and the right edge is
+ considered to be adjacent to another part of the tiling grid.
+ </description>
+ </entry>
+ <entry name="tiled_top" value="7" since="2">
+ <description summary="the surface is tiled">
+ The window is currently in a tiled layout and the top edge is
+ considered to be adjacent to another part of the tiling grid.
+ </description>
+ </entry>
+ <entry name="tiled_bottom" value="8" since="2">
+ <description summary="the surface is tiled">
+ The window is currently in a tiled layout and the bottom edge is
+ considered to be adjacent to another part of the tiling grid.
+ </description>
+ </entry>
</enum>
<request name="set_max_size">
@@ -989,7 +1013,7 @@
</event>
</interface>
- <interface name="xdg_popup" version="1">
+ <interface name="xdg_popup" version="2">
<description summary="short-lived, popup surfaces for menus">
A popup surface is a short-lived, temporary surface. It can be used to
implement for example menus, popovers, tooltips and other similar user
|
|
[-]
[+]
|
Added |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/unstable/input-timestamps/README
^
|
| @@ -0,0 +1,4 @@
+High-resolution timestamps for input events.
+
+Maintainers:
+Alexandros Frantzis <alexandros.frantzis@collabora.com>
|
|
[-]
[+]
|
Added |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/unstable/input-timestamps/input-timestamps-unstable-v1.xml
^
|
| @@ -0,0 +1,145 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<protocol name="input_timestamps_unstable_v1">
+
+ <copyright>
+ Copyright © 2017 Collabora, Ltd.
+
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice (including the next
+ paragraph) shall be included in all copies or substantial portions of the
+ Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+ </copyright>
+
+ <description summary="High-resolution timestamps for input events">
+ This protocol specifies a way for a client to request and receive
+ high-resolution timestamps for input events.
+
+ Warning! The protocol described in this file is experimental and
+ backward incompatible changes may be made. Backward compatible changes
+ may be added together with the corresponding interface version bump.
+ Backward incompatible changes are done by bumping the version number in
+ the protocol and interface names and resetting the interface version.
+ Once the protocol is to be declared stable, the 'z' prefix and the
+ version number in the protocol and interface names are removed and the
+ interface version number is reset.
+ </description>
+
+ <interface name="zwp_input_timestamps_manager_v1" version="1">
+ <description summary="context object for high-resolution input timestamps">
+ A global interface used for requesting high-resolution timestamps
+ for input events.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the input timestamps manager object">
+ Informs the server that the client will no longer be using this
+ protocol object. Existing objects created by this object are not
+ affected.
+ </description>
+ </request>
+
+ <request name="get_keyboard_timestamps">
+ <description summary="subscribe to high-resolution keyboard timestamp events">
+ Creates a new input timestamps object that represents a subscription
+ to high-resolution timestamp events for all wl_keyboard events that
+ carry a timestamp.
+
+ If the associated wl_keyboard object is invalidated, either through
+ client action (e.g. release) or server-side changes, the input
+ timestamps object becomes inert and the client should destroy it
+ by calling zwp_input_timestamps_v1.destroy.
+ </description>
+ <arg name="id" type="new_id" interface="zwp_input_timestamps_v1"/>
+ <arg name="keyboard" type="object" interface="wl_keyboard"
+ summary="the wl_keyboard object for which to get timestamp events"/>
+ </request>
+
+ <request name="get_pointer_timestamps">
+ <description summary="subscribe to high-resolution pointer timestamp events">
+ Creates a new input timestamps object that represents a subscription
+ to high-resolution timestamp events for all wl_pointer events that
+ carry a timestamp.
+
+ If the associated wl_pointer object is invalidated, either through
+ client action (e.g. release) or server-side changes, the input
+ timestamps object becomes inert and the client should destroy it
+ by calling zwp_input_timestamps_v1.destroy.
+ </description>
+ <arg name="id" type="new_id" interface="zwp_input_timestamps_v1"/>
+ <arg name="pointer" type="object" interface="wl_pointer"
+ summary="the wl_pointer object for which to get timestamp events"/>
+ </request>
+
+ <request name="get_touch_timestamps">
+ <description summary="subscribe to high-resolution touch timestamp events">
+ Creates a new input timestamps object that represents a subscription
+ to high-resolution timestamp events for all wl_touch events that
+ carry a timestamp.
+
+ If the associated wl_touch object becomes invalid, either through
+ client action (e.g. release) or server-side changes, the input
+ timestamps object becomes inert and the client should destroy it
+ by calling zwp_input_timestamps_v1.destroy.
+ </description>
+ <arg name="id" type="new_id" interface="zwp_input_timestamps_v1"/>
+ <arg name="touch" type="object" interface="wl_touch"
+ summary="the wl_touch object for which to get timestamp events"/>
+ </request>
+ </interface>
+
+ <interface name="zwp_input_timestamps_v1" version="1">
+ <description summary="context object for input timestamps">
+ Provides high-resolution timestamp events for a set of subscribed input
+ events. The set of subscribed input events is determined by the
+ zwp_input_timestamps_manager_v1 request used to create this object.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy the input timestamps object">
+ Informs the server that the client will no longer be using this
+ protocol object. After the server processes the request, no more
+ timestamp events will be emitted.
+ </description>
+ </request>
+
+ <event name="timestamp">
+ <description summary="high-resolution timestamp event">
+ The timestamp event is associated with the first subsequent input event
+ carrying a timestamp which belongs to the set of input events this
+ object is subscribed to.
+
+ The timestamp provided by this event is a high-resolution version of
+ the timestamp argument of the associated input event. The provided
+ timestamp is in the same clock domain and is at least as accurate as
+ the associated input event timestamp.
+
+ The timestamp is expressed as tv_sec_hi, tv_sec_lo, tv_nsec triples,
+ each component being an unsigned 32-bit value. Whole seconds are in
+ tv_sec which is a 64-bit value combined from tv_sec_hi and tv_sec_lo,
+ and the additional fractional part in tv_nsec as nanoseconds. Hence,
+ for valid timestamps tv_nsec must be in [0, 999999999].
+ </description>
+ <arg name="tv_sec_hi" type="uint"
+ summary="high 32 bits of the seconds part of the timestamp"/>
+ <arg name="tv_sec_lo" type="uint"
+ summary="low 32 bits of the seconds part of the timestamp"/>
+ <arg name="tv_nsec" type="uint"
+ summary="nanoseconds part of the timestamp"/>
+ </event>
+ </interface>
+
+</protocol>
|
|
[-]
[+]
|
Changed |
_service:tar_git:wayland-protocols-1.14.0.tar.xz/wayland-protocols/unstable/xdg-output/xdg-output-unstable-v1.xml
^
|
| @@ -54,7 +54,7 @@
reset.
</description>
- <interface name="zxdg_output_manager_v1" version="1">
+ <interface name="zxdg_output_manager_v1" version="2">
<description summary="manage xdg_output objects">
A global factory interface for xdg_output objects.
</description>
@@ -77,7 +77,7 @@
</request>
</interface>
- <interface name="zxdg_output_v1" version="1">
+ <interface name="zxdg_output_v1" version="2">
<description summary="compositor logical output region">
An xdg_output describes part of the compositor geometry.
@@ -157,5 +157,50 @@
</description>
</event>
+ <!-- Version 2 additions -->
+
+ <event name="name" since="2">
+ <description summary="name of this output">
+ Many compositors will assign names to their outputs, show them to the
+ user, allow them to be configured by name, etc. The client may wish to
+ know this name as well to offer the user similar behaviors.
+
+ The naming convention is compositor defined, but limited to
+ alphanumeric characters and dashes (-). Each name is unique among all
+ wl_output globals, but if a wl_output global is destroyed the same name
+ may be reused later. The names will also remain consistent across
+ sessions with the same hardware and software configuration.
+
+ Examples of names include 'HDMI-A-1', 'WL-1', 'X11-1', etc. However, do
+ not assume that the name is a reflection of an underlying DRM
+ connector, X11 connection, etc.
+
+ The name event is sent after creating an xdg_output (see
+ xdg_output_manager.get_xdg_output). This event is only sent once per
+ xdg_output, and the name does not change over the lifetime of the
+ wl_output global.
+ </description>
+ <arg name="name" type="string" summary="output name"/>
+ </event>
+
+ <event name="description" since="2">
+ <description summary="human-readable description of this output">
+ Many compositors can produce human-readable descriptions of their
+ outputs. The client may wish to know this description as well, to
+ communicate the user for various purposes.
+
+ The description is a UTF-8 string with no convention defined for its
+ contents. Examples might include 'Foocorp 11" Display' or 'Virtual X11
+ output via :1'.
+
+ The description event is sent after creating an xdg_output (see
+ xdg_output_manager.get_xdg_output). This event is only sent once per
+ xdg_output, and the description does not change over the lifetime of
+ the wl_output global. The description is optional, and may not be sent
+ at all.
+ </description>
+ <arg name="description" type="string" summary="output description"/>
+ </event>
+
</interface>
</protocol>
|
