[cairo-commit] [cairo-www] src/todo.mdwn

[Chris Wilson]

 src/todo.mdwn |   21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

New commits:
commit 0fad90e946f00548b9b4f357e0010981baffdd4c
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Wed Oct 8 16:14:51 2008 +0100

    More bugzilla copying.
    
    Add some more todo items from bugzilla.

diff --git a/src/todo.mdwn b/src/todo.mdwn
index 858d01d..36b53ee 100644
--- a/src/todo.mdwn
+++ b/src/todo.mdwn
@@ -80,7 +80,7 @@ Changes that add new API (API changes/removals will not be considered)
 
  * Export meta surfaces
 
-   Examples for possible uses: a combined surface <https://bugs.freedesktop.org/attachment.cgi?id=5764>
+   Examples for possible uses: a combined surface <https://bugs.freedesktop.org/attachment.cgi?id=5764>, multipage surface (like psnup, page selection, reverse ordering) [0](https://bugs.freedesktop.org/attachment.cgi?id=4507), [1](https://bugs.freedesktop.org/attachment.cgi?id=4506), [2](https://bugs.freedesktop.org/attachment.cgi?id=4509), [3](https://bugs.freedesktop.org/attachment.cgi?id=4505) and [4](https://bugs.freedesktop.org/attachment.cgi?id=4508).
 
 Further comparison of cairo with other vector graphics languages, and in particular features that cairo lacks, can be found in [missing](/missing).
 
@@ -89,6 +89,25 @@ Performance improvements
  * Add dashing support to the fast-path rectilinear stroking
    code, (will help GTK+ focus rectangle, for example)
 
+ * Special-case extreme scaling of dashed lines i.e. when dashes are sub-tolerance
+
+  To quote Carl, "We can take the maximum single length from the
+  dash sequence, (either drawn or not), and compute its maximum size in device
+  space. (We should have code for that part in cairo_pen.c).
+
+  Then if that length is less than the tolerance, multiplying the current alpha
+  by the percentage of the dash sequence that's lit, then stroking a solid line
+  should be sufficient."
+
+  An incomplete patch can be found here: <https://bugs.freedesktop.org/attachment.cgi?id=2277>
+
+  A remaining task is
+  "One approach that would work is a sliding integral over the pattern with a
+  1-pixel-wide window, checking for a constant value at every position, (after
+  rounding based on the maximum 8-bit alpha depth)."
+
+  Again profiling, and a perf-case showing the improvements are also necessary.
+
  * Improve software polygon compositing by doing it in a
    single scanline pass rather than tessellating, rasterizing, then
    compositing the entire polygon.