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
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
|
.. highlight:: xml
.. _gentut-typesystem:
Creating the Typesystem Description
===================================
The type system is a specification used when mapping a C++ based library onto a
corresponding Python module. The specification is a handwritten XML document
listing the types that will be available in the generated binding, alterations
to classes and function signatures to better suit the target language,
and listing the components that should be rejected for the binding.
**PyQtB** uses a typesystem format similar to the ones used **QtJambi** and
**QtScript**, thoroughly described in the page *"The Qt Jambi Type System"*. [#]_
The divergences between **PyQtB** and QtScript/QtJambi typesystems will be
highlighted whenever they appear. Things to be aware of when writing
a typesystem will be also mentioned.
Describing **libfoo** for Python Audiences
------------------------------------------
All typesystem files start with the root ``typesystem`` tag, the
``package`` attribute carries the name of the package as it will be seen
from Python.
Right after that, all the typesystem files providing information required for
the generation process are included in the same fashion as header files in C.
**foobinding/data/typesystem_test.xml**
::
<?xml version="1.0"?>
<typesystem package="foo">
<load-typesystem name="typesystem_core.xml" generate="no"/>
<object-type name="Math"/>
</typesystem>
The inclusion of the other typesystem files is achieved with the
``load-typesystem`` tag. The ``generate`` attribute must be set to ``"no"``
or else the generator will try to create more source code for the already
existing bindings included for reference.
The C++ classes derived from **QObject** intended to be exposed in the target
language are described with ``object-type`` tags.
For this example binding just specifying the name of the class does the trick,
since the generator system will automatically catch the methods with arguments
and return value of types known. These types can be described in the same
typesystem file or in the ones referenced with the ``load-typesystem`` tag.
In more complex situations method signatures can be changed or rejected with
other tags that can be checked out in the typesystem reference.
Other Common Cases and Differences
----------------------------------
What follows now is some common uses of the typesystem capabilities. All of them
can be seen in the Qt4 typesystem files. They are not used for this binding
tutorial example, so if you just want to have things working ASAP,
move along.
Templates
~~~~~~~~~
To ease the process of writing custom code for the binding, recurring pieces of
code can be turned generic with the Typesystem template mechanism.
They are declared in a way similar to this snippet:
::
<template name="only_bool*_fix">
bool ok;
%RETURN_TYPE retval = self.%FUNCTION_NAME(&ok);
</template>
And is used as in this example:
::
<inject-code class="native" position="beginning">
<insert-template name="only_bool*_fix"/>
</inject-code>
The ``typesystem_template.xml`` file from the Qt4 bindings can be used as a
good resource for examples of this. Check also the QtJambi documentation on
typesystem templates. [#]_
Non-QObject Derived Classes
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Even in a Qt4 based library it is common to find classes that doesn't
pertain to the QObject hierarchy, these must be declared as ``value-type``:
::
<value-type name="RectOrSomethingLikeThat"/>
Unused Tags
~~~~~~~~~~~
Some tags defined in the QtScript/QtJambi typesystem has no effect in **PyQtB**
typesystem, they are:
+ conversion-rule
+ argument-map
Changes to ``"inject-code"`` Tag
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
You can pass a file name to the **inject-code** tag, the file contents will
be injected in the generated code.
The ``class`` attribute value ``java`` was changed to ``target``, while
``native`` remained the same.
Global Functions
~~~~~~~~~~~~~~~~
The **BoostGenerator** supports global functions, you can also reject these
functions using the **rejection** tag like is done to reject classes, just
pass an empty string to the class attribute.
::
<rejection class="" function-name="qt_noop"/>
.. [#] http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-typesystem.html
.. [#] http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-typesystem.html#using-code-templates
|
