From a89d9c632f3661780e25ae9bc5760735152a48b3 Mon Sep 17 00:00:00 2001 From: Duna Oh Date: Tue, 6 Oct 2015 17:43:17 +0900 Subject: [PATCH 01/16] tizen-policy: add a request 'lower_by_res_id' Signed-off-by: Duna Oh Change-Id: Ia47255ef8b15de36bc668057713291ff02be8c1b --- protocol/tizen-extension.xml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 0985eff..1083a37 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -38,6 +38,10 @@ + + + + -- 2.7.4 From 14ac41434e411b39fac8baf790a76b30ec86367c Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Wed, 7 Oct 2015 16:47:31 +0900 Subject: [PATCH 02/16] Packaging: update version to 1.0.9 Change-Id: Icb39ce54115eceaad3569ba4a200cece61ed8396 --- 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 1857ddf..f24ddea 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.8 +Version: 1.0.9 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From e60d25baa5739e355aa70fd6bfae93703bcd1e2a Mon Sep 17 00:00:00 2001 From: Boram Park Date: Thu, 8 Oct 2015 16:46:04 +0900 Subject: [PATCH 03/16] remove tizen_buffer_pool interface Change-Id: Id21a90e374248964a843391ba6ab6fa85e11953b --- protocol/tizen-extension.xml | 121 ------------------------------------------- 1 file changed, 121 deletions(-) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 1083a37..8026fec 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -391,127 +391,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- 2.7.4 From ab4b03f5a9b659369fafafe54e551af61af6ebf7 Mon Sep 17 00:00:00 2001 From: Boram Park Date: Thu, 8 Oct 2015 16:46:35 +0900 Subject: [PATCH 04/16] Packaging: update version to 1.0.10 Change-Id: I009634442ac51ac5c31bef1199b8ab7479a6c328 --- 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 f24ddea..cf0897d 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.9 +Version: 1.0.10 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From c2e543618434262d33ce49addf63f710803adf67 Mon Sep 17 00:00:00 2001 From: Duna Oh Date: Tue, 20 Oct 2015 12:58:16 +0900 Subject: [PATCH 05/16] tizen-policy: add a request 'set_type' for notification window Signed-off-by: Duna Oh Change-Id: Id3d6cc138ea5b49032c4887a762d0fe8e55ee4fb --- protocol/tizen-extension.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 8026fec..31d7164 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -55,6 +55,23 @@ + + + + + + + + + + + + + + + + + -- 2.7.4 From bd0f9985775e34a321334617dd987d0982df3f39 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Sun, 8 Nov 2015 17:30:46 +0900 Subject: [PATCH 06/16] Packaging: update version to 1.0.11 Change-Id: I075a0dd71ab22025fb54fa42f608308a0f852f85 --- 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 cf0897d..ae2eefa 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.10 +Version: 1.0.11 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From d3765e50113ac1c5f2dfb63928f55ed2bd21038c Mon Sep 17 00:00:00 2001 From: JengHyun Kang Date: Fri, 6 Nov 2015 19:42:39 +0900 Subject: [PATCH 07/16] Add a new grab mode named Registered Change-Id: Id2444a71d1e7b84ccedace4840a3be059b33d26e --- protocol/tizen-extension.xml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 31d7164..637b280 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -283,6 +283,8 @@ summary="mode to get a key grab exclusively, overridably regardless of the order in the surface stack"/> + -- 2.7.4 From 3822919c003a41bfbac7f634c46e372102cc1ff8 Mon Sep 17 00:00:00 2001 From: JengHyun Kang Date: Tue, 10 Nov 2015 14:39:26 +0900 Subject: [PATCH 08/16] Fix a syntax error Change-Id: I068f507480858675f21fafa3c595ac41a835d12c --- protocol/tizen-extension.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 637b280..a8d4cc4 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -284,7 +284,7 @@ + summary="mode to get a key grab only when a requesting surface is on top among the registering surfaces for the key"/> -- 2.7.4 From 6e0cf1eb5df0e3cf45426d9bd86ccd738d4b06ef Mon Sep 17 00:00:00 2001 From: Sung-Jin Park Date: Tue, 10 Nov 2015 19:53:11 +0900 Subject: [PATCH 09/16] Packaging: update version to 1.0.12 Change-Id: I00500e4a9c988f569f680baec162d11b2307b087 --- 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 ae2eefa..6a18bc0 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.11 +Version: 1.0.12 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From 8a940799c906a7d316131d2842b518f5fdd55c39 Mon Sep 17 00:00:00 2001 From: MinJeong Kim Date: Fri, 6 Nov 2015 22:38:57 +0900 Subject: [PATCH 10/16] xdg_shell: update version to 5 Change-Id: I1f9da232687e6256fef42a894ba3e6f27254bcbc --- protocol/xdg-shell.xml | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml index b0e4343..a4335f1 100644 --- a/protocol/xdg-shell.xml +++ b/protocol/xdg-shell.xml @@ -45,13 +45,26 @@ 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 @@ -152,7 +165,7 @@ unmapped if the parent is unmapped too. They should not appear on task bars and alt+tab. - + @@ -362,8 +375,6 @@ - - The close event is sent by the compositor when the user @@ -417,7 +428,6 @@ that is, when the users clicks a surface that doesn't belong to the client owning the popup surface. - -- 2.7.4 From 0e8b7c20afa31ec408fe53b5144f308751904ca6 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Wed, 11 Nov 2015 14:20:40 +0900 Subject: [PATCH 11/16] xdg_shell: Update descriptions Change-Id: I53f5261ded95c8d71c1ca50bc79b927ff9295231 --- protocol/xdg-shell.xml | 362 ++++++++++++++++++++++++++++++++++--------------- 1 file changed, 254 insertions(+), 108 deletions(-) diff --git a/protocol/xdg-shell.xml b/protocol/xdg-shell.xml index a4335f1..44a3a12 100644 --- a/protocol/xdg-shell.xml +++ b/protocol/xdg-shell.xml @@ -31,11 +31,10 @@ - This interface is implemented by servers that provide - desktop-style user interfaces. - - It allows clients to associate a xdg_surface with - a basic surface. + 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. @@ -78,36 +77,40 @@ - Create a shell surface for an existing surface. - - This request gives the surface the role of xdg_surface. If the - surface already has another role, it raises a protocol error. - - Only one shell or popup surface can be associated with a given - surface. + 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. - - Create a popup surface for an existing surface. - - This request gives the surface the role of xdg_popup. If the - surface already has another role, it raises a protocol error. - - Only one shell or popup surface can be associated with a given - surface. + + 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. - - + + - @@ -120,8 +123,11 @@ 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. - + @@ -134,8 +140,7 @@ - - + An interface that may be implemented by a wl_surface, for implementations that provide a desktop-style user interface. @@ -143,27 +148,37 @@ properties like maximized, fullscreen, minimized, and to move and resize them, and associate metadata like title and app id. - On the server side the object is automatically destroyed when - the related wl_surface is destroyed. On client side, - xdg_surface.destroy() must be called before destroying - the wl_surface object. + 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. - - The xdg_surface interface is removed from the wl_surface object - that was turned into a xdg_surface with - xdg_shell.get_xdg_surface request. The xdg_surface properties, - like maximized and fullscreen, are lost. The wl_surface loses - its role as a xdg_surface. The wl_surface is unmapped. + + 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. - - Child surfaces are stacked above their parents, and will be - unmapped if the parent is unmapped too. They should not appear - on task bars and alt+tab. + + 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. @@ -182,14 +197,27 @@ - - Set an id for the surface. + + Set an application identifier for the surface. - The app id identifies the general class of applications to which - the surface belongs. + 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. - It should be the ID that appears in the new desktop entry - specification, the interface name. + 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/ @@ -201,29 +229,32 @@ 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 parent surface. There are - no guarantees as to what the window menu contains. + 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. - Your surface must have focus on the seat passed in to pop up the - window menu. + This request must be used in response to some sort of user action + like a button press, key press, or touch down event. - - + + - Start a pointer-driven move of the surface. + 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. - This request must be used in response to a button press event. The server may ignore move requests depending on the state of the surface (e.g. fullscreen or maximized). - - + + @@ -246,14 +277,16 @@ - Start a pointer-driven resizing of the surface. + 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. - This request must be used in response to a button press event. The server may ignore resize requests depending on the state of the surface (e.g. fullscreen or maximized). - - + + @@ -301,16 +334,26 @@ - The configure event asks the client to resize its surface. + 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. The states listed in the event specify how the - width/height arguments should be interpreted. + about how its surface should be resized in window geometry + coordinates. See set_window_geometry. - A client should arrange a new surface, and then send a - ack_configure request with the serial sent in this configure - event before attaching a new surface. + 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 @@ -325,14 +368,19 @@ - When a configure event is received, a client should then ack it - using the ack_configure request to ensure that the compositor - knows the client has seen the event. + 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. - By this point, the state is confirmed, and the next attach should - contain the buffer drawn for the configure event you are acking. + If the client receives multiple configure events before it + can respond to one, it only has to ack the last configure event. - + @@ -342,15 +390,26 @@ portions like drop-shadows which should be ignored for the purposes of aligning, placing and constraining windows. - The default value is the full bounds of the surface, including any - subsurfaces. Once the window geometry of the surface is set once, - it is not possible to unset it, and it will remain the same until + 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. @@ -358,8 +417,48 @@ - - + + + 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. + + @@ -368,12 +467,27 @@ 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. + + @@ -390,43 +504,75 @@ - - An interface that may be implemented by a wl_surface, for - implementations that provide a desktop-style popups/menus. A popup - surface is a transient surface with an added pointer grab. - - An existing implicit grab will be changed to owner-events mode, - and the popup grab will continue after the implicit grab ends - (i.e. releasing the mouse button does not cause the popup to be - unmapped). - - The popup grab continues until the window is destroyed or a mouse - button is pressed in any other clients window. A click in any of - the clients surfaces is reported as normal, however, clicks in - other clients surfaces will be discarded and trigger the callback. - - The x and y arguments specify the locations of the upper left - corner of the surface relative to the upper left corner of the - parent surface, in surface local coordinates. - - xdg_popup surfaces are always transient for another surface. + + 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. - - The xdg_surface interface is removed from the wl_surface object - that was turned into a xdg_surface with - xdg_shell.get_xdg_surface request. The xdg_surface properties, - like maximized and fullscreen, are lost. The wl_surface loses - its role as a xdg_surface. The wl_surface is unmapped. + + 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 grab is broken, - that is, when the users clicks a surface that doesn't belong - to the client owning the popup 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. -- 2.7.4 From 33833dd07419a96f0f6efeb3096160ccaa53e036 Mon Sep 17 00:00:00 2001 From: Gwanglim Lee Date: Wed, 18 Nov 2015 20:39:13 +0900 Subject: [PATCH 12/16] Packaging: update version to 1.0.13 Change-Id: I66f5eb962997da570388fd3717110aff52bf7c42 --- 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 6a18bc0..3b2c054 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.12 +Version: 1.0.13 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From ce2bdb96c269e0ac5f6d317d39bbf951ea7539e9 Mon Sep 17 00:00:00 2001 From: Sangjin Lee Date: Fri, 13 Nov 2015 21:45:51 +0900 Subject: [PATCH 13/16] add new protocol for embedded compositor Change-Id: I3d58ce462c3b0e143b4aa6aaf4337d1fe2441e0f --- protocol/tizen-extension.xml | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index a8d4cc4..1e627aa 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -426,4 +426,26 @@ + + + + The global obejct. Wayland has 3 type of compositor, embedded compositor is one of them. + But tizen application is sendboxing by smack, then a application not allow commutication to other application by socket. + So system or session compositor create socket and send to embedded compostior. + + + + + The get_socket request ask the server to create socket and emit socket event. + + + + + + Sent immediately after get_socket request + + + + + -- 2.7.4 From e43f0ea7ad2443e0816b0db8a20b5a8355e968ec Mon Sep 17 00:00:00 2001 From: Boram Park Date: Tue, 24 Nov 2015 15:16:24 +0900 Subject: [PATCH 14/16] Packaging: update version to 1.0.14 Change-Id: I3969bd4f115abccfdd9c2adc5380290f6e0175c3 --- 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 3b2c054..ab1e11c 100644 --- a/packaging/wayland-extension.spec +++ b/packaging/wayland-extension.spec @@ -1,5 +1,5 @@ Name: wayland-extension -Version: 1.0.13 +Version: 1.0.14 Release: 0 Summary: Wayland Extension Protocol License: MIT -- 2.7.4 From 78c94187f6ad6ad8337e0b14a575513000b49a0b Mon Sep 17 00:00:00 2001 From: Boram Park Date: Wed, 25 Nov 2015 21:35:31 +0900 Subject: [PATCH 15/16] add tizen_video_object interface Change-Id: Ideee6954a34cce1bb2eba55ff7bc84a14bc41439 --- protocol/tizen-extension.xml | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/protocol/tizen-extension.xml b/protocol/tizen-extension.xml index 1e627aa..ae4fbc9 100644 --- a/protocol/tizen-extension.xml +++ b/protocol/tizen-extension.xml @@ -416,6 +416,11 @@ Clients can get the video information that the compositor can handle from this interface. + + + + + The tbm format codes match the #defines in tbm_surface.h. The formats actually @@ -424,6 +429,34 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + -- 2.7.4 From 9fb580c99d8a744b0d887d00a33bbb6d75873c9e Mon Sep 17 00:00:00 2001 From: Li Zhang Date: Tue, 1 Dec 2015 21:00:16 +0800 Subject: [PATCH 16/16] input-method, text: update descriptions Change-Id: Ieae3f3819a205e616783b2c9818fd2960515c9d0 --- protocol/input-method.xml | 17 +++++++---------- protocol/text.xml | 47 +++++++++++++++++++++++------------------------ 2 files changed, 30 insertions(+), 34 deletions(-) diff --git a/protocol/input-method.xml b/protocol/input-method.xml index a10d3f0..87feca8 100644 --- a/protocol/input-method.xml +++ b/protocol/input-method.xml @@ -25,7 +25,6 @@ THIS SOFTWARE. - Corresponds to a text model on input method side. An input method context @@ -75,10 +74,10 @@ - Sets styling information on composing text. The style is applied for - length in bytes from index relative to the beginning of - the composing text (as byte offset). Multiple styles can - be applied to a composing text. + Set styling information on composing text. The style is applied for + length in bytes from index relative to the beginning of the composing + text (as byte offset). Multiple styles can be applied to a composing + text. This request should be sent before sending preedit_string request. @@ -88,7 +87,7 @@ - Sets the cursor position inside the composing text (as byte offset) + Set the cursor position inside the composing text (as byte offset) relative to the start of the composing text. When index is negative no cursor should be displayed. @@ -99,8 +98,6 @@ - - This request will be handled on text_input side as part of a directly following commit_string request. @@ -109,7 +106,7 @@ - Sets the cursor and anchor to a new position. Index is the new cursor + Set the cursor and anchor to a new position. Index is the new cursor position in bytes (when >= 0 relative to the end of inserted text else relative to beginning of inserted text). Anchor is the new anchor position in bytes (when >= 0 relative to the end of inserted text, else @@ -276,7 +273,7 @@ - A keyboard surface is only shown, when a text model is active + A keyboard surface is only shown, when a text model is active. diff --git a/protocol/text.xml b/protocol/text.xml index 454a531..9a4e6ad 100644 --- a/protocol/text.xml +++ b/protocol/text.xml @@ -28,7 +28,7 @@ - An object used for text input. Adds support for text input and input + An object used for text input. Adds support for text input and input methods to applications. A text-input object is created from a wl_text_input_manager and corresponds typically to a text entry in an application. @@ -50,7 +50,7 @@ - Requests the text-input object to be activated (typically when the + Requests the text-input object to be activated (typically when the text entry gets focus). The seat argument is a wl_seat which maintains the focus for this activation. The surface argument is a wl_surface assigned to the @@ -86,8 +86,8 @@ - - Sets the plain surrounding text around the input position. Text is + + Set the plain surrounding text around the input position. Text is UTF-8 encoded. Cursor is the byte offset within the surrounding text. Anchor is the byte offset of the selection anchor within the surrounding text. If there is no selected @@ -142,7 +142,7 @@ - Sets the content purpose and content hint. While the purpose is the + Set the content purpose and content hint. While the purpose is the basic purpose of an input field, the hint flags allow to modify some of the behavior. @@ -160,14 +160,14 @@ - - Sets a specific language. This allows for example a virtual keyboard to - show a language specific layout. The "language" argument is a RFC-3066 - format language tag. + + Set a specific language. This allows for example a virtual keyboard to + show a language specific layout. The "language" argument is a RFC-3066 + format language tag. - It could be used for example in a word processor to indicate language of - currently edited document or in an instant message application which tracks - languages of contacts. + It could be used for example in a word processor to indicate language of + currently edited document or in an instant message application which tracks + languages of contacts. @@ -193,7 +193,7 @@ - Sets the return key type. + Set the return key type. @@ -249,10 +249,10 @@ be removed. The commit text can be used to replace the preedit text on reset - (for example on unfocus). + (for example on unfocus). - The text input should also handle all preedit_style and preedit_cursor - events occurring directly before preedit_string. + The text input should also handle all preedit_style and preedit_cursor + events occurring directly before preedit_string. @@ -270,11 +270,10 @@ - Sets styling information on composing text. The style is applied for - length bytes from index relative to the beginning of the composing - text (as byte offset). Multiple styles can - be applied to a composing text by sending multiple preedit_styling - events. + Set styling information on composing text. The style is applied for + length bytes from index relative to the beginning of the composing + text (as byte offset). Multiple styles can be applied to a composing + text by sending multiple preedit_styling events. This event is handled as part of a following preedit_string event. @@ -284,7 +283,7 @@ - Sets the cursor position inside the composing text (as byte + Set the cursor position inside the composing text (as byte offset) relative to the start of the composing text. When index is a negative number no cursor is shown. @@ -346,7 +345,7 @@ - Sets the language of the input text. The "language" argument is a RFC-3066 + Set the language of the input text. The "language" argument is a RFC-3066 format language tag. @@ -359,7 +358,7 @@ - Sets the text direction of input text. + Set the text direction of input text. It is mainly needed for showing input cursor on correct side of the editor when there is no input yet done and making sure neutral -- 2.7.4