Sorry this may be a very inept question:|
How will this effect integration with OpenGL. I know we use a lot of get/sets on pixels buffers; off screen rendering, textured (especial animated) and tricks. You want and need that raw data access. taking it way I think would also break GTKGLExt if I am not mistaken?
As I have come to understand, most GL windows have a completely different context than the windowing system itself. Is cairo going to play nice?
I mean with this:
> Date: Fri, 3 Sep 2010 09:52:22 -0400
> Subject: Re: pixbuf<->cairo_surface_t conversion
> From: matthias clasen gmail com
> To: sandmann daimi au dk
> CC: gtk-devel-list gnome org; hp pobox com
> On Fri, Sep 3, 2010 at 3:22 AM, Soeren Sandmann <sandmann daimi au dk> wrote:
> > Not that it matters that much, but if you use cairo_mask() with the
> > pixbuf data as both source and mask, the source as RGB24 and the mask
> > as ARGB32, you could make cairo do the conversion from pixbuf to
> > surface. That would likely hit an SSE2 or ARM NEON optimized code path
> > in pixman.
> Interesting. But how would that deal with the fixed-endianness of
> pixbuf data vs the native endianness of cairo ?
> gtk-devel-list mailing list
> gtk-devel-list gnome org