Re: "floccinaucinihilipilification", or "convolutions, blocking, and windows server 2003"

Around 13 o'clock on Mar 16, Jaymz Julian wrote:

> I looked at it, and it looked to me like it was specifically for a 
> transformation filter (bilinear, nearest, etc)

Nope.  Filters are always applied on the source operands.  Note that these 
two are identity functions when there is no transformation, hence your 
confusion is understandable.

> I can move this code to use the Filter mechinism easily enough. 

Ok, cool.  You basically get a giant array of fixed point numbers to do 
whatever you want with.  If you want to add optimized filters for special 
purposes, please feel free to implement more than one 'convolution' filter 
and give them new names.  Surely a special 'blur' filter would be very 
welcome if it was really fast.

As for chaining convolutions, I suggest that a combination of convolutions
should itself be a well defined convolution.  Hence, we can simply compute 
the overall convolution on the client side.

> I wanted to see wether people wanted this complexity of operations before
> I spent the time to clean it up.

The answer is "no", we don't want to see all of that complexity in the 
server.  Remember that our goal here is to:

	a)	Reduce network traffic
	b)	Get at hardware acceleration

An explicit non-goal is to provide an easy to use API at this level -- 
that's a problem for higher level libaries (like cairo).  Given that we 
can even use intermediate buffers if necessary without increasing network 
traffic, and given that hardware is unlikely to support combinations of 
filters any time soon, it seems clear that a single filter should suffice.

Can you list the filters that you have implemented?  We should be able to 
figure out how to parameterize them pretty easily.

-keith

_______________________________________________
xserver mailing list
[email protected]
http://freedesktop.org/mailman/listinfo/xserver

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.3.1 11/28/2001

iD8DBQFAVnGbQp8BWwlsTdMRAuyaAJwN+NcEix/8pxmB2LvoFkrFrDixJQCgjxpV
0GSiu1insiDiCGfJWR1FZfM=
=VfBR
-----END PGP SIGNATURE-----