Re: [clutter] client-side matrix

2009-02-23 Thread Havoc Pennington
Hi, On Mon, Feb 23, 2009 at 3:26 AM, Tomas Frydrych t...@linux.intel.com wrote: I do not particularly like this idea on principle, as you are moving processing from GPU to CPU. Also, it feels like you are trying to address driver brokenness in Clutter. I would say the main win of the patch

Re: [clutter] client-side matrix

2009-02-23 Thread Robert Bragg
On Mon, 2009-02-23 at 08:26 +, Tomas Frydrych wrote: Havoc Pennington wrote: Anyway, maintaining the matrix client-side does not look super hard but it's mostly a series of matter of taste judgment calls so if anyone could give some guidance on how to approach this... some early

Re: [clutter] client-side matrix

2009-02-23 Thread Robert Bragg
On Sun, 2009-02-22 at 01:35 -0500, Havoc Pennington wrote: Hi, When using indirect rendering (I know, it's insane, but currently needed for compositing managers), shoveling the matrix over the X socket and occasionally pulling it back is turning out to be a pretty bad problem. Every

Re: [clutter] client-side matrix

2009-02-23 Thread Havoc Pennington
Hi, On Mon, Feb 23, 2009 at 7:32 AM, Robert Bragg b...@o-hand.com wrote: I'd personally be fairly happy with the flush type approach; but I'd take the opportunity to add something like cogl_flush_gl_state() which I think would tie into ideas we've discussed in the past about improving the

Re: [clutter] client-side matrix

2009-02-23 Thread Havoc Pennington
Hi, On Mon, Feb 23, 2009 at 7:32 AM, Robert Bragg b...@o-hand.com wrote: The biggest disadvantage to dealing with the matrices client side looks to be with tracking the inverse matrix. Calculating the inverse can be a rather expensive operation, and at least looking at the Mesa code it's

Re: [clutter] client-side matrix

2009-02-23 Thread Havoc Pennington
Hi, On Mon, Feb 23, 2009 at 7:32 AM, Robert Bragg b...@o-hand.com wrote: Personally I wouldn't be so worried about this - at least not for the same reason. I think there are good reasons why GLES 2.0 and OpenGL 3.0 scrapped the GL matrix stack APIs entirely. I don't think it's typical for the

Re: [clutter] client-side matrix

2009-02-23 Thread Robert Bragg
On Mon, 2009-02-23 at 08:09 -0500, Havoc Pennington wrote: Hi, On Mon, Feb 23, 2009 at 7:32 AM, Robert Bragg b...@o-hand.com wrote: I'd personally be fairly happy with the flush type approach; but I'd take the opportunity to add something like cogl_flush_gl_state() which I think would

Re: [clutter] client-side matrix

2009-02-23 Thread Robert Bragg
On Mon, 2009-02-23 at 08:12 -0500, Havoc Pennington wrote: Hi, On Mon, Feb 23, 2009 at 7:32 AM, Robert Bragg b...@o-hand.com wrote: The biggest disadvantage to dealing with the matrices client side looks to be with tracking the inverse matrix. Calculating the inverse can be a rather

[clutter] client-side matrix

2009-02-21 Thread Havoc Pennington
Hi, When using indirect rendering (I know, it's insane, but currently needed for compositing managers), shoveling the matrix over the X socket and occasionally pulling it back is turning out to be a pretty bad problem. Every glPushMatrix(), PopMatrix, Translate, etc. is another X request. In an