1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
.. module:: pywayland.protocol_core
.. _protocol_core:
Protocol Core Modules
=====================
.. toctree::
:maxdepth: 2
Interface
---------
:class:`Interface` objects are only created as a subclass of Interface. The
Interface class wraps the protocol objects, and serves to initialize a set of
parameters for the Interface and provide decorators for defining
:class:`~pywayland.interface.Message` objects on the interface.
.. autoclass:: Interface
:members:
Interface Metaclass
-------------------
This metaclass initializes lists for the requests and events on an interface
and initializes a cdata struct for the class.
.. autoclass:: pywayland.protocol_core.interface.InterfaceMeta
:members:
Proxy
-----
:class:`Proxy` objects are not created directly, and users should generally not
create a proxy class on their own. Proxy classes give client side access to
the interfaces defined by the Wayland protocol. Proxies are returned from the
server after calling protocol methods which return ``new_id``'s.
.. autoclass:: Proxy
:members:
Resource
--------
.. autoclass:: Resource
:members:
Global
------
.. autoclass:: Global
:members:
Message
-------
:class:`~pywayland.interface.Message` objects are used to wrap the method calls
on the protocol objects. The Message objects are added to the
:class:`~pywayland.interface.Interface`'s as either requests (client-side
functions) or events (server-side functions).
.. autoclass:: pywayland.protocol_core.message.Message
:members:
Argument
--------
.. autoclass:: pywayland.protocol_core.argument.Argument
:members:
ArgumentType
------------
.. autoclass:: pywayland.protocol_core.argument.ArgumentType
:members:
|
