summaryrefslogtreecommitdiffstats
path: root/meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch
diff options
context:
space:
mode:
Diffstat (limited to 'meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch')
-rw-r--r--meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch239
1 files changed, 0 insertions, 239 deletions
diff --git a/meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch b/meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch
deleted file mode 100644
index 8087743..0000000
--- a/meta-ivi/recipes-graphics/wayland/weston-1.6.0/0002-protocol-add-interface-ivi_application-extension.patch
+++ /dev/null
@@ -1,239 +0,0 @@
-From 983fb7e0cf9f91a60e1cb07f73fb5e70b4cc9362 Mon Sep 17 00:00:00 2001
-From: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-Date: Mon, 17 Mar 2014 14:15:14 +0900
-Subject: [PATCH 02/15] protocol: add interface ivi_application extension
-
-- introduces ivi-application.xml
-
-<<<<<<new
-Many applications in an IVI-system are special single-purpose
-applications that have a very specific role in the whole IVI UI, for
-example a rear camera, speedometer, map, etc. The IVI system vendor
-specifies what these are and how they integrate into the UI. They also
-vary between particular IVI systems. This is why we use (system-)global,
-unique, pre-determined ID numbers to tell what wl_surface is which
-application, instead of writing specific shell requests for each one.
-Using ID numbers allows vendors to easily invent new component
-applications without extending or breaking the actual Wayland protocol.
-In IVI-systems, the ID is a standard concept already used in several
-APIs, with a vendor-specified global definition of ID assignments.`
->>>>>>old
-ivi_applicatoin extension creates ivi_surface objects tied
-to a given wl_surface with a given id. The given id can be used in a
-shell to identify which application is assigned to a wl_surface and
-layout the surface wherever the shell wants. ivi_surface objects can
-be used to receive status of wl_surface in the scenegraph of the
-compositor.
-------
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
-ivi-application.xml: Add configure event in ivi_surface
-
-Configure event is notified to suggest resize of its surface
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: update description of destroy.
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application, remove Visibility event.
-
-Visibility event can be replaced with frame event. We need to clarify
-IVI use case to enalbe again, why explicit event is required.
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application.xml, update decription of ivi-application
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application add errors and modify description of
-surface_create
-
-Indeed, the new role stuff. For more information, see:
-http://cgit.freedesktop.org/wayland/wayland/commit/?id=ff2df60b1a07c3d26d170e65cd5440d15cdf3088
-and examples:
-http://cgit.freedesktop.org/wayland/wayland/commit/?id=a27501f40e9a369ed5d4c655674130e76214281f
-http://cgit.freedesktop.org/wayland/wayland/commit/?id=7a0b86ab22e026387b6d529a46d8eb416caa26fa
-http://cgit.freedesktop.org/wayland/weston/commit/?id=50b67479033709d8ab32744c7b8346b130ace9e0
-
-So, you also need to add a protocol error code for role errors like in
-the examples.
-
-What happens if the ID is already used by an existing surface? Does that
-depend on the particular ID perhaps?
-
-Would you want to tie ID as a role? Note, that if you do, there cannot
-be two surfaces with the same ID.
-
-I think we talked about this before, but the specifications are still
-missing here.
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application.xml. alignment of indents
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: fix xml format error
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-Makefile.am: add ivi-application to toolkit
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application.xml, add clear decription of surface_create
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
-
------------------------------------------------------------------
-protocol: ivi-application.xml, update license file test
-
-Signed-off-by: Nobuhiko Tanibata <NOBUHIKO_TANIBATA@xddp.denso.co.jp>
----
- Makefile.am | 7 ++-
- protocol/ivi-application.xml | 96 ++++++++++++++++++++++++++++++++++++++++++
- 2 files changed, 101 insertions(+), 2 deletions(-)
- create mode 100644 protocol/ivi-application.xml
-
-diff --git a/Makefile.am b/Makefile.am
-index b2d6893..2330933 100644
---- a/Makefile.am
-+++ b/Makefile.am
-@@ -446,7 +446,9 @@ nodist_libtoytoolkit_la_SOURCES = \
- protocol/workspaces-protocol.c \
- protocol/workspaces-client-protocol.h \
- protocol/xdg-shell-protocol.c \
-- protocol/xdg-shell-client-protocol.h
-+ protocol/xdg-shell-client-protocol.h \
-+ protocol/ivi-application-protocol.c \
-+ protocol/ivi-application-client-protocol.h
-
- BUILT_SOURCES += $(nodist_libtoytoolkit_la_SOURCES)
-
-@@ -987,7 +989,8 @@ EXTRA_DIST += \
- protocol/wayland-test.xml \
- protocol/xdg-shell.xml \
- protocol/fullscreen-shell.xml \
-- protocol/scaler.xml
-+ protocol/scaler.xml \
-+ protocol/ivi-application.xml
-
- man_MANS = weston.1 weston.ini.5
-
-diff --git a/protocol/ivi-application.xml b/protocol/ivi-application.xml
-new file mode 100644
-index 0000000..6bb90a7
---- /dev/null
-+++ b/protocol/ivi-application.xml
-@@ -0,0 +1,96 @@
-+<?xml version="1.0" encoding="UTF-8"?>
-+<protocol name="ivi_application">
-+
-+ <copyright>
-+ Copyright (C) 2013 DENSO CORPORATION
-+ Copyright (c) 2013 BMW Car IT GmbH
-+
-+ 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.
-+ </copyright>
-+
-+ <interface name="ivi_surface" version="1">
-+ <description summary="application interface to surface in ivi compositor"/>
-+
-+ <request name="destroy" type="destructor">
-+ <description summary="destroy ivi_surface">
-+ This removes link from ivi_id to wl_surface and destroys ivi_surface.
-+ The ID, ivi_id, is free and can be used for surface_create again.
-+ </description>
-+ </request>
-+
-+ <event name="configure">
-+ <description summary="suggest resize">
-+ The configure event asks the client to resize its surface.
-+
-+ The size is a hint, in the sense that the client is free to
-+ ignore it if it doesn't resize, pick a smaller size (to
-+ satisfy aspect ratio or resize in steps of NxM pixels).
-+
-+ The client is free to dismiss all but the last configure
-+ event it received.
-+
-+ The width and height arguments specify the size of the window
-+ in surface local coordinates.
-+ </description>
-+ <arg name="width" type="int"/>
-+ <arg name="height" type="int"/>
-+ </event>
-+ </interface>
-+
-+ <interface name="ivi_application" version="1">
-+ <description summary="create ivi-style surfaces">
-+ This interface is exposed as a global singleton.
-+ This interface is implemented by servers that provide IVI-style user interfaces.
-+ It allows clients to associate a ivi_surface with wl_surface.
-+ </description>
-+
-+ <enum name="error">
-+ <entry name="role" value="0" summary="given wl_surface has another role"/>
-+ <entry name="ivi_id" value="1" summary="given ivi_id is assigned to another wl_surface"/>
-+ </enum>
-+
-+ <request name="surface_create">
-+ <description summary="create ivi_surface with numeric ID in ivi compositor">
-+ This request gives the wl_surface the role of an IVI Surface. Creating more than
-+ one ivi_surface for a wl_surface is not allowed. Note, that this still allows the
-+ following example:
-+
-+ 1. create a wl_surface
-+ 2. create ivi_surface for the wl_surface
-+ 3. destroy the ivi_surface
-+ 4. create ivi_surface for the wl_surface (with the same or another ivi_id as before)
-+
-+ surface_create will create a interface:ivi_surface with numeric ID; ivi_id in
-+ ivi compositor. These ivi_ids are defined as unique in the system to identify
-+ it inside of ivi compositor. The ivi compositor implements business logic how to
-+ set properties of the surface with ivi_id according to status of the system.
-+ E.g. a unique ID for Car Navigation application is used for implementing special
-+ logic of the application about where it shall be located.
-+ The server regards following cases as protocol errors and disconnects the client.
-+ - wl_surface already has an nother role.
-+ - ivi_id is already assigned to an another wl_surface
-+ </description>
-+ <arg name="ivi_id" type="uint"/>
-+ <arg name="surface" type="object" interface="wl_surface"/>
-+ <arg name="id" type="new_id" interface="ivi_surface"/>
-+ </request>
-+
-+ </interface>
-+
-+</protocol>
---
-1.7.9.5
-