--- title: Advanced Client-Side Topics order: 10 layout: page --- [[gwt.advanced]] = Advanced Client-Side Topics In the following, we mention some topics that you may encounter when integrating widgets. [[gwt.advanced.phases]] == Client-Side Processing Phases Vaadin's client-side engine reacts to changes from the server in a number of phases, the order of which can be relevant for a connector. The processing occurs in the [methodname]#handleUIDLMessage()# method in [classname]#ApplicationConnection#, but the logic can be quite overwhelming, so we describe the phases in the following summary. . Any dependencies defined by using [classname]#@JavaScript#, [classname]#@StyleSheet# or [classname]#@HtmlImport# on the server-side class are loaded. Processing does not continue until the browser confirms that they have been loaded. . New connectors are instantiated and [methodname]#init()# is run for each [interfacename]#Connector#. . State objects are updated, but no state change event is fired yet. . The connector hierarchy is updated, but no hierarchy change event is fired yet. [methodname]#setParent()# and [methodname]#setChildren()# are run in this phase. . Hierarchy change events are fired. This means that all state objects and the entire hierarchy are already up to date when this happens. The DOM hierarchy should in theory be up to date after all hierarchy events have been handled, although there are some built-in components that for various reasons do not always live up to this promise. . Captions are updated, causing [methodname]#updateCaption()# to be invoked on layouts as needed. . [classname]#@DelegateToWidget# is handled for all changed state objects using the annotation. . State change events are fired for all changed state objects. . [methodname]#updateFromUIDL()# is called for legacy connectors. . All RPC methods received from the server are invoked. . Connectors that are no longer included in the hierarchy are unregistered. This calls [methodname]#onUnregister()# on the [interfacename]#Connector#. . The layout phase starts, first checking the sizes and positions of all elements, and then notifying any [interfacename]#ElementResizeListener#s, as well as calling the appropriate layout method for the connectors that implement either [classname]#SimpleManagedLayout# or [classname]#DirectionalManagedLayout# interface. eaking'>Temp_KnuthStylePageBreaking Apache XML Graphics FOP: https://github.com/apache/xmlgraphics-fopwww-data
aboutsummaryrefslogtreecommitdiffstats
path: root/examples/fo/basic/tableunits.fo
blob: cfc672d67647abacfdb7560c28ebc784f5fcf468 (plain) 
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
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221