[cairo-commit] cairo ChangeLog,1.288,1.289 TODO,1.24,1.25

[Carl Worth]

Committed by: cworth

Update of /cvs/cairo/cairo
In directory gabe:/tmp/cvs-serv28899

Modified Files:
	ChangeLog TODO 
Log Message:

        * TODO: Added some TODO items from mailing list traffic.


Index: ChangeLog
===================================================================
RCS file: /cvs/cairo/cairo/ChangeLog,v
retrieving revision 1.288
retrieving revision 1.289
diff -u -d -r1.288 -r1.289
--- ChangeLog	6 Jan 2005 01:46:31 -0000	1.288
+++ ChangeLog	6 Jan 2005 16:51:48 -0000	1.289
@@ -1,3 +1,7 @@
+2005-01-06  Carl Worth  <cworth at cworth.org>
+
+	* TODO: Added some TODO items from mailing list traffic.
+
 2005-01-05  Kristian Høgsberg  <krh at redhat.com>
 
 	* src/cairo_pdf_surface.c: (emit_image_data): Implement image

Index: TODO
===================================================================
RCS file: /cvs/cairo/cairo/TODO,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -d -r1.24 -r1.25
--- TODO	23 Dec 2004 21:49:56 -0000	1.24
+++ TODO	6 Jan 2005 16:51:48 -0000	1.25
@@ -1,3 +1,6 @@
+* Replace PNG backend with an image_surface function to save a PNG
+  image.
+
 * Clean up the API in preparation for freezing and release.
 
 * Implement a PDF backend.
@@ -69,9 +72,36 @@
   current path. We may also need to provide the coordinates of the
   faces of every dash as well.
 
+* Should add geometry pruning as appropriate.
+
 * We need a way to get at the image data after something
   like cairo_surface_create_similar with the image backend.
 
+* Three suggestions from Owen that will help GTK+ performance:
+
+  - The ability have an additional rectangle-list clip in the
+   Xlib surface. Frequently during an expose event, GTK+ is
+   drawing L shaped areas
+
+         XXXXXX
+         X.....
+         X.....
+
+   And passing the real clip to the server is going to save
+   a lot of pixel operations that will be thrown away.
+
+ - The ability to pass in a width/height to cairo_xlib_surface_create()
+   to avoid a round-trip. (Round-trips are bad to the point where
+   querying the the server is something you don't want to do in
+   production software)
+
+ - More of a future thing, the ability to hint to to cairo that
+   the contents of the Xlib surface passed to
+   cairo_xlib_surface_create() are a solid fill ... this is
+   very much the normal case for GTK+ usage and allows for
+   big optimization in the no-RENDER case.
+   (see http://mail.gnome.org/archives/gtk-devel-list/2003-March/msg00045.html
+
 * Verification, profiling, optimization.
 
 	centi_unfinished.svg may provide a good test case.