diff options
author | Søren Sandmann Pedersen <ssp@redhat.com> | 2009-02-26 04:28:00 -0500 |
---|---|---|
committer | Søren Sandmann Pedersen <ssp@redhat.com> | 2009-02-26 04:28:00 -0500 |
commit | 39607168413c9708ac1104fa5e2568139b12b7a4 (patch) | |
tree | e1a6e0c01052c7ae4e945b94d2bcb18f906011b8 | |
parent | cfaa1868ef4b5c0cb81718200fb8fc5b64b617c5 (diff) |
TODO
-rw-r--r-- | TODO | 21 |
1 files changed, 21 insertions, 0 deletions
@@ -51,6 +51,27 @@ 4. Delete shadow 5. Wrap some of the ops, or use XAA? + The input we get is: + + - First a damage notification: "I am going to draw here" + - Then maybe an exa notification + + So the algorithm is. + + Maintain a "to_copy" region to be copied into the device + + - in damage, if there is anything in to_copy, copy it + + - in block handler, if there is anything in to_copy, copy it + + - in exa, if we manage to accelerate, delete to_copy. + + Unfortunately, for core text, what happens is + - damage is produced for the glyph box + - solid fill is generated + - the glyph is drawn + And the algorithm above means the damage is thrown away. + - Coding style fixes - Better malloc() implementation |