blob: 3b9f4168de3b9355ef605a64d64a19f8cbacd6c0 (
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
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
|
ClearArea
---------
Basically a special case of PolyFillRect. Put up some sort of image first
so we can clear it away. Try both small areas and big areas, to give
credit to servers for optimizing small ones.
Data: Pixels per second.
Breaking that down into large and small areas would probably not
be userful.
GC Fields: None.
CopyArea
--------
Putting up some image and then repeatedly copying from one part of it
to another would do the right thing and could look neat if done right.
We probably want to see what happens when the source area is clipped,
as that as mentioned specifically in the protocol document.
Data: Pixels per second.
GC Fields: function (*)
plane-mask
subwindow-mode
graphics-exposures
clip-x-origin
clip-y-origin
clip-mask
CopyPlane
---------
Special case of CopyArea again.
PolyPoint
---------
Draw lots of points.
Either start out with an image that's 50/50 black and white
(preferred) or draw enough points that some points will get drawn at
least twice (to test functions other than copy).
Data: Points per second.
GC fields: function (*)
plane-mask
foreground
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
PolyLine
--------
Circular test like there is now.
Try clipping at window boundaries?
Data: Lines per second.
Pixels per second (is this valid - do lines that are twice as
long take twice as long to draw? Also, is it valid to compare
thin lines and fat lines?)
GC fields: function (*)
plane-mask
line-width (*)
line-style (*)
cap-style (*)
join-style (*)
fill-style (*)
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile (*)
stipple (*)
tile-stipple-x-origin
tile-stipple-y-origin
dash-offset
dashes (*)
PolySegment
-----------
Just like PolyLine but lines don't have to be connected. Crosshatching?
Data: Lines per second, pixels per second(?)
GC fields: function
plane-mask
line-width
line-style
cap-style
fill-style
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
dash-offset
dashes
PolyRectangle
-------------
Lots of five point PolyLines. Partly concentric ones would look nice; we
also need overlap for testing different functions.
Data: Rectangles per second.
Pixels per second? (divide by perimeter)
GC fields: function
plane-mask
line-width
line-style
join-style
fill-style
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
dash-offset
dashes
PolyArc
-------
Overlapping concentric things (ripples) would look cool.
Is it possible to special-case circles? Test for this?
Data: Arcs per second? If we had the same test each time this might
be OK.
Pixels per second? Finding the length of an arc could be
annoying.
GC fields: function
plane-mask
line-width
line-style
cap-style
join-style
fill-style
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
dash-offset
dashes
FillPoly
--------
Use the same test as PolyLine?
Overlapping is a must to test functions.
Convex vs. Concave polygons.
Data: Pixels per second, I guess.
Data for convex vs. concave could be interesting.
GC fields: function
plane-mask
fill-style
fill-rule
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
PolyFillRectangle
-----------------
Use same test as PolyRectangle?
Perhaps give FillPoly some of these too, see if it special cases them.
Fill Rectangle vs. Fill Poly for same size areas would be an
interesting comparison.
Data: Pixels per second.
GC fields: function
plane-mask
fill-style
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
PolyFillArc
-----------
Use same test as PolyArc?
Data: Pixels per second would be hard to compute, but what else is there?
GC fields: function
plane-mask
fill-style
arc-mode
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
PutImage
--------
GC fields: function
plane-mask
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
GetImage
--------
PolyText8
---------
GC fields: function
plane-mask
fill-style
font
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
Possibly foreground
background
tile
stipple
tile-stipple-x-origin
tile-stipple-y-origin
PolyText16
----------
ImageText8
----------
GC fields: plane-mask
foreground
background
font
subwindow-mode
clip-x-origin
clip-y-origin
clip-mask
ImageText16
---------
|
