From f57f484eb434ac13865161527f9324bc6428c115 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Wed, 25 Oct 2017 16:07:33 +0900 Subject: [PATCH 01/16] configure.ac: updated comment for xdg-shell unstable v5 Change-Id: Icb0c38d748793830bc30230a51124924ea6e9add --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index ea2b9a6..79ea9fc 100644 --- a/Makefile.am +++ b/Makefile.am @@ -25,7 +25,7 @@ src/%-server.pc : $(top_srcdir)/src/template-server.pc src/%-client.pc : $(top_srcdir)/src/template-client.pc $(cp) $< $@ && $(perl) -pi -e 's|template|$*|g' $@ -### xdg-shell +### xdg-shell (unstable v5) protocol_LTLIBRARIES += \ libxdg-shell-server.la \ libxdg-shell-client.la -- 2.7.4 From b50a4213a9449ffbcb5cff87fd7ef3353549c677 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Wed, 25 Oct 2017 17:31:18 +0900 Subject: [PATCH 02/16] added xdg-shell unstable v6 library and header files to wayland-extension pkg Change-Id: Ia161d77f2610890a8c6f9dbc00a1cb442a450d6b --- Makefile.am | 37 ++++++++++++++++++++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index 79ea9fc..9a6ac17 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1,5 +1,7 @@ AM_CPPFLAGS = \ -I$(top_builddir)/protocol/tizen \ + -I$(top_builddir)/protocol/unstable \ + -I$(top_builddir)/protocol/stable \ -I$(top_srcdir)/src \ $(NULL) @@ -11,7 +13,7 @@ pkgconfig_DATA = protocolinclude_HEADERS = src/wayland-extension-version.h protocol_LTLIBRARIES = -### protocol.[ch] +### protocol/tizen/protocol.[ch] protocol/tizen/%-protocol.c : $(top_srcdir)/protocol/tizen/%.xml $(wayland_scanner) code < $< > $@ protocol/tizen/%-server-protocol.h : $(top_srcdir)/protocol/tizen/%.xml @@ -19,6 +21,22 @@ protocol/tizen/%-server-protocol.h : $(top_srcdir)/protocol/tizen/%.xml protocol/tizen/%-client-protocol.h : $(top_srcdir)/protocol/tizen/%.xml $(wayland_scanner) client-header < $< > $@ +### protocol/unstable/protocol.[ch] +protocol/unstable/%-protocol.c : $(top_srcdir)/protocol/unstable/*/%.xml + $(wayland_scanner) code < $< > $@ +protocol/unstable/%-server-protocol.h : $(top_srcdir)/protocol/unstable/*/%.xml + $(wayland_scanner) server-header < $< > $@ +protocol/unstable/%-client-protocol.h : $(top_srcdir)/protocol/unstable/*/%.xml + $(wayland_scanner) client-header < $< > $@ + +### protocol/stable/protocol.[ch] +protocol/stable/%-protocol.c : $(top_srcdir)/protocol/stable/*/%.xml + $(wayland_scanner) code < $< > $@ +protocol/stable/%-server-protocol.h : $(top_srcdir)/protocol/stable/*/%.xml + $(wayland_scanner) server-header < $< > $@ +protocol/stable/%-client-protocol.h : $(top_srcdir)/protocol/stable/*/%.xml + $(wayland_scanner) client-header < $< > $@ + ### protocol.pc src/%-server.pc : $(top_srcdir)/src/template-server.pc $(cp) $< $@ && $(perl) -pi -e 's|template|$*|g' $@ @@ -42,6 +60,23 @@ libxdg_shell_client_la_SOURCES = protocol/tizen/xdg-shell-protocol.c libxdg_shell_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ libxdg_shell_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ +### xdg-shell (unstable v6) +protocol_LTLIBRARIES += \ + libxdg-shell-unstable-v6-server.la \ + libxdg-shell-unstable-v6-client.la +pkgconfig_DATA += \ + src/xdg-shell-unstable-v6-server.pc \ + src/xdg-shell-unstable-v6-client.pc +protocolinclude_HEADERS += \ + protocol/unstable/xdg-shell-unstable-v6-server-protocol.h \ + protocol/unstable/xdg-shell-unstable-v6-client-protocol.h +libxdg_shell_unstable_v6_server_la_SOURCES = protocol/unstable/xdg-shell-unstable-v6-protocol.c +libxdg_shell_unstable_v6_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ +libxdg_shell_unstable_v6_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ +libxdg_shell_unstable_v6_client_la_SOURCES = protocol/unstable/xdg-shell-unstable-v6-protocol.c +libxdg_shell_unstable_v6_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ +libxdg_shell_unstable_v6_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ + ### input-method protocol_LTLIBRARIES += \ libinput-method-server.la \ -- 2.7.4 From ad7fe13a89a79c6b68926dc199993cf9b76ffb55 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Tue, 6 Feb 2018 17:56:28 +0900 Subject: [PATCH 03/16] Makefile.am: fixed path of tizen-surface Change-Id: I6487a4ffc824d66ce16ec9818cbb8e6cdaf13db5 --- Makefile.am | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Makefile.am b/Makefile.am index 9a6ac17..5031203 100644 --- a/Makefile.am +++ b/Makefile.am @@ -255,12 +255,12 @@ pkgconfig_DATA += \ src/tizen-surface-server.pc \ src/tizen-surface-client.pc protocolinclude_HEADERS += \ - protocol/tizen-surface-server-protocol.h \ - protocol/tizen-surface-client-protocol.h -libtizen_surface_server_la_SOURCES = protocol/tizen-surface-protocol.c + protocol/tizen/tizen-surface-server-protocol.h \ + protocol/tizen/tizen-surface-client-protocol.h +libtizen_surface_server_la_SOURCES = protocol/tizen/tizen-surface-protocol.c libtizen_surface_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ libtizen_surface_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ -libtizen_surface_client_la_SOURCES = protocol/tizen-surface-protocol.c +libtizen_surface_client_la_SOURCES = protocol/tizen/tizen-surface-protocol.c libtizen_surface_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ libtizen_surface_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ -- 2.7.4 From 72a9be12aea73caccf768b947be35e767deffbb4 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Fri, 9 Feb 2018 20:22:36 +0900 Subject: [PATCH 04/16] merged with wayland-protocols 1.12 added new protocols: xdg-shell stable v1, input-timestamps unstable v1 Change-Id: I7b5a8e3533a9ed4f7067b592e2b0c3ae0369e877 --- Makefile.am | 51 +- configure.ac | 2 +- protocol/stable/xdg-shell/README | 5 + protocol/stable/xdg-shell/xdg-shell.xml | 1120 ++++++++++++++++++++ protocol/unstable/input-timestamps/README | 4 + .../input-timestamps-unstable-v1.xml | 145 +++ 6 files changed, 1310 insertions(+), 17 deletions(-) create mode 100644 protocol/stable/xdg-shell/README create mode 100644 protocol/stable/xdg-shell/xdg-shell.xml create mode 100644 protocol/unstable/input-timestamps/README create mode 100644 protocol/unstable/input-timestamps/input-timestamps-unstable-v1.xml diff --git a/Makefile.am b/Makefile.am index 5031203..54bf5f2 100644 --- a/Makefile.am +++ b/Makefile.am @@ -43,22 +43,22 @@ src/%-server.pc : $(top_srcdir)/src/template-server.pc src/%-client.pc : $(top_srcdir)/src/template-client.pc $(cp) $< $@ && $(perl) -pi -e 's|template|$*|g' $@ -### xdg-shell (unstable v5) -protocol_LTLIBRARIES += \ - libxdg-shell-server.la \ - libxdg-shell-client.la -pkgconfig_DATA += \ - src/xdg-shell-server.pc \ - src/xdg-shell-client.pc -protocolinclude_HEADERS += \ - protocol/tizen/xdg-shell-server-protocol.h \ - protocol/tizen/xdg-shell-client-protocol.h -libxdg_shell_server_la_SOURCES = protocol/tizen/xdg-shell-protocol.c -libxdg_shell_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ -libxdg_shell_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ -libxdg_shell_client_la_SOURCES = protocol/tizen/xdg-shell-protocol.c -libxdg_shell_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ -libxdg_shell_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ +#### xdg-shell (unstable v5) +#protocol_LTLIBRARIES += \ +# libxdg-shell-server.la \ +# libxdg-shell-client.la +#pkgconfig_DATA += \ +# src/xdg-shell-server.pc \ +# src/xdg-shell-client.pc +#protocolinclude_HEADERS += \ +# protocol/tizen/xdg-shell-server-protocol.h \ +# protocol/tizen/xdg-shell-client-protocol.h +#libxdg_shell_server_la_SOURCES = protocol/tizen/xdg-shell-protocol.c +#libxdg_shell_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ +#libxdg_shell_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ +#libxdg_shell_client_la_SOURCES = protocol/tizen/xdg-shell-protocol.c +#libxdg_shell_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ +#libxdg_shell_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ ### xdg-shell (unstable v6) protocol_LTLIBRARIES += \ @@ -77,6 +77,23 @@ libxdg_shell_unstable_v6_client_la_SOURCES = protocol/unstable/xdg-shell-unstabl libxdg_shell_unstable_v6_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ libxdg_shell_unstable_v6_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ +### xdg-shell (stable v1) +protocol_LTLIBRARIES += \ + libxdg-shell-server.la \ + libxdg-shell-client.la +pkgconfig_DATA += \ + src/xdg-shell-server.pc \ + src/xdg-shell-client.pc +protocolinclude_HEADERS += \ + protocol/stable/xdg-shell-server-protocol.h \ + protocol/stable/xdg-shell-client-protocol.h +libxdg_shell_server_la_SOURCES = protocol/stable/xdg-shell-protocol.c +libxdg_shell_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ +libxdg_shell_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ +libxdg_shell_client_la_SOURCES = protocol/stable/xdg-shell-protocol.c +libxdg_shell_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ +libxdg_shell_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ + ### input-method protocol_LTLIBRARIES += \ libinput-method-server.la \ @@ -283,11 +300,13 @@ unstable_protocols = \ protocol/unstable/xwayland-keyboard-grab/xwayland-keyboard-grab-unstable-v1.xml \ protocol/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml \ protocol/unstable/xdg-output/xdg-output-unstable-v1.xml \ + protocol/unstable/input-timestamps/input-timestamps-unstable-v1.xml \ $(NULL) stable_protocols = \ protocol/stable/presentation-time/presentation-time.xml \ protocol/stable/viewporter/viewporter.xml \ + protocol/stable/xdg-shell/xdg-shell.xml \ $(NULL) nobase_dist_pkgdata_DATA = \ diff --git a/configure.ac b/configure.ac index 282db8c..7b2ff1a 100644 --- a/configure.ac +++ b/configure.ac @@ -7,7 +7,7 @@ m4_define([wayland_extension_version], [wayland_extension_major_version.wayland_extension_minor_version.wayland_extension_micro_version]) m4_define([wayland_protocols_major_version], [1]) -m4_define([wayland_protocols_minor_version], [11]) +m4_define([wayland_protocols_minor_version], [12]) m4_define([wayland_protocols_version], [wayland_protocols_major_version.wayland_protocols_minor_version]) diff --git a/protocol/stable/xdg-shell/README b/protocol/stable/xdg-shell/README new file mode 100644 index 0000000..2769abb --- /dev/null +++ b/protocol/stable/xdg-shell/README @@ -0,0 +1,5 @@ +xdg shell protocol + +Maintainers: +Jonas Ådahl +Mike Blumenkrantz diff --git a/protocol/stable/xdg-shell/xdg-shell.xml b/protocol/stable/xdg-shell/xdg-shell.xml new file mode 100644 index 0000000..d524ea9 --- /dev/null +++ b/protocol/stable/xdg-shell/xdg-shell.xml @@ -0,0 +1,1120 @@ + + + + + Copyright © 2008-2013 Kristian Høgsberg + Copyright © 2013 Rafael Antognolli + Copyright © 2013 Jasper St. Pierre + Copyright © 2010-2013 Intel Corporation + Copyright © 2015-2017 Samsung Electronics Co., Ltd + Copyright © 2015-2017 Red Hat Inc. + + 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. + + + + + 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 + defines the basic functionality needed for clients and the compositor to + create windows that can be dragged, resized, maximized, etc, as well as + creating transient windows such as popup menus. + + + + + + + + + + + + + + Destroy this xdg_wm_base object. + + Destroying a bound xdg_wm_base object while there are surfaces + still alive created by this xdg_wm_base object instance is illegal + and will result in a protocol error. + + + + + + Create a positioner object. A positioner object is used to position + surfaces relative to some parent surface. See the interface description + and xdg_surface.get_popup for details. + + + + + + + This creates an xdg_surface for the given surface. While xdg_surface + itself is not a role, the corresponding surface may only be assigned + a role extending xdg_surface, such as xdg_toplevel or xdg_popup. + + This creates an xdg_surface for the given surface. An xdg_surface is + used as basis to define a role to a given surface, such as xdg_toplevel + or xdg_popup. It also manages functionality shared between xdg_surface + based surface roles. + + See the documentation of xdg_surface for more details about what an + xdg_surface is and how it is used. + + + + + + + + A client must respond to a ping event with a pong request or + the client may be deemed unresponsive. See xdg_wm_base.ping. + + + + + + + The ping event asks the client if it's still alive. Pass the + serial specified in the event back to the compositor by sending + a "pong" request back with the specified serial. See xdg_wm_base.ping. + + Compositors can use this to determine if the client is still + alive. It's unspecified what will happen if the client doesn't + respond to the ping request, or in what timeframe. Clients should + try to respond in a reasonable amount of time. + + A compositor is free to ping in any way it wants, but a client must + always respond to any xdg_wm_base object it created. + + + + + + + + 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 + the child surface remains within the visible area's borders, and to + specify how the child surface changes its position, such as sliding along + an axis, or flipping around a rectangle. These positioner-created rules are + constrained by the requirement that a child surface must intersect with or + be at least partially adjacent to its parent surface. + + See the various requests for details about possible rules. + + At the time of the request, the compositor makes a copy of the rules + specified by the xdg_positioner. Thus, after the request is complete the + xdg_positioner object can be destroyed or reused; further changes to the + object will have no effect on previous usages. + + For an xdg_positioner object to be considered complete, it must have a + non-zero size set by set_size, and a non-zero anchor rectangle set by + set_anchor_rect. Passing an incomplete xdg_positioner object when + positioning a surface raises an error. + + + + + + + + + Notify the compositor that the xdg_positioner will no longer be used. + + + + + + Set the size of the surface that is to be positioned with the positioner + object. The size is in surface-local coordinates and corresponds to the + window geometry. See xdg_surface.set_window_geometry. + + If a zero or negative size is set the invalid_input error is raised. + + + + + + + + Specify the anchor rectangle within the parent surface that the child + surface will be placed relative to. The rectangle is relative to the + window geometry as defined by xdg_surface.set_window_geometry of the + parent surface. + + When the xdg_positioner object is used to position a child surface, the + anchor rectangle may not extend outside the window geometry of the + positioned child's parent surface. + + If a negative size is set the invalid_input error is raised. + + + + + + + + + + + + + + + + + + + + + + Defines the anchor point for the anchor rectangle. The specified anchor + is used derive an anchor point that the child surface will be + positioned relative to. If a corner anchor is set (e.g. 'top_left' or + 'bottom_right'), the anchor point will be at the specified corner; + otherwise, the derived anchor point will be centered on the specified + edge, or in the center of the anchor rectangle if no edge is specified. + + + + + + + + + + + + + + + + + + + Defines in what direction a surface should be positioned, relative to + the anchor point of the parent surface. If a corner gravity is + specified (e.g. 'bottom_right' or 'top_left'), then the child surface + will be placed towards the specified gravity; otherwise, the child + surface will be centered over the anchor point on any axis that had no + gravity specified. + + + + + + + The constraint adjustment value define ways the compositor will adjust + the position of the surface, if the unadjusted position would result + in the surface being partly constrained. + + Whether a surface is considered 'constrained' is left to the compositor + to determine. For example, the surface may be partly outside the + compositor's defined 'work area', thus necessitating the child surface's + position be adjusted until it is entirely inside the work area. + + The adjustments can be combined, according to a defined precedence: 1) + Flip, 2) Slide, 3) Resize. + + + + Don't alter the surface position even if it is constrained on some + axis, for example partially outside the edge of an output. + + + + + Slide the surface along the x axis until it is no longer constrained. + + First try to slide towards the direction of the gravity on the x axis + until either the edge in the opposite direction of the gravity is + unconstrained or the edge in the direction of the gravity is + constrained. + + Then try to slide towards the opposite direction of the gravity on the + x axis until either the edge in the direction of the gravity is + unconstrained or the edge in the opposite direction of the gravity is + constrained. + + + + + Slide the surface along the y axis until it is no longer constrained. + + First try to slide towards the direction of the gravity on the y axis + until either the edge in the opposite direction of the gravity is + unconstrained or the edge in the direction of the gravity is + constrained. + + Then try to slide towards the opposite direction of the gravity on the + y axis until either the edge in the direction of the gravity is + unconstrained or the edge in the opposite direction of the gravity is + constrained. + + + + + Invert the anchor and gravity on the x axis if the surface is + constrained on the x axis. For example, if the left edge of the + surface is constrained, the gravity is 'left' and the anchor is + 'left', change the gravity to 'right' and the anchor to 'right'. + + If the adjusted position also ends up being constrained, the resulting + position of the flip_x adjustment will be the one before the + adjustment. + + + + + Invert the anchor and gravity on the y axis if the surface is + constrained on the y axis. For example, if the bottom edge of the + surface is constrained, the gravity is 'bottom' and the anchor is + 'bottom', change the gravity to 'top' and the anchor to 'top'. + + The adjusted position is calculated given the original anchor + rectangle and offset, but with the new flipped anchor and gravity + values. + + If the adjusted position also ends up being constrained, the resulting + position of the flip_y adjustment will be the one before the + adjustment. + + + + + Resize the surface horizontally so that it is completely + unconstrained. + + + + + Resize the surface vertically so that it is completely unconstrained. + + + + + + + Specify how the window should be positioned if the originally intended + position caused the surface to be constrained, meaning at least + partially outside positioning boundaries set by the compositor. The + adjustment is set by constructing a bitmask describing the adjustment to + be made when the surface is constrained on that axis. + + If no bit for one axis is set, the compositor will assume that the child + surface should not change its position on that axis when constrained. + + If more than one bit for one axis is set, the order of how adjustments + are applied is specified in the corresponding adjustment descriptions. + + The default adjustment is none. + + + + + + + Specify the surface position offset relative to the position of the + anchor on the anchor rectangle and the anchor on the surface. For + example if the anchor of the anchor rectangle is at (x, y), the surface + has the gravity bottom|right, and the offset is (ox, oy), the calculated + surface position will be (x + ox, y + oy). The offset position of the + surface is the one used for constraint testing. See + set_constraint_adjustment. + + An example use case is placing a popup menu on top of a user interface + element, while aligning the user interface element of the parent surface + with some user interface element placed somewhere in the popup surface. + + + + + + + + + An interface that may be implemented by a wl_surface, for + implementations that provide a desktop-style user interface. + + It provides a base set of functionality required to construct user + interface elements requiring management by the compositor, such as + toplevel windows, menus, etc. The types of functionality are split into + xdg_surface roles. + + Creating an xdg_surface does not set the role for a wl_surface. In order + to map an xdg_surface, the client must create a role-specific object + using, e.g., get_toplevel, get_popup. The wl_surface for any given + xdg_surface can have at most one role, and may not be assigned any role + not based on xdg_surface. + + A role must be assigned before any other requests are made to the + xdg_surface object. + + The client must call wl_surface.commit on the corresponding wl_surface + for the xdg_surface state to take effect. + + Creating an xdg_surface from a wl_surface which has a buffer attached or + committed is a client error, and any attempts by a client to attach or + manipulate a buffer prior to the first xdg_surface.configure call must + also be treated as errors. + + Mapping an xdg_surface-based role surface is defined as making it + possible for the surface to be shown by the compositor. Note that + a mapped surface is not guaranteed to be visible once it is mapped. + + For an xdg_surface to be mapped by the compositor, the following + conditions must be met: + (1) the client has assigned an xdg_surface-based role to the surface + (2) the client has set and committed the xdg_surface state and the + role-dependent state to the surface + (3) the client has committed a buffer to the surface + + A newly-unmapped surface is considered to have met condition (1) out + of the 3 required conditions for mapping a surface if its role surface + has not been destroyed. + + + + + + + + + + + Destroy the xdg_surface object. An xdg_surface must only be destroyed + after its role object has been destroyed. + + + + + + This creates an xdg_toplevel object for the given xdg_surface and gives + the associated wl_surface the xdg_toplevel role. + + See the documentation of xdg_toplevel for more details about what an + xdg_toplevel is and how it is used. + + + + + + + This creates an xdg_popup object for the given xdg_surface and gives + the associated wl_surface the xdg_popup role. + + If null is passed as a parent, a parent surface must be specified using + some other protocol, before committing the initial state. + + See the documentation of xdg_popup for more details about what an + xdg_popup is and how it is used. + + + + + + + + + The window geometry of a surface is its "visible bounds" from the + user's perspective. Client-side decorations often have invisible + portions like drop-shadows which should be ignored for the + purposes of aligning, placing and constraining windows. + + The window geometry is double buffered, and will be applied at the + time wl_surface.commit of the corresponding wl_surface is called. + + When maintaining a position, the compositor should treat the (x, y) + coordinate of the window geometry as the top left corner of the window. + A client changing the (x, y) window geometry coordinate should in + general not alter the position of the window. + + Once the window geometry of the surface is set, it is not possible to + unset it, and it will remain the same until set_window_geometry is + called again, even if a new subsurface or buffer is attached. + + If never set, the value is the full bounds of the surface, + including any subsurfaces. This updates dynamically on every + commit. This unset is meant for extremely simple clients. + + The arguments are given in the surface-local coordinate space of + the wl_surface associated with this xdg_surface. + + The width and height must be greater than zero. Setting an invalid size + will raise an error. When applied, the effective window geometry will be + the set window geometry clamped to the bounding rectangle of the + combined geometry of the surface of the xdg_surface and the associated + subsurfaces. + + + + + + + + + + When a configure event is received, if a client commits the + surface in response to the configure event, then the client + must make an ack_configure request sometime before the commit + request, passing along the serial of the configure event. + + For instance, for toplevel surfaces the compositor might use this + information to move a surface to the top left only when the client has + drawn itself for the maximized or fullscreen state. + + If the client receives multiple configure events before it + can respond to one, it only has to ack the last configure event. + + A client is not required to commit immediately after sending + an ack_configure request - it may even ack_configure several times + before its next surface commit. + + A client may send multiple ack_configure requests before committing, but + only the last request sent before a commit indicates which configure + event the client really is responding to. + + + + + + + The configure event marks the end of a configure sequence. A configure + sequence is a set of one or more events configuring the state of the + xdg_surface, including the final xdg_surface.configure event. + + Where applicable, xdg_surface surface roles will during a configure + sequence extend this event as a latched state sent as events before the + xdg_surface.configure event. Such events should be considered to make up + a set of atomically applied configuration states, where the + xdg_surface.configure commits the accumulated state. + + Clients should arrange their surface for the new states, and then send + an ack_configure request with the serial sent in this configure event at + some point before committing the new surface. + + If the client receives multiple configure events before it can respond + to one, it is free to discard all but the last event it received. + + + + + + + + This interface defines an xdg_surface role which allows a surface to, + among other things, set window-like properties such as maximize, + fullscreen, and minimize, set application-specific metadata like title and + id, and well as trigger user interactive operations such as interactive + resize and move. + + Unmapping an xdg_toplevel means that the surface cannot be shown + by the compositor until it is explicitly mapped again. + All active operations (e.g., move, resize) are canceled and all + attributes (e.g. title, state, stacking, ...) are discarded for + an xdg_toplevel surface when it is unmapped. + + Attaching a null buffer to a toplevel unmaps the surface. + + + + + This request destroys the role surface and unmaps the surface; + see "Unmapping" behavior in interface section for details. + + + + + + Set the "parent" of this surface. This surface should be stacked + 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 + is raised. + + Setting a null parent for a child window removes any parent-child + relationship for the child. Setting a null parent for a window which + currently has no parent is a no-op. + + If the parent is unmapped then its children are managed as + though the parent of the now-unmapped parent has become the + parent of this surface. If no parent exists for the now-unmapped + parent then the children are managed as though they have no + parent surface. + + + + + + + Set a short title for the surface. + + This string may be used to identify the surface in a task bar, + window list, or other user interface elements provided by the + compositor. + + The string must be encoded in UTF-8. + + + + + + + Set an application identifier for the surface. + + The app ID identifies the general class of applications to which + the surface belongs. The compositor can use this to group multiple + surfaces together, or to determine how to launch a new application. + + For D-Bus activatable applications, the app ID is used as the D-Bus + service name. + + The compositor shell will try to group application surfaces together + by their app ID. As a best practice, it is suggested to select app + ID's that match the basename of the application's .desktop file. + For example, "org.freedesktop.FooViewer" where the .desktop file is + "org.freedesktop.FooViewer.desktop". + + See the desktop-entry specification [0] for more details on + application identifiers and how they relate to well-known D-Bus + names and .desktop files. + + [0] http://standards.freedesktop.org/desktop-entry-spec/ + + + + + + + Clients implementing client-side decorations might want to show + a context menu when right-clicking on the decorations, giving the + user a menu that they can use to maximize or minimize the window. + + This request asks the compositor to pop up such a window menu at + the given position, relative to the local surface coordinates of + the parent surface. There are no guarantees as to what menu items + the window menu contains. + + This request must be used in response to some sort of user action + like a button press, key press, or touch down event. + + + + + + + + + + Start an interactive, user-driven move of the surface. + + This request must be used in response to some sort of user action + like a button press, key press, or touch down event. The passed + serial is used to determine the type of interactive move (touch, + pointer, etc). + + The server may ignore move requests depending on the state of + the surface (e.g. fullscreen or maximized), or if the passed serial + is no longer valid. + + If triggered, the surface will lose the focus of the device + (wl_pointer, wl_touch, etc) used for the move. It is up to the + compositor to visually indicate that the move is taking place, such as + updating a pointer cursor, during the move. There is no guarantee + that the device focus will return when the move is completed. + + + + + + + + These values are used to indicate which edge of a surface + is being dragged in a resize operation. + + + + + + + + + + + + + + + Start a user-driven, interactive resize of the surface. + + This request must be used in response to some sort of user action + like a button press, key press, or touch down event. The passed + serial is used to determine the type of interactive resize (touch, + pointer, etc). + + The server may ignore resize requests depending on the state of + the surface (e.g. fullscreen or maximized). + + If triggered, the client will receive configure events with the + "resize" state enum value and the expected sizes. See the "resize" + enum value for more details about what is required. The client + must also acknowledge configure events using "ack_configure". After + the resize is completed, the client will receive another "configure" + event without the resize state. + + If triggered, the surface also will lose the focus of the device + (wl_pointer, wl_touch, etc) used for the resize. It is up to the + compositor to visually indicate that the resize is taking place, + such as updating a pointer cursor, during the resize. There is no + guarantee that the device focus will return when the resize is + completed. + + The edges parameter specifies how the surface should be resized, + and is one of the values of the resize_edge enum. The compositor + may use this information to update the surface position for + example when dragging the top left corner. The compositor may also + use this information to adapt its behavior, e.g. choose an + appropriate cursor image. + + + + + + + + + The different state values used on the surface. This is designed for + state values like maximized, fullscreen. It is paired with the + configure event to ensure that both the client and the compositor + setting the state can be synchronized. + + States set in this way are double-buffered. They will get applied on + the next commit. + + + + The surface is maximized. The window geometry specified in the configure + event must be obeyed by the client. + + + + + The surface is fullscreen. The window geometry specified in the + configure event is a maximum; the client cannot resize beyond it. For + a surface to cover the whole fullscreened area, the geometry + dimensions must be obeyed by the client. For more details, see + xdg_toplevel.set_fullscreen. + + + + + The surface is being resized. The window geometry specified in the + configure event is a maximum; the client cannot resize beyond it. + Clients that have aspect ratio or cell sizing configuration can use + a smaller size, however. + + + + + Client window decorations should be painted as if the window is + active. Do not assume this means that the window actually has + keyboard or pointer focus. + + + + + + + Set a maximum size for the window. + + The client can specify a maximum size so that the compositor does + not try to configure the window beyond this size. + + The width and height arguments are in window geometry coordinates. + See xdg_surface.set_window_geometry. + + Values set in this way are double-buffered. They will get applied + on the next commit. + + The compositor can use this information to allow or disallow + different states like maximize or fullscreen and draw accurate + animations. + + Similarly, a tiling window manager may use this information to + place and resize client windows in a more effective way. + + The client should not rely on the compositor to obey the maximum + size. The compositor may decide to ignore the values set by the + client and request a larger size. + + If never set, or a value of zero in the request, means that the + client has no expected maximum size in the given dimension. + As a result, a client wishing to reset the maximum size + to an unspecified state can use zero for width and height in the + request. + + Requesting a maximum size to be smaller than the minimum size of + a surface is illegal and will result in a protocol error. + + The width and height must be greater than or equal to zero. Using + strictly negative values for width and height will result in a + protocol error. + + + + + + + + Set a minimum size for the window. + + The client can specify a minimum size so that the compositor does + not try to configure the window below this size. + + The width and height arguments are in window geometry coordinates. + See xdg_surface.set_window_geometry. + + Values set in this way are double-buffered. They will get applied + on the next commit. + + The compositor can use this information to allow or disallow + different states like maximize or fullscreen and draw accurate + animations. + + Similarly, a tiling window manager may use this information to + place and resize client windows in a more effective way. + + The client should not rely on the compositor to obey the minimum + size. The compositor may decide to ignore the values set by the + client and request a smaller size. + + If never set, or a value of zero in the request, means that the + client has no expected minimum size in the given dimension. + As a result, a client wishing to reset the minimum size + to an unspecified state can use zero for width and height in the + request. + + Requesting a minimum size to be larger than the maximum size of + a surface is illegal and will result in a protocol error. + + The width and height must be greater than or equal to zero. Using + strictly negative values for width and height will result in a + protocol error. + + + + + + + + Maximize the surface. + + After requesting that the surface should be maximized, the compositor + will respond by emitting a configure event with the "maximized" state + and the required window geometry. The client should then update its + content, drawing it in a maximized state, i.e. without shadow or other + decoration outside of the window geometry. The client must also + acknowledge the configure when committing the new content (see + ack_configure). + + It is up to the compositor to decide how and where to maximize the + surface, for example which output and what region of the screen should + be used. + + If the surface was already maximized, the compositor will still emit + a configure event with the "maximized" state. + + If the surface is in a fullscreen state, this request has no direct + effect. It will alter the state the surface is returned to when + unmaximized if not overridden by the compositor. + + + + + + Unmaximize the surface. + + After requesting that the surface should be unmaximized, the compositor + will respond by emitting a configure event without the "maximized" + state. If available, the compositor will include the window geometry + dimensions the window had prior to being maximized in the configure + event. The client must then update its content, drawing it in a + regular state, i.e. potentially with shadow, etc. The client must also + acknowledge the configure when committing the new content (see + ack_configure). + + It is up to the compositor to position the surface after it was + unmaximized; usually the position the surface had before maximizing, if + applicable. + + If the surface was already not maximized, the compositor will still + emit a configure event without the "maximized" state. + + If the surface is in a fullscreen state, this request has no direct + effect. It will alter the state the surface is returned to when + unmaximized if not overridden by the compositor. + + + + + + Make the surface fullscreen. + + After requesting that the surface should be fullscreened, the + compositor will respond by emitting a configure event with the + "fullscreen" state and the fullscreen window geometry. The client must + also acknowledge the configure when committing the new content (see + ack_configure). + + The output passed by the request indicates the client's preference as + to which display it should be set fullscreen on. If this value is NULL, + it's up to the compositor to choose which display will be used to map + this surface. + + If the surface doesn't cover the whole output, the compositor will + position the surface in the center of the output and compensate with + with border fill covering the rest of the output. The content of the + border fill is undefined, but should be assumed to be in some way that + attempts to blend into the surrounding area (e.g. solid black). + + If the fullscreened surface is not opaque, the compositor must make + sure that other screen content not part of the same surface tree (made + up of subsurfaces, popups or similarly coupled surfaces) are not + visible below the fullscreened surface. + + + + + + + Make the surface no longer fullscreen. + + After requesting that the surface should be unfullscreened, the + compositor will respond by emitting a configure event without the + "fullscreen" state. + + Making a surface unfullscreen sets states for the surface based on the following: + * the state(s) it may have had before becoming fullscreen + * any state(s) decided by the compositor + * any state(s) requested by the client while the surface was fullscreen + + The compositor may include the previous window geometry dimensions in + the configure event, if applicable. + + The client must also acknowledge the configure when committing the new + content (see ack_configure). + + + + + + Request that the compositor minimize your surface. There is no + way to know if the surface is currently minimized, nor is there + any way to unset minimization on this surface. + + If you are looking to throttle redrawing when minimized, please + instead use the wl_surface.frame event for this, as this will + also work with live previews on windows in Alt-Tab, Expose or + similar compositor features. + + + + + + This configure event asks the client to resize its toplevel surface or + to change its state. The configured state should not be applied + immediately. See xdg_surface.configure for details. + + The width and height arguments specify a hint to the window + about how its surface should be resized in window geometry + coordinates. See set_window_geometry. + + If the width or height arguments are zero, it means the client + should decide its own window dimension. This may happen when the + compositor needs to configure the state of the surface but doesn't + have any information about any previous or expected dimension. + + The states listed in the event specify how the width/height + arguments should be interpreted, and possibly how it should be + drawn. + + Clients must send an ack_configure in response to this event. See + xdg_surface.configure and xdg_surface.ack_configure for details. + + + + + + + + + The close event is sent by the compositor when the user + wants the surface to be closed. This should be equivalent to + the user clicking the close button in client-side decorations, + if your application has any. + + This is only a request that the user intends to close the + window. The client may choose to ignore this request, or show + a dialog to ask the user to save their data, etc. + + + + + + + A popup surface is a short-lived, temporary surface. It can be used to + implement for example menus, popovers, tooltips and other similar user + interface concepts. + + A popup can be made to take an explicit grab. See xdg_popup.grab for + details. + + When the popup is dismissed, a popup_done event will be sent out, and at + the same time the surface will be unmapped. See the xdg_popup.popup_done + event for details. + + Explicitly destroying the xdg_popup object will also dismiss the popup and + unmap the surface. Clients that want to dismiss the popup when another + surface of their own is clicked should dismiss the popup using the destroy + request. + + The parent surface must have either the xdg_toplevel or xdg_popup surface + role. + + A newly created xdg_popup will be stacked on top of all previously created + xdg_popup surfaces associated with the same xdg_toplevel. + + The parent of an xdg_popup must be mapped (see the xdg_surface + description) before the xdg_popup itself. + + The x and y arguments passed when creating the popup object specify + where the top left of the popup should be placed, relative to the + local surface coordinates of the parent surface. See + xdg_surface.get_popup. An xdg_popup must intersect with or be at least + partially adjacent to its parent surface. + + The client must call wl_surface.commit on the corresponding wl_surface + for the xdg_popup state to take effect. + + + + + + + + + This destroys the popup. Explicitly destroying the xdg_popup + object will also dismiss the popup, and unmap the surface. + + If this xdg_popup is not the "topmost" popup, a protocol error + will be sent. + + + + + + This request makes the created popup take an explicit grab. An explicit + grab will be dismissed when the user dismisses the popup, or when the + client destroys the xdg_popup. This can be done by the user clicking + outside the surface, using the keyboard, or even locking the screen + through closing the lid or a timeout. + + If the compositor denies the grab, the popup will be immediately + dismissed. + + This request must be used in response to some sort of user action like a + button press, key press, or touch down event. The serial number of the + event should be passed as 'serial'. + + The parent of a grabbing popup must either be an xdg_toplevel surface or + another xdg_popup with an explicit grab. If the parent is another + xdg_popup it means that the popups are nested, with this popup now being + the topmost popup. + + Nested popups must be destroyed in the reverse order they were created + in, e.g. the only popup you are allowed to destroy at all times is the + topmost one. + + When compositors choose to dismiss a popup, they may dismiss every + nested grabbing popup as well. When a compositor dismisses popups, it + will follow the same dismissing order as required from the client. + + The parent of a grabbing popup must either be another xdg_popup with an + active explicit grab, or an xdg_popup or xdg_toplevel, if there are no + explicit grabs already taken. + + If the topmost grabbing popup is destroyed, the grab will be returned to + the parent of the popup, if that parent previously had an explicit grab. + + If the parent is a grabbing popup which has already been dismissed, this + popup will be immediately dismissed. If the parent is a popup that did + not take an explicit grab, an error will be raised. + + During a popup grab, the client owning the grab will receive pointer + and touch events for all their surfaces as normal (similar to an + "owner-events" grab in X11 parlance), while the top most grabbing popup + will always have keyboard focus. + + + + + + + + This event asks the popup surface to configure itself given the + configuration. The configured state should not be applied immediately. + See xdg_surface.configure for details. + + The x and y arguments represent the position the popup was placed at + given the xdg_positioner rule, relative to the upper left corner of the + window geometry of the parent surface. + + + + + + + + + + The popup_done event is sent out when a popup is dismissed by the + compositor. The client should destroy the xdg_popup object at this + point. + + + + + diff --git a/protocol/unstable/input-timestamps/README b/protocol/unstable/input-timestamps/README new file mode 100644 index 0000000..3e82890 --- /dev/null +++ b/protocol/unstable/input-timestamps/README @@ -0,0 +1,4 @@ +High-resolution timestamps for input events. + +Maintainers: +Alexandros Frantzis diff --git a/protocol/unstable/input-timestamps/input-timestamps-unstable-v1.xml b/protocol/unstable/input-timestamps/input-timestamps-unstable-v1.xml new file mode 100644 index 0000000..7c5e082 --- /dev/null +++ b/protocol/unstable/input-timestamps/input-timestamps-unstable-v1.xml @@ -0,0 +1,145 @@ + + + + + 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. + + + + 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. + + + + + A global interface used for requesting high-resolution timestamps + for input events. + + + + + Informs the server that the client will no longer be using this + protocol object. Existing objects created by this object are not + affected. + + + + + + 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. + + + + + + + + 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. + + + + + + + + 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. + + + + + + + + + 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. + + + + + 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. + + + + + + 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]. + + + + + + + + -- 2.7.4 From a7ef50322ff947e553dbb0d5c9e672c11f25d604 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Fri, 9 Feb 2018 20:30:51 +0900 Subject: [PATCH 05/16] changed xdg-shell unstable v5 to unstable directory from tizen Change-Id: I76813a68849a6e013f953cf8a35ca3c349c8619e --- Makefile.am | 32 +-- protocol/tizen/xdg-shell.xml | 588 ------------------------------------------- 2 files changed, 16 insertions(+), 604 deletions(-) delete mode 100644 protocol/tizen/xdg-shell.xml diff --git a/Makefile.am b/Makefile.am index 54bf5f2..f685041 100644 --- a/Makefile.am +++ b/Makefile.am @@ -43,22 +43,22 @@ src/%-server.pc : $(top_srcdir)/src/template-server.pc src/%-client.pc : $(top_srcdir)/src/template-client.pc $(cp) $< $@ && $(perl) -pi -e 's|template|$*|g' $@ -#### xdg-shell (unstable v5) -#protocol_LTLIBRARIES += \ -# libxdg-shell-server.la \ -# libxdg-shell-client.la -#pkgconfig_DATA += \ -# src/xdg-shell-server.pc \ -# src/xdg-shell-client.pc -#protocolinclude_HEADERS += \ -# protocol/tizen/xdg-shell-server-protocol.h \ -# protocol/tizen/xdg-shell-client-protocol.h -#libxdg_shell_server_la_SOURCES = protocol/tizen/xdg-shell-protocol.c -#libxdg_shell_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ -#libxdg_shell_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ -#libxdg_shell_client_la_SOURCES = protocol/tizen/xdg-shell-protocol.c -#libxdg_shell_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ -#libxdg_shell_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ +### xdg-shell (unstable v5) +protocol_LTLIBRARIES += \ + libxdg-shell-unstable-v5-server.la \ + libxdg-shell-unstable-v5-client.la +pkgconfig_DATA += \ + src/xdg-shell-unstable-v5-server.pc \ + src/xdg-shell-unstable-v5-client.pc +protocolinclude_HEADERS += \ + protocol/unstable/xdg-shell-unstable-v5-server-protocol.h \ + protocol/unstable/xdg-shell-unstable-v5-client-protocol.h +libxdg_shell_unstable_v5_server_la_SOURCES = protocol/unstable/xdg-shell-unstable-v5-protocol.c +libxdg_shell_unstable_v5_server_la_CFLAGS = @WAYLAND_SERVER_CFLAGS@ +libxdg_shell_unstable_v5_server_la_LIBADD = @WAYLAND_SERVER_LIBS@ +libxdg_shell_unstable_v5_client_la_SOURCES = protocol/unstable/xdg-shell-unstable-v5-protocol.c +libxdg_shell_unstable_v5_client_la_CFLAGS = @WAYLAND_CLIENT_CFLAGS@ +libxdg_shell_unstable_v5_client_la_LIBADD = @WAYLAND_CLIENT_LIBS@ ### xdg-shell (unstable v6) protocol_LTLIBRARIES += \ diff --git a/protocol/tizen/xdg-shell.xml b/protocol/tizen/xdg-shell.xml deleted file mode 100644 index 68b874a..0000000 --- a/protocol/tizen/xdg-shell.xml +++ /dev/null @@ -1,588 +0,0 @@ - - - - - Copyright © 2008-2013 Kristian Høgsberg - Copyright © 2013 Rafael Antognolli - Copyright © 2013 Jasper St. Pierre - Copyright © 2010-2013 Intel Corporation - - 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. - - - - - xdg_shell allows clients to turn a wl_surface into a "real window" - which can be dragged, resized, stacked, and moved around by the - user. Everything about this interface is suited towards traditional - desktop environments. - - - - - The 'current' member of this enum gives the version of the - protocol. Implementations can compare this to the version - they implement using static_assert to ensure the protocol and - implementation versions match. - - - - - - - - - - - - - - Destroy this xdg_shell object. - - Destroying a bound xdg_shell object while there are surfaces - still alive created by this xdg_shell object instance is illegal - and will result in a protocol error. - - - - - - Negotiate the unstable version of the interface. This - mechanism is in place to ensure client and server agree on the - unstable versions of the protocol that they speak or exit - cleanly if they don't agree. This request will go away once - the xdg-shell protocol is stable. - - - - - - - This creates an xdg_surface for the given surface and gives it the - xdg_surface role. A wl_surface can only be given an xdg_surface role - once. If get_xdg_surface is called with a wl_surface that already has - an active xdg_surface associated with it, or if it had any other role, - an error is raised. - - See the documentation of xdg_surface for more details about what an - xdg_surface is and how it is used. - - - - - - - - This creates an xdg_popup for the given surface and gives it the - xdg_popup role. A wl_surface can only be given an xdg_popup role - once. If get_xdg_popup is called with a wl_surface that already has - an active xdg_popup associated with it, or if it had any other role, - an error is raised. - - This request must be used in response to some sort of user action - like a button press, key press, or touch down event. - - See the documentation of xdg_popup for more details about what an - xdg_popup is and how it is used. - - - - - - - - - - - - - The ping event asks the client if it's still alive. Pass the - serial specified in the event back to the compositor by sending - a "pong" request back with the specified serial. - - Compositors can use this to determine if the client is still - alive. It's unspecified what will happen if the client doesn't - respond to the ping request, or in what timeframe. Clients should - try to respond in a reasonable amount of time. - - A compositor is free to ping in any way it wants, but a client must - always respond to any xdg_shell object it created. - - - - - - - A client must respond to a ping event with a pong request or - the client may be deemed unresponsive. - - - - - - - - An interface that may be implemented by a wl_surface, for - implementations that provide a desktop-style user interface. - - It provides requests to treat surfaces like windows, allowing to set - properties like maximized, fullscreen, minimized, and to move and resize - them, and associate metadata like title and app id. - - The client must call wl_surface.commit on the corresponding wl_surface - for the xdg_surface state to take effect. Prior to committing the new - state, it can set up initial configuration, such as maximizing or setting - a window geometry. - - Even without attaching a buffer the compositor must respond to initial - committed configuration, for instance sending a configure event with - expected window geometry if the client maximized its surface during - initialization. - - For a surface to be mapped by the compositor the client must have - committed both an xdg_surface state and a buffer. - - - - - Unmap and destroy the window. The window will be effectively - hidden from the user's point of view, and all state like - maximization, fullscreen, and so on, will be lost. - - - - - - Set the "parent" of this surface. This window should be stacked - above a parent. The parent surface must be mapped as long as this - surface is mapped. - - Parent windows should be set on dialogs, toolboxes, or other - "auxiliary" surfaces, so that the parent is raised when the dialog - is raised. - - - - - - - Set a short title for the surface. - - This string may be used to identify the surface in a task bar, - window list, or other user interface elements provided by the - compositor. - - The string must be encoded in UTF-8. - - - - - - - Set an application identifier for the surface. - - The app ID identifies the general class of applications to which - the surface belongs. The compositor can use this to group multiple - surfaces together, or to determine how to launch a new application. - - For D-Bus activatable applications, the app ID is used as the D-Bus - service name. - - The compositor shell will try to group application surfaces together - by their app ID. As a best practice, it is suggested to select app - ID's that match the basename of the application's .desktop file. - For example, "org.freedesktop.FooViewer" where the .desktop file is - "org.freedesktop.FooViewer.desktop". - - See the desktop-entry specification [0] for more details on - application identifiers and how they relate to well-known D-Bus - names and .desktop files. - - [0] http://standards.freedesktop.org/desktop-entry-spec/ - - - - - - - Clients implementing client-side decorations might want to show - a context menu when right-clicking on the decorations, giving the - user a menu that they can use to maximize or minimize the window. - - This request asks the compositor to pop up such a window menu at - the given position, relative to the local surface coordinates of - the parent surface. There are no guarantees as to what menu items - the window menu contains. - - This request must be used in response to some sort of user action - like a button press, key press, or touch down event. - - - - - - - - - - - Start an interactive, user-driven move of the surface. - - This request must be used in response to some sort of user action - like a button press, key press, or touch down event. - - The server may ignore move requests depending on the state of - the surface (e.g. fullscreen or maximized). - - - - - - - - These values are used to indicate which edge of a surface - is being dragged in a resize operation. The server may - use this information to adapt its behavior, e.g. choose - an appropriate cursor image. - - - - - - - - - - - - - - - Start a user-driven, interactive resize of the surface. - - This request must be used in response to some sort of user action - like a button press, key press, or touch down event. - - The server may ignore resize requests depending on the state of - the surface (e.g. fullscreen or maximized). - - - - - - - - - The different state values used on the surface. This is designed for - state values like maximized, fullscreen. It is paired with the - configure event to ensure that both the client and the compositor - setting the state can be synchronized. - - States set in this way are double-buffered. They will get applied on - the next commit. - - Desktop environments may extend this enum by taking up a range of - values and documenting the range they chose in this description. - They are not required to document the values for the range that they - chose. Ideally, any good extensions from a desktop environment should - make its way into standardization into this enum. - - The current reserved ranges are: - - 0x0000 - 0x0FFF: xdg-shell core values, documented below. - 0x1000 - 0x1FFF: GNOME - - - - The surface is maximized. The window geometry specified in the configure - event must be obeyed by the client. - - - - - The surface is fullscreen. The window geometry specified in the configure - event must be obeyed by the client. - - - - - The surface is being resized. The window geometry specified in the - configure event is a maximum; the client cannot resize beyond it. - Clients that have aspect ratio or cell sizing configuration can use - a smaller size, however. - - - - - Client window decorations should be painted as if the window is - active. Do not assume this means that the window actually has - keyboard or pointer focus. - - - - - - - The configure event asks the client to resize its surface or to - change its state. - - The width and height arguments specify a hint to the window - about how its surface should be resized in window geometry - coordinates. See set_window_geometry. - - If the width or height arguments are zero, it means the client - should decide its own window dimension. This may happen when the - compositor need to configure the state of the surface but doesn't - have any information about any previous or expected dimension. - - The states listed in the event specify how the width/height - arguments should be interpreted, and possibly how it should be - drawn. - - Clients should arrange their surface for the new size and - states, and then send a ack_configure request with the serial - sent in this configure event at some point before committing - the new surface. - - If the client receives multiple configure events before it - can respond to one, it is free to discard all but the last - event it received. - - - - - - - - - - - When a configure event is received, if a client commits the - surface in response to the configure event, then the client - must make a ack_configure request before the commit request, - passing along the serial of the configure event. - - For instance, the compositor might use this information to move - a surface to the top left only when the client has drawn itself - for the maximized or fullscreen state. - - If the client receives multiple configure events before it - can respond to one, it only has to ack the last configure event. - - - - - - - The window geometry of a window is its "visible bounds" from the - user's perspective. Client-side decorations often have invisible - portions like drop-shadows which should be ignored for the - purposes of aligning, placing and constraining windows. - - The window geometry is double buffered, and will be applied at the - time wl_surface.commit of the corresponding wl_surface is called. - - Once the window geometry of the surface is set once, it is not - possible to unset it, and it will remain the same until - set_window_geometry is called again, even if a new subsurface or - buffer is attached. - - If never set, the value is the full bounds of the surface, - including any subsurfaces. This updates dynamically on every - commit. This unset mode is meant for extremely simple clients. - - If responding to a configure event, the window geometry in here - must respect the sizing negotiations specified by the states in - the configure event. - - The arguments are given in the surface local coordinate space of - the wl_surface associated with this xdg_surface. - - The width and height must be greater than zero. - - - - - - - - - - Maximize the surface. - - After requesting that the surface should be maximized, the compositor - will respond by emitting a configure event with the "maximized" state - and the required window geometry. The client should then update its - content, drawing it in a maximized state, i.e. without shadow or other - decoration outside of the window geometry. The client must also - acknowledge the configure when committing the new content (see - ack_configure). - - It is up to the compositor to decide how and where to maximize the - surface, for example which output and what region of the screen should - be used. - - If the surface was already maximized, the compositor will still emit - a configure event with the "maximized" state. - - - - - - Unmaximize the surface. - - After requesting that the surface should be unmaximized, the compositor - will respond by emitting a configure event without the "maximized" - state. If available, the compositor will include the window geometry - dimensions the window had prior to being maximized in the configure - request. The client must then update its content, drawing it in a - regular state, i.e. potentially with shadow, etc. The client must also - acknowledge the configure when committing the new content (see - ack_configure). - - It is up to the compositor to position the surface after it was - unmaximized; usually the position the surface had before maximizing, if - applicable. - - If the surface was already not maximized, the compositor will still - emit a configure event without the "maximized" state. - - - - - - Make the surface fullscreen. - - You can specify an output that you would prefer to be fullscreen. - If this value is NULL, it's up to the compositor to choose which - display will be used to map this surface. - - If the surface doesn't cover the whole output, the compositor will - position the surface in the center of the output and compensate with - black borders filling the rest of the output. - - - - - - - - Request that the compositor minimize your surface. There is no - way to know if the surface is currently minimized, nor is there - any way to unset minimization on this surface. - - If you are looking to throttle redrawing when minimized, please - instead use the wl_surface.frame event for this, as this will - also work with live previews on windows in Alt-Tab, Expose or - similar compositor features. - - - - - - The close event is sent by the compositor when the user - wants the surface to be closed. This should be equivalent to - the user clicking the close button in client-side decorations, - if your application has any... - - This is only a request that the user intends to close your - window. The client may choose to ignore this request, or show - a dialog to ask the user to save their data... - - - - - - - A popup surface is a short-lived, temporary surface that can be - used to implement menus. It takes an explicit grab on the surface - that will be dismissed when the user dismisses the popup. This can - be done by the user clicking outside the surface, using the keyboard, - or even locking the screen through closing the lid or a timeout. - - When the popup is dismissed, a popup_done event will be sent out, - and at the same time the surface will be unmapped. The xdg_popup - object is now inert and cannot be reactivated, so clients should - destroy it. Explicitly destroying the xdg_popup object will also - dismiss the popup and unmap the surface. - - Clients will receive events for all their surfaces during this - grab (which is an "owner-events" grab in X11 parlance). This is - done so that users can navigate through submenus and other - "nested" popup windows without having to dismiss the topmost - popup. - - Clients that want to dismiss the popup when another surface of - their own is clicked should dismiss the popup using the destroy - request. - - The parent surface must have either an xdg_surface or xdg_popup - role. - - Specifying an xdg_popup for the parent means that the popups are - nested, with this popup now being the topmost popup. Nested - popups must be destroyed in the reverse order they were created - in, e.g. the only popup you are allowed to destroy at all times - is the topmost one. - - If there is an existing popup when creating a new popup, the - parent must be the current topmost popup. - - A parent surface must be mapped before the new popup is mapped. - - When compositors choose to dismiss a popup, they will likely - dismiss every nested popup as well. When a compositor dismisses - popups, it will follow the same dismissing order as required - from the client. - - The x and y arguments passed when creating the popup object specify - where the top left of the popup should be placed, relative to the - local surface coordinates of the parent surface. See - xdg_shell.get_xdg_popup. - - The client must call wl_surface.commit on the corresponding wl_surface - for the xdg_popup state to take effect. - - For a surface to be mapped by the compositor the client must have - committed both the xdg_popup state and a buffer. - - - - - This destroys the popup. Explicitly destroying the xdg_popup - object will also dismiss the popup, and unmap the surface. - - If this xdg_popup is not the "topmost" popup, a protocol error - will be sent. - - - - - - The popup_done event is sent out when a popup is dismissed by the - compositor. The client should destroy the xdg_popup object at this - point. - - - - - -- 2.7.4 From ddd1269985f4891bbed3bf2627dd9541df226507 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Mon, 19 Mar 2018 16:28:50 +0900 Subject: [PATCH 06/16] Packaging: update version to 1.2.0 Change-Id: If65a10699b5f2cf05712660a9d6bfa845153cf85 --- packaging/wayland-extension.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/wayland-extension.spec b/packaging/wayland-extension.spec index 390c49a..8633fc9 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.1.31 +Version: 1.2.0 Release: 0 Summary: Wayland extenstion protocols that add functionality not available in the Wayland core protocol License: MIT -- 2.7.4 From 6043c99bbd8bb86f61ac01a724c1c6f678635a84 Mon Sep 17 00:00:00 2001 From: JengHyun Kang Date: Mon, 2 Apr 2018 14:12:16 +0900 Subject: [PATCH 07/16] tizen_keyrouter: add a new event to deliver event surface Change-Id: Icd03c88b93642e34938f9ec3e93db38cf49a9974 --- protocol/tizen/tizen-extension.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/protocol/tizen/tizen-extension.xml b/protocol/tizen/tizen-extension.xml index 960c73e..4b66f13 100644 --- a/protocol/tizen/tizen-extension.xml +++ b/protocol/tizen/tizen-extension.xml @@ -564,7 +564,7 @@ - + In tradition, all the keys in a keyboard and a device on which some keys are attached will be sent to focus surface by default. @@ -704,7 +704,11 @@ Destroy the tizen_keyrouter. - + + + + + -- 2.7.4 From 73688d9154f961c9eb3f64d6aebe209a3b53027f Mon Sep 17 00:00:00 2001 From: JengHyun Kang Date: Fri, 13 Apr 2018 14:28:29 +0900 Subject: [PATCH 08/16] Packaging: update version to 1.2.1 Change-Id: Ie833c3dfebe188d59d3e9f99773d296775f70c5c --- packaging/wayland-extension.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/wayland-extension.spec b/packaging/wayland-extension.spec index 8633fc9..827779a 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.2.0 +Version: 1.2.1 Release: 0 Summary: Wayland extenstion protocols that add functionality not available in the Wayland core protocol License: MIT -- 2.7.4 From dcb2cca149bb9d704fe4c015af9983241d7c7c74 Mon Sep 17 00:00:00 2001 From: InHong Han Date: Thu, 19 Apr 2018 20:39:40 +0900 Subject: [PATCH 09/16] text: Add a enum name of preedit_style Change-Id: Ia761e2dae4071a8dc3aff22c129078d2bb5d26af --- protocol/tizen/text.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/protocol/tizen/text.xml b/protocol/tizen/text.xml index 662c44d..03d74ac 100644 --- a/protocol/tizen/text.xml +++ b/protocol/tizen/text.xml @@ -355,6 +355,11 @@ + + + + + -- 2.7.4 From e6be1b075892e9afa5430c3ff6cf6de5cf65a5f1 Mon Sep 17 00:00:00 2001 From: Jihoon Kim Date: Fri, 20 Apr 2018 08:58:47 +0900 Subject: [PATCH 10/16] Packaging: update version to 1.2.2 Change-Id: I74f79ea9076377d1019978cb96b3195a62d638de Signed-off-by: Jihoon Kim --- packaging/wayland-extension.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/wayland-extension.spec b/packaging/wayland-extension.spec index 827779a..7b7b955 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.2.1 +Version: 1.2.2 Release: 0 Summary: Wayland extenstion protocols that add functionality not available in the Wayland core protocol License: MIT -- 2.7.4 From f5dd53e5e72c525c55890bf2c63b9e74f93b6609 Mon Sep 17 00:00:00 2001 From: Jihoon Kim Date: Mon, 18 Jun 2018 17:36:01 +0900 Subject: [PATCH 11/16] text: Remove security code enum in autofill type Change-Id: I50c0e09873bf4d2fefcf6b459defb68e60c62631 Signed-off-by: Jihoon Kim --- protocol/tizen/text.xml | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/protocol/tizen/text.xml b/protocol/tizen/text.xml index 03d74ac..f81168c 100644 --- a/protocol/tizen/text.xml +++ b/protocol/tizen/text.xml @@ -111,13 +111,12 @@ - - - - - - - + + + + + + -- 2.7.4 From bfa9396510040d050fbb1953d8f6b4f55e4e6644 Mon Sep 17 00:00:00 2001 From: Jihoon Kim Date: Mon, 18 Jun 2018 17:36:33 +0900 Subject: [PATCH 12/16] Packaging: update version to 1.2.3 Change-Id: I7b694775d5445b3e88ebb0f214b8d5b8e4145e84 Signed-off-by: Jihoon Kim --- packaging/wayland-extension.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/wayland-extension.spec b/packaging/wayland-extension.spec index 7b7b955..82a984a 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.2.2 +Version: 1.2.3 Release: 0 Summary: Wayland extenstion protocols that add functionality not available in the Wayland core protocol License: MIT -- 2.7.4 From f6f73b0789eea3bb1fb02b6c7a4ca92f259a2535 Mon Sep 17 00:00:00 2001 From: Juyeon Lee Date: Wed, 20 Jun 2018 16:29:22 +0900 Subject: [PATCH 13/16] tizen-extension: add tizen_move_resize iface added tizen_move_resize interface, it has request for a wl_surface to move, resize at the same time by passing x,y,w,h geometry params Change-Id: I375390632170fc7b8c6d3a7e0800a0d9bf539eb8 --- protocol/tizen/tizen-extension.xml | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/protocol/tizen/tizen-extension.xml b/protocol/tizen/tizen-extension.xml index 4b66f13..22299b8 100644 --- a/protocol/tizen/tizen-extension.xml +++ b/protocol/tizen/tizen-extension.xml @@ -19,7 +19,7 @@ - + @@ -347,6 +347,11 @@ + + + + + @@ -384,6 +389,16 @@ + + + + + + + + + + -- 2.7.4 From e1e923079ab6769ba6bee75418c20e67906f520f Mon Sep 17 00:00:00 2001 From: Juyeon Lee Date: Wed, 20 Jun 2018 17:27:44 +0900 Subject: [PATCH 14/16] fix build break Change-Id: Iaa218b0abb82d61bc82c93ab166a3a63c29ef2e4 --- protocol/tizen/tizen-extension.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/protocol/tizen/tizen-extension.xml b/protocol/tizen/tizen-extension.xml index 22299b8..a3d351f 100644 --- a/protocol/tizen/tizen-extension.xml +++ b/protocol/tizen/tizen-extension.xml @@ -389,6 +389,7 @@ + -- 2.7.4 From 8a9404fad74c9e8c3c594e718f0ab4727a45fd0b Mon Sep 17 00:00:00 2001 From: InHong Han Date: Tue, 21 Aug 2018 11:32:11 +0900 Subject: [PATCH 15/16] input-method: Add reshow_input_panel protocol Change-Id: I7cb20076e85ff01d3fdad0b669ae393b77887534 --- protocol/tizen/input-method.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/protocol/tizen/input-method.xml b/protocol/tizen/input-method.xml index fb28774..705342b 100644 --- a/protocol/tizen/input-method.xml +++ b/protocol/tizen/input-method.xml @@ -246,6 +246,11 @@ + + + This is a request to send show event after IME is restarted. + + -- 2.7.4 From 3a3886b2add30e035712f94d278e9e970b8f891a Mon Sep 17 00:00:00 2001 From: InHong Han Date: Wed, 22 Aug 2018 10:19:51 +0900 Subject: [PATCH 16/16] Packaging: update version to 1.2.4 Change-Id: I75dc178a497f674d34e2560517c61814ed74d09f --- packaging/wayland-extension.spec | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packaging/wayland-extension.spec b/packaging/wayland-extension.spec index 82a984a..67e27ea 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.2.3 +Version: 1.2.4 Release: 0 Summary: Wayland extenstion protocols that add functionality not available in the Wayland core protocol License: MIT -- 2.7.4