Lines Matching +full:wayland +full:- +full:protocols

1 Wayland protocols
2 -----------------
4 wayland-protocols contains Wayland protocols that add functionality not
5 available in the Wayland core protocol. Such protocols either add
7 protocol either in Wayland core, or some other protocol in
8 wayland-protocols.
10 A protocol in wayland-protocols consists of a directory containing a set
16 Protocols may be 'stable', 'unstable' or 'deprecated', and the interface
21 the maintainers. Changes to such protocols will always be backward
33 is placed within the toplevel directory containing the protocols with the
34 same state. Stable protocols are placed in the +stable/+ directory,
35 unstable protocols are placed in the +unstable/+ directory, and
36 deprecated protocols are placed in the +deprecated/+ directory.
41 Makefile.am entry to the wayland-protocols git repository with the
43 the wayland-devel@lists.freedesktop.org mailing list using
44 'git send-email' with the subject prefix 'RFC wayland-protocols' or
45 'PATCH wayland-protocols' depending on what state the protocol is in.
47 To propose changes to existing protocols, create a patch with the
57 All protocols should avoid using generic namespaces or no namespaces in
60 interface names from other protocols should also be avoided.
62 For generic protocols not limited to certain configurations (such as
66 For operating system specific protocols, the interfaces should be
72 Unstable protocols have a special naming convention in order to make it
90 For example, an unstable protocol called foo-bar with major version 2
92 be placed in the directory +unstable/foo-bar/+ consisting of one file
93 called +README+ and one called +foo-bar-unstable-v2.xml+. The XML file
114 in the regular way as done in core Wayland or in stable protocols.
140 Each release of wayland-protocols finalizes the version of the protocols