third_party: Update to version 2 of remote_shell_protocol.

third_party/wayland-protocols/unstable/remote-shell/remote-shell-unstable-v1.xml

 <?xml version="1.0" encoding="UTF-8"?>
 <protocol name="remote_shell_unstable_v1">
 
   <copyright>
     Copyright 2016 The Chromium Authors.
 
     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,
@@ skipping 20 matching lines @@
     Warning! The protocol described in this file is experimental and backward
     incompatible changes may be made. Backward compatible changes may be added
     together with the corresponding interface version bump. Backward
     incompatible changes are done by bumping the version number in the protocol
     and interface names and resetting the interface version. Once the protocol
     is to be declared stable, the 'z' prefix and the version number in the
     protocol and interface names are removed and the interface version number is
     reset.
   </description>
 
-  <interface name="zwp_remote_shell_v1" version="1">
+  <interface name="zwp_remote_shell_v1" version="2">
     <description summary="remote_shell">
       The global interface that allows clients to turn a wl_surface into a
       "real window" which is remotely managed but can be stacked, activated
       and made fullscreen by the user.
     </description>
 
     <enum name="container">
       <description summary="containers for remote surfaces">
         Determine how a remote surface should be stacked relative to other
         shell surfaces.
@@ skipping 46 matching lines @@
 
     <event name="activated">
       <description summary="activated surface changed">
         Notifies client that the activated surface changed.
       </description>
       <arg name="gained_active" type="object" interface="wl_surface" allow-null="true"/>
       <arg name="lost_active" type="object" interface="wl_surface" allow-null="true"/>
     </event>
   </interface>
 
-  <interface name="zwp_remote_surface_v1" version="1">
+  <interface name="zwp_remote_surface_v1" version="2">
     <description summary="A desktop window">
       An interface that may be implemented by a wl_surface, for
       implementations that provide a desktop-style user interface
       and allows for remotely managed windows.
 
       It provides requests to treat surfaces like windows, allowing to set
       properties like app id and geometry.
 
       The client must call wl_surface.commit on the corresponding wl_surface
       for the remote_surface state to take effect.
@@ skipping 76 matching lines @@
         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...
       </description>
     </event>
+
+    <!-- Version 2 additions -->
+
+    <request name="fullscreen" since="2">
+      <description summary="fullscreen">
+        Request that surface is made fullscreen.
+
+        This is only a request that the window should be made fullscreen.
+        The compositor may choose to ignore this request. The client should
+        listen to set_fullscreen events to determine if the window was
+        made fullscreen or not.
+      </description>
+    </request>
+
+    <request name="maximize" since="2">
+      <description summary="maximize">
+        Request that surface is maximized. The window geometry will be updated
+        to whatever the compositor finds appropriate for a maximized window.
+
+        This is only a request that the window should be maximized. The
+        compositor may choose to ignore this request. The client should
+        listen to set_maximized events to determine if the window was
+        maximized or not.
+      </description>
+    </request>
+
+    <request name="minimize" since="2">
+      <description summary="minimize">
+        Request that surface is minimized.
+
+        This is only a request that the window should be maximized. The

[mtomasz, 2016/06/03 03:56:42]

nit: maximized -> minimized?

[reveman, 2016/06/03 11:25:30]

done

+        compositor may choose to ignore this request. The client should
+        listen to set_minimized events to determine if the window was
+        minimized or not.
+      </description>
+    </request>
+
+    <request name="restore" since="2">
+      <description summary="restore">
+        Request that surface is restored. This restores the window geometry
+        to what it was before the window was minimized, maximized or made
+        fullscreen.
+
+        This is only a request that the window should be restored. The
+        compositor may choose to ignore this request. The client should
+        listen to unset_maximized, unset_minimize and unset_fullscreen
+        events to determine if the window was restored or not.
+      </description>
+    </request>
+
+    <event name="set_maximized" since="2">
+      <description summary="surface wants to be maximized">
+        The set_maximized event is sent by the compositor when the user
+        wants the surface to be maximized.
+
+        This is only a request that the user intends to maximized the window.
+        The client may choose to ignore this request.
+      </description>
+    </event>
+
+    <event name="unset_maximized" since="2">
+      <description summary="surface wants to be restored">
+        The unset_maximized event is sent by the compositor when the user
+        wants the surface to be made visible.
+
+        This is only a request that the user intends to make your
+        window visible. The client may choose to ignore this request.
+      </description>
+    </event>
+
+    <event name="set_minimize" since="2">

[mtomasz, 2016/06/03 06:30:30]

nit: set_minimized

[reveman, 2016/06/03 11:25:29]

done

+      <description summary="surface wants to be minimized">
+        The set_minimized event is sent by the compositor when the user
+        wants the surface to be minimized.
+
+        This is only a request that the user intends to minimize the window.
+        The client may choose to ignore this request.
+      </description>
+    </event>
+
+    <event name="unset_minimized" since="2">
+      <description summary="surface wants to be restored">
+        The unset_minimized event is sent by the compositor when the user
+        wants the surface to be made visible.
+
+        This is only a request that the user intends to make your
+        window visible. The client may choose to ignore this request.
+      </description>
+    </event>
   </interface>
 
 </protocol>