Re: [PATCH wayland-protocols v4 2/7] xdg-shell: Put xdg_shell events after requests

2016-07-20 Thread Quentin Glidic

On 24/06/2016 08:47, Jonas Ådahl wrote:

It makes the structure consistent with most other protocols and
provides a clear separation between what is done by the server and what
is done by the client.

Signed-off-by: Jonas Ådahl 
Reviewed-by: Yong Bakos 
Reviewed-by: Mike Blumenkrantz 
---


Just moving stuff around so:
Reviewed-by: Quentin Glidic 

Cheers,




Changes since v3:

 - Added 'See xdg_shell.ping/pong' to xdg_shell.pong/ping.

 unstable/xdg-shell/xdg-shell-unstable-v6.xml | 74 ++--
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml 
b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
index 3268077..a7294dc 100644
--- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml
+++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
@@ -70,11 +70,19 @@
   
 

+
+  
+   A client must respond to a ping event with a pong request or
+   the client may be deemed unresponsive. See xdg_shell.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.
+   a "pong" request back with the specified serial. See xdg_shell.ping.

Compositors can use this to determine if the client is still
alive. It's unspecified what will happen if the client doesn't
@@ -86,14 +94,6 @@
   
   
 
-
-
-  
-   A client must respond to a ping event with a pong request or
-   the client may be deemed unresponsive.
-  
-  
-
   

   
@@ -471,34 +471,6 @@
   
 

-
-  
-   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 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 must send an ack_configure in response to this event. See
-   xdg_surface.configure and xdg_surface.ack_configure for details.
-  
-
-  
-  
-  
-
-
 
   
Set a maximum size for the window.
@@ -653,6 +625,34 @@
   
 

+
+  
+   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 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 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




--

Quentin “Sardem FF7” Glidic
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel


[PATCH wayland-protocols v4 2/7] xdg-shell: Put xdg_shell events after requests

2016-06-23 Thread Jonas Ådahl
It makes the structure consistent with most other protocols and
provides a clear separation between what is done by the server and what
is done by the client.

Signed-off-by: Jonas Ådahl 
Reviewed-by: Yong Bakos 
Reviewed-by: Mike Blumenkrantz 
---

Changes since v3:

 - Added 'See xdg_shell.ping/pong' to xdg_shell.pong/ping.

 unstable/xdg-shell/xdg-shell-unstable-v6.xml | 74 ++--
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/unstable/xdg-shell/xdg-shell-unstable-v6.xml 
b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
index 3268077..a7294dc 100644
--- a/unstable/xdg-shell/xdg-shell-unstable-v6.xml
+++ b/unstable/xdg-shell/xdg-shell-unstable-v6.xml
@@ -70,11 +70,19 @@
   
 
 
+
+  
+   A client must respond to a ping event with a pong request or
+   the client may be deemed unresponsive. See xdg_shell.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.
+   a "pong" request back with the specified serial. See xdg_shell.ping.
 
Compositors can use this to determine if the client is still
alive. It's unspecified what will happen if the client doesn't
@@ -86,14 +94,6 @@
   
   
 
-
-
-  
-   A client must respond to a ping event with a pong request or
-   the client may be deemed unresponsive.
-  
-  
-
   
 
   
@@ -471,34 +471,6 @@
   
 
 
-
-  
-   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 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 must send an ack_configure in response to this event. See
-   xdg_surface.configure and xdg_surface.ack_configure for details.
-  
-
-  
-  
-  
-
-
 
   
Set a maximum size for the window.
@@ -653,6 +625,34 @@
   
 
 
+
+  
+   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 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 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
-- 
2.5.5

___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel