x11proto-xext: Changes to 'debian-unstable'
ChangeLog | 186 +
configure.ac | 2
debian/changelog | 26
debian/control | 8
debian/x11proto-xext-dev.install | 1
shmstr.h | 3
specs/.gitignore | 2
specs/Makefile.am | 20
specs/appendix.xml | 61
specs/appgroup.xml | 248 -
specs/appgrp.xml | 1018 ++++++
specs/dbe.xml | 4
specs/dpms.xml | 17
specs/evi.xml | 29
specs/geproto.xml | 4
specs/lbx.xml | 6291 +++++++++++++++++++++++++++++++++++++++
specs/multibuf.xml | 79
specs/security.xml | 4
specs/shape.xml | 34
specs/shm.xml | 23
specs/sync.xml | 239 +
specs/tog-cup.xml | 30
specs/xtest.xml | 37
syncconst.h | 6
syncproto.h | 96
syncstr.h | 2
26 files changed, 8044 insertions(+), 426 deletions(-)
New commits:
commit c6063a782fb09afd30646c5da117e87787556a47
Author: Julien Cristau <jcristau@debian.org>
Date: Thu Apr 28 13:38:20 2011 +0200
Upload to unstable.
diff --git a/debian/changelog b/debian/changelog
index 399e44a..be6f74f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+x11proto-xext (7.2.0-2) unstable; urgency=low
+
+ * Upload to unstable.
+
+ -- Julien Cristau <jcristau@debian.org> Thu, 28 Apr 2011 13:40:53 +0200
+
x11proto-xext (7.2.0-1) experimental; urgency=low
* New upstream release.
commit 8854061da37311037b49dc06cc3fd066cbfe85d3
Author: Cyril Brulebois <kibi@debian.org>
Date: Sun Feb 27 12:03:52 2011 +0100
Upload to experimental.
diff --git a/debian/changelog b/debian/changelog
index c9f343a..399e44a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,8 @@
-x11proto-xext (7.2.0-1) UNRELEASED; urgency=low
+x11proto-xext (7.2.0-1) experimental; urgency=low
* New upstream release.
- -- Cyril Brulebois <kibi@debian.org> Sun, 27 Feb 2011 12:02:53 +0100
+ -- Cyril Brulebois <kibi@debian.org> Sun, 27 Feb 2011 12:03:52 +0100
x11proto-xext (7.1.99.0-1) experimental; urgency=low
commit 99fa56964da7207c7c7ecbf67318d921be04e88c
Author: Cyril Brulebois <kibi@debian.org>
Date: Sun Feb 27 12:03:07 2011 +0100
Bump changelogs.
diff --git a/ChangeLog b/ChangeLog
index 1fcd54c..778f35a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,189 @@
+commit c593fd1000ceb83f0933361c5e7496d799233f7e
+Author: Keith Packard <keithp@keithp.com>
+Date: Sat Feb 26 23:57:48 2011 -0800
+
+ Version 7.2.0
+
+ Signed-off-by: Keith Packard <keithp@keithp.com>
+
+commit a6a542841e85344115bbb6a1ba35c4f3487995e4
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Fri Feb 25 08:53:55 2011 -0500
+
+ Docbook: change the book id to match the xml file basename
+
+ This is required for the up-coming external references support.
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit d16788e87438015d3e121ffb046bc6a4ce01da89
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Fri Feb 25 08:51:47 2011 -0500
+
+ Docbook: change the book id to match the xml file basename
+
+ This is required for the up-coming external references support.
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit 8c6cc9ddb5776a2b32d42a41d27b3df56e62c44f
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Thu Feb 24 20:44:00 2011 -0500
+
+ Docbook: change the book id to match the xml file basename
+
+ Rename appgroup.xml as it conflicts with xorg-docs/specs/Xserver/appgroup.xml
+ This is required for the up-coming external references support.
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit 9df8b77604b7ea7132d32f65f2280720b91249c1
+Author: Alan Coopersmith <alan.coopersmith@oracle.com>
+Date: Thu Dec 16 23:54:45 2010 -0800
+
+ specs: Fix section titles/nesting
+
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 6aa72ae8e629e065f09a6b6c05504363806d76a3
+Author: Paulo Zanoni <pzanoni@mandriva.com>
+Date: Tue Dec 14 16:23:56 2010 -0200
+
+ Use the same docbookx.dtd version (4.3) for all docs
+
+ This way we don't need to require 4.1.2 and 4.5
+ The geproto xml was inconsistent, by the way.
+
+ Signed-off-by: Paulo Zanoni <pzanoni@mandriva.com>
+ Reviewed-by: Matt Dew <matt@osource.org>
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 77c2b72d8df53e918b0fbff5425af82ac7f5693a
+Author: Alan Coopersmith <alan.coopersmith@oracle.com>
+Date: Thu Dec 9 17:43:29 2010 -0800
+
+ specs/sync.xml: Fix minor typos in document title section
+
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit b4e8a6fb63715442b4927d18d9cdd7ee78e50d00
+Author: James Jones <jajones@nvidia.com>
+Date: Mon Nov 29 09:35:50 2010 -0800
+
+ Bump version to 7.1.99.0
+
+ Use version 7.1.99.0 to mark the inclusion of
+ Fence Sync protocol support.
+
+ Signed-off-by: James Jones <jajones@nvidia.com>
+ Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
+ Acked-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 6e696a0a4c9a115c7f080c2bdee3d8afc16b134f
+Author: James Jones <jajones@nvidia.com>
+Date: Wed Feb 24 15:57:29 2010 -0800
+
+ Add protocol for XSyncAwaitFence()
+
+ Add the fence sync object equivalent of
+ XSyncAwait()
+
+ Signed-off-by: James Jones <jajones@nvidia.com>
+ Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
+ Acked-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 220b824f20dc3dd0fd6eae6e2896fb63aefbf11a
+Author: James Jones <jajones@nvidia.com>
+Date: Mon Feb 22 17:01:16 2010 -0800
+
+ Add XSyncQueryFence()
+
+ Allows callers to query whether a given fence sync
+ object is currently triggered or not.
+
+ Signed-off-by: James Jones <jajones@nvidia.com>
+ Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
+ Acked-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit d079ee210726d2407fa9c8cf99555daf2d96023a
+Author: James Jones <jajones@nvidia.com>
+Date: Fri Feb 12 16:38:08 2010 -0800
+
+ Initial Fence Sync support
+
+ Defines the protocol for creation and basic
+ management of binary state sync objects.
+ The following operations are defined:
+
+ -Creation
+ -Destruction
+ -Trigger
+ -Reset
+
+ Signed-off-by: James Jones <jajones@nvidia.com>
+ Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
+ Acked-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 9ba2065b63ea0e61a17b8221ad454c02a1755373
+Author: James Jones <jajones@nvidia.com>
+Date: Wed Aug 11 15:03:59 2010 -0700
+
+ Document changes in XSync version 3.1
+
+ Signed-off-by: James Jones <jajones@nvidia.com>
+ Reviewed-by: Pierre-Loup Griffais <pgriffais@nvidia.com>
+ Reviewed-by: Aaron Plattner <aplattner@nvidia.com>
+ Reviewed-by: Robert Morell <rmorell@nvidia.com>
+ Acked-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit fd8a26edefc53b370c554a60c75ff32fc60b99c8
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Tue Nov 30 09:05:07 2010 -0500
+
+ specs: add low bandwith spec from xorg-docs
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit 3102665110846af5c87792b221e1ef6a9dc1a0e2
+Author: Matt Dew <matt@osource.org>
+Date: Mon Nov 29 16:29:44 2010 -0500
+
+ specs: add appgroup specs in DocBook/XML format
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit f6ee80371c4bf9ebd99418a4328a351186ac0847
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Tue Nov 9 15:19:09 2010 -0500
+
+ config: HTML file generation: use the installed copy of xorg.css
+
+ Currenlty the xorg.css file is copied in each location
+ where a DocBook/XML file resides. This produces about
+ 70 copies in the $(docdir) install tree.
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
+commit 6fbb74bfe75adc7cfd6d4bc642d7d4179a3db17d
+Author: Jesse Adkins <jesserayadkins@gmail.com>
+Date: Tue Sep 28 13:30:04 2010 -0700
+
+ Purge cvs tags.
+
+ Signed-off-by: Jesse Adkins <jesserayadkins@gmail.com>
+ Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
+
+commit 5508eec058c0ffbb180f3d98f8a02083d6de428b
+Author: Gaetan Nadon <memsize@videotron.ca>
+Date: Thu Sep 9 16:41:21 2010 -0400
+
+ Remove the appgroup specs which is the one for the server side.
+
+ The spec for the protocol side is still in Framemaker format.
+ See doc/xorg-docs/specs/Xext/AppGroup.mif
+
+ Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
+
commit 5daf9cff36df7423f6247fc8174b8e6c9443ed07
Author: Adam Jackson <ajax@redhat.com>
Date: Tue Aug 10 10:24:51 2010 -0400
diff --git a/debian/changelog b/debian/changelog
index b109a4e..c9f343a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+x11proto-xext (7.2.0-1) UNRELEASED; urgency=low
+
+ * New upstream release.
+
+ -- Cyril Brulebois <kibi@debian.org> Sun, 27 Feb 2011 12:02:53 +0100
+
x11proto-xext (7.1.99.0-1) experimental; urgency=low
[ Christopher James Halse Rogers ]
commit c593fd1000ceb83f0933361c5e7496d799233f7e
Author: Keith Packard <keithp@keithp.com>
Date: Sat Feb 26 23:57:48 2011 -0800
Version 7.2.0
Signed-off-by: Keith Packard <keithp@keithp.com>
diff --git a/configure.ac b/configure.ac
index 41269a3..dd30292 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1,5 +1,5 @@
AC_PREREQ([2.60])
-AC_INIT([XExtProto], [7.1.99.0], [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg])
+AC_INIT([XExtProto], [7.2.0], [https://bugs.freedesktop.org/enter_bug.cgi?product=xorg])
AM_INIT_AUTOMAKE([foreign dist-bzip2])
AM_MAINTAINER_MODE
commit a6a542841e85344115bbb6a1ba35c4f3487995e4
Author: Gaetan Nadon <memsize@videotron.ca>
Date: Fri Feb 25 08:53:55 2011 -0500
Docbook: change the book id to match the xml file basename
This is required for the up-coming external references support.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
diff --git a/specs/shm.xml b/specs/shm.xml
index 19d9309..127412c 100644
--- a/specs/shm.xml
+++ b/specs/shm.xml
@@ -4,7 +4,7 @@
<!-- lifted from troff+ms+XMan by doclifter -->
-<book id="mit-shm">
+<book id="shm">
<bookinfo>
<title>MIT-SHM(The MIT Shared Memory Extension)</title>
commit d16788e87438015d3e121ffb046bc6a4ce01da89
Author: Gaetan Nadon <memsize@videotron.ca>
Date: Fri Feb 25 08:51:47 2011 -0500
Docbook: change the book id to match the xml file basename
This is required for the up-coming external references support.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
diff --git a/specs/multibuf.xml b/specs/multibuf.xml
index eb01829..1c8e363 100644
--- a/specs/multibuf.xml
+++ b/specs/multibuf.xml
@@ -4,7 +4,7 @@
<!-- lifted from troff+ms+XMan by doclifter -->
-<book id="buffer">
+<book id="multibuf">
<bookinfo>
<title>Extending X for Double-Buffering, Multi-Buffering, and Stereo</title>
commit 8c6cc9ddb5776a2b32d42a41d27b3df56e62c44f
Author: Gaetan Nadon <memsize@videotron.ca>
Date: Thu Feb 24 20:44:00 2011 -0500
Docbook: change the book id to match the xml file basename
Rename appgroup.xml as it conflicts with xorg-docs/specs/Xserver/appgroup.xml
This is required for the up-coming external references support.
Signed-off-by: Gaetan Nadon <memsize@videotron.ca>
diff --git a/specs/Makefile.am b/specs/Makefile.am
index 3792353..e689dff 100644
--- a/specs/Makefile.am
+++ b/specs/Makefile.am
@@ -23,7 +23,7 @@
if ENABLE_SPECS
doc_sources = \
- appgroup.xml \
+ appgrp.xml \
dbe.xml \
dpms.xml \
evi.xml \
diff --git a/specs/appgroup.xml b/specs/appgroup.xml
deleted file mode 100644
index f506d86..0000000
--- a/specs/appgroup.xml
+++ /dev/null
@@ -1,1018 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" ?>
-<!DOCTYPE article
- PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
- "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd";>
-
-<article id="appgroup">
-
-<articleinfo>
- <title>Application Group Extension to the X Protocol</title>
- <subtitle>X Consortium Standard</subtitle>
- <authorgroup>
- <author>
- <firstname>Kaleb</firstname>
- <othername>S.</othername>
- <surname>KEITHLEY</surname>
- <affiliation><orgname>X Consortium, Inc</orgname></affiliation>
- <email>kaleb@x.org</email>
- </author>
- </authorgroup>
- <releaseinfo>X Version 11, Release 6.4</releaseinfo>
- <date>27 September 1996</date>
-
-<legalnotice>
-<para>
-Copyright © 1996 X Consortium, Inc. All Rights Reserved.
-</para>
-
-<para>
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE X CONSORTIUM BE LIABLE FOR ANY CLAIM,
-DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
-OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
-OR THE USE OF OR OTHER DEALINGS IN THE SOFTWARE.
-</para>
-<para>
-Except as contained in this notice, the name of the X Consortium shall not be used in advertising
-or otherwise to promote the sale, use or other dealings in this Software without prior written
-authorization from the X Consortium.
-</para>
-</legalnotice>
-
-<abstract>
-<para>
-The Application Group Extension to the X protocol is intended to provide a framework to allow
-more than one program to manage X applications on the desktop. The initial use of this extension
-will be to insert or embed the windows of X programs into the windows of another program, such
-as a web browser. This extension is not intended to address larger embedding issues that, for
-example, OpenDoc does, such as shared menu bars, etc.
-</para>
-</abstract>
-</articleinfo>
-
-<sect1 id='purpose_and_goals'>
-<title>Purpose and Goals</title>
-
-<para>
-The Application Group Extension to the X protocol is intended to provide
-a framework to allow more than one program to manage X applications on
-the desktop. The initial use of this extension will be to insert or embed
-the windows of X programs into the windows of another program, such as a
-web browser. This extension is not intended to address larger embedding
-issues that, for example, OpenDoc does, such as shared menu bars, etc.
-Using X programs on the World Wide Web allows for greater control of the
-presentation and takes advantage of the existing body of X programs rather
-than re-implement them in another language. In addition it allows the
-embedding of non-X programs into web browsers by using third party products
-like Wabi, MAE, and WinCenter.
-<footnote><para>
-Wabi is a trademark of Sun Microsystems, Inc. MAE is a trademark of Apple
-Computer, Inc. WinCenter is a trademark of Network Computing Devices, Inc.
-</para></footnote>
-</para>
-
-</sect1>
-
-<sect1 id='overview_of_the_protocol'>
-<title>Overview of the protocol.</title>
-
-<para>
-This extension introduces the concept of an Application Group. An Application Group is a set of one or more applications that are primarily managed by a special application known as the Application Group Leader, which, for example, might be a web browser. The primary purpose of Application Groups is to provide a means of sharing the Substructure-Redirect attribute of the root window between the window manager and one or more Application Group Leaders.
-</para>
-
-<para>
-To join an Application Group an application must present the proper authorization during the connection setup. Authorizations are generated by the X server at the request of an Application Group Leader, and are then stored for the application to use to establish its connection to the X server. To generate an authorization the Application Group Leader sends a request to the server naming the Application Group to which the authorization will be bound, and any applications that connect using that authorization will automatically become part of the associated Application Group. The protocol to generate an authorization is defined in the Security Extension specification.
-</para>
-
-<para>
-As a member of an Application Group, when an application creates and maps a window as a child of the root window, the MapRequest and ConfigureRequest events are delivered to the Application Group Leader instead of the window manager. The Application Group Leader may then reparent the window into its own window hierarchy; or reissue the map request, in which case the window comes under the control of the window manager.
-</para>
-
-</sect1>
-<sect1 id='requests'>
-<title>Requests</title>
-
-
-<para><emphasis role='bold'>AppGroupQueryVersion</emphasis></para>
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>client_major_version: CARD16</entry>
- </row>
- <row>
- <entry>client_minor_version: CARD16</entry>
- </row>
- <row>
- <entry>=></entry>
- </row>
- <row>
- <entry>server_major_version: CARD16</entry>
- </row>
- <row>
- <entry>server_minor_version: CARD16</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-If supplied, the client_major_version and client_minor_version indicate what version of the protocol the application wants the server to implement. The server version numbers returned indicate the version of the protocol the X server actually supports. This may not match the versions requested by the application. An implementation may (but need not) support more than one version simultaneously. The server_major_version and server_minor_version numbers are a mechanism to support any future revisions of the Application Group extension protocol which may be necessary. In general, the major version would increment for incompatible changes, and the minor version would increment for small, upward-compatible changes. X servers that support the protocol defined in this document will return a server_major_version of 1 and a server_minor_version of 0.
-</para>
-
-
-<para><emphasis role='bold'>AppGroupCreate</emphasis></para>
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>app_group: APPGROUP</entry>
- </row>
- <row>
- <entry>value_mask: BITMASK</entry>
- </row>
- <row>
- <entry>value_list: LISTofVALUE</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-This request creates an Application Group using app_group as the Application Group ID.
-</para>
-
-
-<para>
-
-</para>
-
-
-<para>
-The value_mask and value_list specify attributes of the Application Group that are to be explicitly initialized. The attributes, their types, and the default values are:
-</para>
-
-<informaltable frame="all">
-<tgroup cols='3'>
-<colspec colsep='0'/>
-<colspec colsep='0'/>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>Attribute</entry>
- <entry>Type</entry>
- <entry>Default</entry>
- </row>
- <row>
- <entry>app_group_leader</entry>
- <entry>Bool</entry>
- <entry>True</entry>
- </row>
- <row>
- <entry>single_screen</entry>
- <entry>Bool</entry>
- <entry>True</entry>
- </row>
- <row>
- <entry>default_root</entry>
- <entry>Window</entry>
- <entry>None</entry>
- </row>
- <row>
- <entry>root_visual</entry>
- <entry>VisualID</entry>
- <entry>None</entry>
- </row>
- <row>
- <entry>default_colormap</entry>
- <entry>Colormap</entry>
- <entry>None</entry>
- </row>
- <row>
- <entry>black_pixel</entry>
- <entry>Pixel</entry>
- <entry>0</entry>
- </row>
- <row>
- <entry>white_pixel</entry>
- <entry>Pixel</entry>
- <entry>0</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-If the single_screen attribute is True then the number of video screens returned to a program in the Application Group in the connection setup message is one, irrespective of how many video screens the server actually has. If a server supports both video and print screens, then all print screens will always be returned. If single_screen is specified as True then the connection setup message will contain only the information about the video screen which has default_root as its root window, plus any print screens.
-</para>
-
-<note><para>
-The intent is to allow an embedding manager to ensure that it will be able to reparent any top-level windows that Application Group members create. By hiding the fact that there are other screens it can be reasonably assured that applications will only create top-level windows on the same screen that it itself appears on. An embedding manager should take care not to supply an invalid display, e.g. :0.1, to a program that will be in an Application Group where the single_screen attribute is True.
-</para></note>
-
-<para>
-If single_screen is set to True default_root specifies which screen will be returned as screen zero in the connection setup message for applications in the Application Group. If set to None, then the real screen zero is used, otherwise the screen which has default_root as its root window will be used.
-</para>
-
-
-<para>
-If single_screen is set to True the root_visual and default_colormap attributes may be used to over-ride the default values that are returned in the connection setup information returned to new programs in the Application Group. If None is specified for root_visual or default_colormap then the normal default values for the screen (possibly spedified by default_root) are used, otherwise the specified values are used. If root_visual and/or default_colormap are specified they must be valid, i.e. root_visual must be a visual type available on the screen, and the colormap, if specified, must be a valid colormap for the visual that is used.
-</para>
-
-<para>
-IF single_screen is set to True and default_colormap is not specified as None, the black_pixel and white_pixel attributes must be specified, and they will over-ride the default values that are returned in the connection setup returned to new programs in the Application Group. If default_colormap is specified as None and black_pixel and/or white_pixel are specified, they will be ignored.
-</para>
-
-<para>
-The app_group_leader attribute is used to identify the Application Group Leader program for the app_group. By specifying True the server will identify the program making the request as the Application Group Leader for the application group. The Application Group Leader receives MapRequest and ConfigureRequest events from the server when an attempt is made to map or configure top-level windows of a program in an Application Group, instead of being sent to a window manager that has selected SubstructureRedirect events on the root window. The parent window field in these events will contain the Application Group ID.
-</para>
-
-<para><emphasis role='bold'>AppGroupDestroy</emphasis></para>
-
-<para>app_group: APPGROUP</para>
-
-
-<para>
-This request destroys the app_group. If the app_group_leader attribute for the app_group is True, then any applications in the Application Group that are still connected will be killed as if a KillClient request had been received for that application.
-</para>
-
-<note><para>
-If the application that created a non-embedded Application Group exits, and therefore any Authorizations to be cancelled, and any applications that attempt to open new connections to the X server using one of those Authorizations will be unable to do so.
-</para></note>
-
-<para><emphasis role='bold'>AppGroupGetAttr</emphasis></para>
-
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>>app_group: APPGROUP</entry>
- </row>
- <row>
- <entry>=></entry>
- </row>
- <row>
- <entry>LISTofVALUE</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-This request returns the application group attributes for app_group.
-</para>
-
-<para><emphasis role='bold'>AppGroupQuery</emphasis></para>
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>resource: XID</entry>
- </row>
- <row>
- <entry>=></entry>
- </row>
- <row>
- <entry>app_group: APPGROUP</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-This request returns the Application Group ID of the application that created resource or None if that application is not associated with any Application Group. The resource value may be the resource base of the application.
-</para>
-
-<para><emphasis role='bold'>AppGroupCreateAssociation</emphasis></para>
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>window: WINDOW</entry>
- </row>
- <row>
- <entry>window_type: CARD32</entry>
- </row>
- <row>
- <entry>system_window: LISTofCARD8</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-This request associates window with system_window. The window_type indicates the native window system of the application making the request. For non-X window_types both the embedding manager and the server must be executing on the same host. When system_window is Microsoft Windows or OS/2 Presentation Manager, the system_window is an HWND; when the native window system is Macintosh, the system_window is a WindowPtr and a Rect. The window may be used for any X request that takes a Window.
-</para>
-
-<para><emphasis role='bold'>AppGroupDestroyAssociation</emphasis></para>
-
-<informaltable>
-<tgroup cols='1'>
-<colspec colsep='0'/>
-<tbody>
- <row>
- <entry>window: WINDOW</entry>
- </row>
-</tbody>
-</tgroup>
-</informaltable>
-
-<para>
-This request destroys the association created with AppGroupCreateAssociation. The window is destroyed. The system_window that was specified in the AppGroupCreateAssociation request is not affected.
-</para>
-
-</sect1>
-
-<sect1 id='changes_to_existing_requests'>
-<title>Changes to Existing Requests</title>
-
-<sect2 id='mapwindow'>
-<title>MapWindow</title>
-
-<para>
-If the override-redirect attribute of the window is False and if the window is a child of a root window and if the window belongs to an application that is in an application group and if some other application is the application group leader for that group, then a MapRequest event is generated and the window remains unmapped. Otherwise, the core protocol semantics apply.
-</para>
-
-</sect2>
-<sect2 id='configurewindow'>
-<title>ConfigureWindow</title>
-
-<para>
-If the override-redirect attribute of the window is False and if the window is a child of a root window and if the window belongs to an application that is in an application group and if some other application is the application group leader for that group, then a ConfigureRequest event is generated and the window remains unchanged. Otherwise, the core protocol semantics apply.
-</para>
-
-</sect2>
-<sect2 id='createwindow'>
-<title>CreateWindow</title>
-
-<para>
-When a program in an Application Group creates a window that is a child of a root window and specifies CopyFromParent for the Visual, if the single_screen attribute is True and the root_visual attribute is set to something other than None, then the window will be created using the Application Group’s root_visual, otherwise core protocol semantics apply.
-</para>
-
-<para>
-When a program in an Application Group creates a window that is a child of a root window and specifies CopyFromParent for the Colormap, if the single_screen attribute is True, the default_colormap attribute is set to something other than None, and the window’s Visual is the same as the Application Group’s root_visual attribute, then the window will be created using the Application Group’s default_colormap, otherwise core protocol semantics apply.
-</para>
-
-</sect2>
-
-<sect2 id='changewindowattributes'>
-<title>ChangeWindowAttributes</title>
-
-<para>
-When a program in an Application Group changes the attributes of a window that is a child of a root window and specifies CopyFromParent for the Colormap, if the single_screen attribute is True, the default_colormap attribute is set to something other than None, and the window’s Visual is the same as the Application Group’s root_visual attribute, then the window will be created using the Application Group’s default_colormap, otherwise core protocol semantics apply.
-</para>
-
-</sect2>
-
-</sect1>
-
-<sect1 id='changes_to_existing_events'>
-<title>Changes to Existing Events</title>
-
-<para>
-When the top-level window of an application that is a member of an Application Group is the target of a MapWindow or ConfigureWindow request, if there is an Application Group Leader then MapRequest and ConfigureRequest events are automatically delivered to it, otherwise the core protocol semantics apply, i.e. they are delivered to the client, if any, that has SubstructureRedirect set in its root-window event mask, e.g. the window manager.
-</para>
-
-<note><para>
-The Application Group Leader must not select SubstructuRedirect events on a root window as doing so would result in a core protocol error; only one client is permitted to do so, and that is usually the window manager.
-</para></note>
-
-
-<sect2 id='maprequest'>
-<title>MapRequest</title>
-
-<para>
-When a MapWindow request is received for a window whose override-redirect attribut is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
-</para>
-
-</sect2>
-<sect2 id='configurerequest'>
-<title>ConfigureRequest</title>
-
-<para>
-When a ConfigureWindow request is received for a window whose override-redirect attribut is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1 id='errors'>
-<title>Errors</title>
-
-<sect2 id='appgroupqueryversion'>
-<title>AppGroupQueryVersion</title>
-
-<para>
-There are no errors for AppGroupQueryVersion.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupcreate'>
-<title>AppGroupCreate</title>
-
-<para>
-A Window error is returned if default_root is specified and is not a valid root window..
-</para>
-
-<para>
-A Color error is returned default_colormap is specified but default_colormap is not a valid colormap for the screen of default_root.
-</para>
-
-<para>
-A Match error is returned if root_visual and default_colormap are both specified, but
-</para>
-
-<para>
-default_colormap’s visual is not root_visual.
-</para>
-
-<para>
-A Match error is returned if root_visual does not exist for the screen of the default_root.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupdestroy'>
-<title>AppGroupDestroy</title>
-
-<para>
-An AppGroup error is returned if app_group is not a valid Application Group.
-</para>
-
-<para>
-An Access error is returned if an untrusted application attempts to destroy an Application Group created by a trusted application.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupgetattr'>
-<title>AppGroupGetAttr</title>
-
-<para>
-An AppGroup error is returned if app_group is not a valid Application Group.
-</para>
-
-<para>
-An Access error is returned if an untrusted application attempts to get the attributes of an Application Group created by a trusted application.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupquery'>
-<title>AppGroupQuery</title>
-
-<para>
-An Access error is returned if an untrusted application attempts to query the Application Group of a trusted application.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupcreateassociation'>
-<title>AppGroupCreateAssociation</title>
-
-<para>
-A Match error is returned if the X server does not support the window_type.
-</para>
-
-<para>
-An Access error may be returned if the X server only supports the window_type on the local host and the program making the request is on a non-local host.
-</para>
-
-<para>
-A Window error may be returned for system-specific errors related to system_window, e.g. system_window does not represent a valid native window.
-</para>
-
-</sect2>
-
-<sect2 id='appgroupdestroyassociation'>
-<title>AppGroupDestroyAssociation</title>
-
-<para>
-A Window error is returned if window was not specified in a previous AppGroupCreateAssociation request.
-</para>
-
-</sect2>
-</sect1>
-
-<sect1 id='encoding'>
-<title>Encoding</title>
-
-<para>
-Please refer to the X11 Protocol encoding document as this document uses conventions established there.
-</para>
-
-
-<para>
-The name of this extension is XC-APPGROUP
-</para>
-
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AppGroupQueryVersion</emphasis>
- 1 CARD8 opcode
- 1 0 XC-APPGROUP opcode
- 2 3 length
- 2 CARD16 client_major_version
- 2 CARD16 client_minor_version
-=>
- 1 1 Reply
- 1 unused
- 2 CARD16 sequence_number
- 4 0 length
- 2 CARD16 server_major_version
- 2 CARD16 server_minor_version
- 20 unused
-</literallayout>
-
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AppGroupCreate</emphasis>
- 1 CARD8 opcode
- 1 1 XC-APPGROUP opcode
- 2 8+n length
- 4 XID app_group
- 4 BITMASK attrib_mask
- #x00000001 app_group_leader
- #x00000002 single_screen
- #0x0000004 default_root
- #x00000008 root_visual
- #x00000010 default_colormap
- #x00000020 black_pixel
- #x00000040 white_pixel
- n LISTofVALUE value-list
-VALUEs
- 4 BOOL app_group_leader
- 4 BOOL single_screen
- 4 WINDOW default_root
- 4 VISUALID root_visual
- 4 COLORMAP default_colormap
- 4 CARD32 black_pixel
- 4 CARD32 white_pixel
-</literallayout>
-
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AppGroupDestroy</emphasis>
- 1 CARD8 opcode
- 1 2 XC-APPGROUP opcode
- 2 2 length
- 4 XID app_group
-</literallayout>
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AAppGroupGetAttr</emphasis>
- 1 CARD8 opcode
- 1 4 XC-APPGROUP opcode
- 2 2 length
- 4 XID app_group
-=>
- 1 1 Reply
- 1 unused
- 2 CARD16 sequence_number
- 4 0 length
- 4 WINDOW default_root
- 4 VISUALID root_visual
- 4 COLORMAP default_colormap
- 4 CARD32 black_pixel
- 4 CARD32 whte_pixel
- 1 BOOL single_screen
- 1 BOOL app_group_leader
- 2 unused
-</literallayout>
-
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AppGroupQuery</emphasis>
- 1 CARD8 opcode
- 1 5 XC-APPGROUP opcode
- 2 2 length
- 4 XID resource
-=>
- 1 1 Reply
- 1 unused
- 2 CARD16 sequence_number
- 4 0 length
- 4 XID app_group
- 20 unused
-</literallayout>
-
-<literallayout class='monospaced'>
-<emphasis role='bold'>AppGroupCreateAssoc</emphasis>
- 1 CARD8 opcode
- 1 6 XC-APPGROUP opcode
Reply to: