Add configuration_changed event and set_background_opacity request.

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="8">
+  <interface name="zwp_remote_shell_v1" version="9">
     <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 48 matching lines @@
         See the documentation of remote_surface for more details about what an
         remote_surface is and how it is used.
       </description>
       <arg name="id" type="new_id" interface="zwp_remote_surface_v1"/>
       <arg name="surface" type="object" interface="wl_surface"/>
       <arg name="container" type="uint"/>
     </request>
 
     <event name="configure">
       <description summary="suggests a re-layout of remote shell">
-        Suggests a re-layout of remote surface geometry.
+        Obsolete: Suggests a re-layout of remote surface geometry.
       </description>
       <arg name="width" type="int"/>
       <arg name="height" type="int"/>
       <arg name="work_area_inset_left" type="int"/>
       <arg name="work_area_inset_top" type="int"/>
       <arg name="work_area_inset_right" type="int"/>
       <arg name="work_area_inset_bottom" type="int"/>
     </event>
 
     <event name="activated">
@@ skipping 13 matching lines @@
       </description>
       <arg name="id" type="new_id" interface="zwp_notification_surface_v1"/>
       <arg name="surface" type="object" interface="wl_surface"/>
       <arg name="notification_id" type="string" />
     </request>
 
     <!-- Version 8 additions -->
 
     <event name="layout_mode_changed" since="8">
       <description summary="layout mode changed">
-        The shell_mode_changed event is sent by the compositor when
+        Obsolete: The shell_mode_changed event is sent by the compositor when
         the shell mode was changed.
 
         This is an event to notify that the shell mode has switched.
       </description>
       <arg name="layout_mode" type="uint"/>
     </event>
+
+    <!-- Version 9 additions -->
+
+    <event name="display_changed" since="9">

[reveman, 2016/07/28 19:52:02]

nit: we don't really have a "display" concept in any of the wayland interfaces.
if anything, "display" is the display server and basically what implements the
compositor and all other interfaces. can we keep referring to this as just the
"shell" and simply say that the shell configuration changed,
name="configuration_changed"?

Fyi, instead of deprecating the old events it would be ok to add additional
configure events and a configure_done event at the end. that's a more common way
of extending wayland interfaces. e.g. wl_output was extended this way. Either
way is fine with me though.

[oshima, 2016/07/28 22:49:48]

done.
that's good to know. For this, I think it's good chance to consolidate them
before cleaning up the interface, so I'll keep this. I'll add _done when we need
more.

+      <description summary="suggests a re-configuration of display for remote shell">

[reveman, 2016/07/28 19:52:02]

nit: s/of display for remote shell/of remote shell/

[oshima, 2016/07/28 22:49:48]

Done.

+        Suggests a re-configuration of display for remote shell.

[reveman, 2016/07/28 19:52:01]

nit: ditto

[oshima, 2016/07/28 22:49:48]

Done.

+      </description>
+      <arg name="output_origin_x" type="int"/>
+      <arg name="output_origin_y" type="int"/>

[reveman, 2016/07/28 19:52:02]

nit: origin_x/y

btw, what's this used for? do we need it?

[oshima, 2016/07/28 22:49:48]

Removed.

+      <arg name="output_width_mm" type="int"/>
+      <arg name="output_height_mm" type="int"/>

[reveman, 2016/07/28 19:52:02]

nit: width/height_mm

[oshima, 2016/07/28 22:49:48]

Done.

+      <arg name="output_subpixel_layout" type="int"/>

[reveman, 2016/07/28 19:52:02]

nit: subpixel_layout, do we really need this?

[oshima, 2016/07/28 22:49:48]

Removed. We may need it in the future for proper font rendering, but we can add
it later.

+      <arg name="output_transform" type="int"/>

[reveman, 2016/07/28 19:52:02]

nit: name="transform"

[oshima, 2016/07/28 22:49:48]

Done.

+
+      <arg name="output_mode_width_pixels" type="int"/>
+      <arg name="output_mode_height_pixels" type="int"/>

[reveman, 2016/07/28 19:52:02]

do we need these? is display_width/height below not enough?

[oshima, 2016/07/28 22:49:48]

They're both used (for physical size and logical pixel). I changed to pass dpi +
physical pixel size. I think this is better.

+      <arg name="output_mode_refresh_rate_mhz" type="int"/>

[reveman, 2016/07/28 19:52:01]

please remove if not needed

[oshima, 2016/07/28 22:49:48]

It looks to me this is used. (it's passed to hwc)

If you think we can just hard code the same value in here, let me know.

+      <arg name="display_scale_factor" type="fixed"/>

[reveman, 2016/07/28 19:52:02]

nit: name="scale_factor"

+      <arg name="display_width" type="int"/>
+      <arg name="display_height" type="int"/>

[reveman, 2016/07/28 19:52:02]

nit: name="width"/"height"

[oshima, 2016/07/28 22:49:48]

done.

+      <arg name="work_area_inset_left" type="int"/>
+      <arg name="work_area_inset_top" type="int"/>
+      <arg name="work_area_inset_right" type="int"/>
+      <arg name="work_area_inset_bottom" type="int"/>
+      <arg name="layout_mode" type="uint"/>
+    </event>
   </interface>
 
-  <interface name="zwp_remote_surface_v1" version="8">
+  <interface name="zwp_remote_surface_v1" version="9">
     <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 298 matching lines @@
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become system modal.
       </description>
     </request>
 
     <request name="unset_system_modal" since="8">
       <description summary="suggests a re-layout of remote shell input area">
         Suggests a surface should become non system modal.
       </description>
     </request>
+
+    <!-- Version 9 additions -->
+
+    <request name="set_background_opacity" since="9">

[reveman, 2016/07/28 19:52:02]

nit: set_rectangular_shadow_background_opacity as I don't think this should
apply unless a rectangular shadow is requested

qq, should this just change the opacity of the background or also the shadow
itself?

[oshima, 2016/07/28 22:49:48]

I'd just change the background for now. We can adjust when we get feedback.

+      <description summary="suggests the window's background opacity">
+        Suggests the window's background opacity.
+      </description>
+      <arg name="opacity" type="fixed"/>
+    </request>
+
   </interface>
 
   <!-- Version 6 additions -->
 
   <interface name="zwp_notification_surface_v1" version="6">
     <description summary="A notification window">
       An interface that may be implemented by a wl_surface to host
       notification contents.
     </description>
 
     <request name="destroy" type="destructor">
       <description summary="Destroy the notification_surface">
         Unmap and destroy the notification surface.
       </description>
     </request>
   </interface>
 
 </protocol>