[cairo-commit] glitz ChangeLog,1.40,1.41 TODO,1.8,1.9

[David Reveman]

Committed by: davidr

Update of /cvs/cairo/glitz
In directory pdx:/tmp/cvs-serv6165

Modified Files:
	ChangeLog TODO 
Log Message:
TODO list update

Index: ChangeLog
===================================================================
RCS file: /cvs/cairo/glitz/ChangeLog,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** ChangeLog	20 Jul 2004 07:51:13 -0000	1.40
--- ChangeLog	22 Jul 2004 20:03:46 -0000	1.41
***************
*** 1,2 ****
--- 1,6 ----
+ 2004-07-22  David Reveman  <c99drn at cs.umu.se>
+ 
+ 	* TODO: Added some important stuff to the TODO list.
+ 
  2004-07-20  David Reveman  <c99drn at cs.umu.se>
  

Index: TODO
===================================================================
RCS file: /cvs/cairo/glitz/TODO,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** TODO	20 Jul 2004 07:51:13 -0000	1.8
--- TODO	22 Jul 2004 20:03:46 -0000	1.9
***************
*** 1,2 ****
--- 1,12 ----
+ * Remove the solid surface type from the API. 1x1 surfaces should
+   internally work in sort of the same way as solid surfaces do now. So
+   a solid surface type will no longer be needed.
+ 
+ * Remove linear and radial surface types and the color range type. Linear
+   and radial gradients should just be another set of filters.
+ 
+ * Add low-pass sub-pixel filters for HW accelerated color balancing 
+   of per-component alpha masks.
+ 
  * GL_MESA_pack_invert support.
  
***************
*** 5,8 ****
--- 15,28 ----
  * Retained-mode rendering.
  
+ * Internal composite interface version 2. This will replace pretty much
+   all of the code in the glitz_composite function. This new interface
+   will be really simple, transformations will be accomplished by just setting
+   texture matrices and repeat will always be handled by HW. However, the
+   GL_ARB_none_power_of_two_texture extension will be required (I don't know
+   any hardware that actually support this yet). This is the perfect solution
+   and definitely the future. (Possible problem with render_texture as we need
+   to be able to set the texture border color and I'm not sure the existing
+   render_texture interfaces allow this.)
+ 
  * WGL (Windows GL) backend.