diff options
author | Søren Sandmann Pedersen <sandmann@redhat.com> | 2008-06-13 16:16:59 -0400 |
---|---|---|
committer | Søren Sandmann Pedersen <sandmann@redhat.com> | 2008-06-14 00:52:03 -0400 |
commit | 534e65d54831018b47c169932a04224e5ba53cb8 (patch) | |
tree | 98483776f5ec24b11fa939fcc77efac6747201a2 /TODO | |
parent | eb2d95de98683a387153f010077ad9c3c3b1b01d (diff) |
Update TODO
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 33 |
1 files changed, 32 insertions, 1 deletions
@@ -42,7 +42,7 @@ - Make pixman_region_point_in() survive a NULL box, then fix up pixman-compose.c - - Possibly look into inlining the fetch functions + - Possibly look into inlining the fetch functions - Test suite @@ -93,6 +93,37 @@ (0, 0). Cairo would have to make sure that the delta *within* a batch of trapezoids does not exceed 16 bit. + - Consider adding actual backends. Brain dump: + + A backend is something that knows how to + + - Create images + - Composite three images + - Rasterize trapezoids + - Do solid fills and blits + + These operations are provided by a vtable that the backend will + create when it is initialized. Initial backends: + + - VMX + - SSE2 + - MMX + - Plain Old C + + When the SIMD backends are initialized, they will be passed a + pointer to the Plain Old C backend that they can use for fallback + purposes. + + Images would gain a vtable as well that would contain things like + + - Read scanline + - Write scanline + + (Or even read_patch/write_patch as suggested by Keith a while + back). + + This could simplify the compositing code considerably. + - Review the pixman_format_code_t enum to make sure it will support future formats. Some formats we will probably need: |