[EGIT] [core/efl] master 01/06: adding wayland subsurfaces protocol file.

2013-10-10 Thread Rafael Antognolli
antognolli pushed a commit to branch master.

http://git.enlightenment.org/core/efl.git/commit/?id=f26f2da5ea55ccdb028065f1ff803cbac08c8863

commit f26f2da5ea55ccdb028065f1ff803cbac08c8863
Author: Rafael Antognolli 
Date:   Wed Aug 7 18:05:55 2013 -0300

adding wayland subsurfaces protocol file.
---
 configure.ac |   1 +
 data/ecore/ecore_wayland/protocol/subsurface.xml | 244 +++
 src/Makefile_Ecore_Wayland.am|  17 ++
 src/lib/ecore_wayland/.gitignore |   2 +
 4 files changed, 264 insertions(+)

diff --git a/configure.ac b/configure.ac
index d5a359e..44b14c1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1007,6 +1007,7 @@ AC_ARG_ENABLE([wayland],
 
 if test "${want_wayland}" = "yes"; then
EFL_PKG_CHECK_STRICT([wayland-client])
+   WAYLAND_SCANNER_RULES(['$(top_srcdir)/data/ecore/ecore_wayland/protocol'])
 fi
 
 # Fb
diff --git a/data/ecore/ecore_wayland/protocol/subsurface.xml 
b/data/ecore/ecore_wayland/protocol/subsurface.xml
new file mode 100644
index 000..9e4a658
--- /dev/null
+++ b/data/ecore/ecore_wayland/protocol/subsurface.xml
@@ -0,0 +1,244 @@
+
+
+
+  
+Copyright © 2012-2013 Collabora, Ltd.
+
+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.
+  
+
+  
+
+  The global interface exposing sub-surface compositing capabilities.
+  A wl_surface, that has sub-surfaces associated, is called the
+  parent surface. Sub-surfaces can be arbitrarily nested and create
+  a tree of sub-surfaces.
+
+  The root surface in a tree of sub-surfaces is the main
+  surface. The main surface cannot be a sub-surface, because
+  sub-surfaces must always have a parent.
+
+  A main surface with its sub-surfaces forms a (compound) window.
+  For window management purposes, this set of wl_surface objects is
+  to be considered as a single window, and it should also behave as
+  such.
+
+  The aim of sub-surfaces is to offload some of the compositing work
+  within a window from clients to the compositor. A prime example is
+  a video player with decorations and video in separate wl_surface
+  objects. This should allow the compositor to pass YUV video buffer
+  processing to dedicated overlay hardware when possible.
+
+
+
+  
+   Informs the server that the client will not be using this
+   protocol object anymore. This does not affect any other
+   objects, wl_subsurface objects included.
+  
+
+
+
+  
+
+
+
+  
+   Create a sub-surface interface for the given surface, and
+   associate it with the given parent surface. This turns a
+   plain wl_surface into a sub-surface.
+
+   The to-be sub-surface must not already have a dedicated
+   purpose, like any shell surface type, cursor image, drag icon,
+   or sub-surface. Otherwise a protocol error is raised.
+  
+
+  
+  
+  
+
+  
+
+  
+
+  An additional interface to a wl_surface object, which has been
+  made a sub-surface. A sub-surface has one parent surface. A
+  sub-surface's size and position are not limited to that of the parent.
+  Particularly, a sub-surface is not automatically clipped to its
+  parent's area.
+
+  A sub-surface becomes mapped, when a non-NULL wl_buffer is applied
+  and the parent surface is mapped. The order of which one happens
+  first is irrelevant. A sub-surface is hidden if the parent becomes
+  hidden, or if a NULL wl_buffer is applied. These rules apply
+  recursively through the tree of surfaces.
+
+  The behaviour of wl_surface.commit request on a sub-surface
+  depends on the sub-surface's mode. The possible modes are
+  synchronized and desynchronized, see methods
+  wl_subsurface.set_sync

[EGIT] [core/efl] master 01/06: adding wayland subsurfaces protocol file.

2013-10-04 Thread Rafael Antognolli
antognolli pushed a commit to branch master.

http://git.enlightenment.org/core/efl.git/commit/?id=ad27efcb397f3dc8da670180784991f876841e01

commit ad27efcb397f3dc8da670180784991f876841e01
Author: Rafael Antognolli 
Date:   Wed Aug 7 18:05:55 2013 -0300

adding wayland subsurfaces protocol file.
---
 configure.ac |   1 +
 data/ecore/ecore_wayland/protocol/subsurface.xml | 244 +++
 src/Makefile_Ecore_Wayland.am|  17 ++
 src/lib/ecore_wayland/.gitignore |   2 +
 4 files changed, 264 insertions(+)

diff --git a/configure.ac b/configure.ac
index 77972b8..21a4d94 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1007,6 +1007,7 @@ AC_ARG_ENABLE([wayland],
 
 if test "${want_wayland}" = "yes"; then
EFL_PKG_CHECK_STRICT([wayland-client])
+   WAYLAND_SCANNER_RULES(['$(top_srcdir)/data/ecore/ecore_wayland/protocol'])
 fi
 
 # Fb
diff --git a/data/ecore/ecore_wayland/protocol/subsurface.xml 
b/data/ecore/ecore_wayland/protocol/subsurface.xml
new file mode 100644
index 000..9e4a658
--- /dev/null
+++ b/data/ecore/ecore_wayland/protocol/subsurface.xml
@@ -0,0 +1,244 @@
+
+
+
+  
+Copyright © 2012-2013 Collabora, Ltd.
+
+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.
+  
+
+  
+
+  The global interface exposing sub-surface compositing capabilities.
+  A wl_surface, that has sub-surfaces associated, is called the
+  parent surface. Sub-surfaces can be arbitrarily nested and create
+  a tree of sub-surfaces.
+
+  The root surface in a tree of sub-surfaces is the main
+  surface. The main surface cannot be a sub-surface, because
+  sub-surfaces must always have a parent.
+
+  A main surface with its sub-surfaces forms a (compound) window.
+  For window management purposes, this set of wl_surface objects is
+  to be considered as a single window, and it should also behave as
+  such.
+
+  The aim of sub-surfaces is to offload some of the compositing work
+  within a window from clients to the compositor. A prime example is
+  a video player with decorations and video in separate wl_surface
+  objects. This should allow the compositor to pass YUV video buffer
+  processing to dedicated overlay hardware when possible.
+
+
+
+  
+   Informs the server that the client will not be using this
+   protocol object anymore. This does not affect any other
+   objects, wl_subsurface objects included.
+  
+
+
+
+  
+
+
+
+  
+   Create a sub-surface interface for the given surface, and
+   associate it with the given parent surface. This turns a
+   plain wl_surface into a sub-surface.
+
+   The to-be sub-surface must not already have a dedicated
+   purpose, like any shell surface type, cursor image, drag icon,
+   or sub-surface. Otherwise a protocol error is raised.
+  
+
+  
+  
+  
+
+  
+
+  
+
+  An additional interface to a wl_surface object, which has been
+  made a sub-surface. A sub-surface has one parent surface. A
+  sub-surface's size and position are not limited to that of the parent.
+  Particularly, a sub-surface is not automatically clipped to its
+  parent's area.
+
+  A sub-surface becomes mapped, when a non-NULL wl_buffer is applied
+  and the parent surface is mapped. The order of which one happens
+  first is irrelevant. A sub-surface is hidden if the parent becomes
+  hidden, or if a NULL wl_buffer is applied. These rules apply
+  recursively through the tree of surfaces.
+
+  The behaviour of wl_surface.commit request on a sub-surface
+  depends on the sub-surface's mode. The possible modes are
+  synchronized and desynchronized, see methods
+  wl_subsurface.set_sync