[Xcb] To do

[Jamey Sharp]

On Wed, Feb 02, 2005 at 07:27:41PM +0100, Vincent Torri wrote:
> On Wed, 2 Feb 2005, Jamey Sharp wrote:
> > On Wed, Feb 02, 2005 at 01:35:12AM -0500, Jeremy Kolb wrote:
> > > Is there anything sort of easyish thing that needs to get done? Or
> > > modifications to glx/randr that need doing?
> >
> > A convenience function built on top of XCBPutImage and XCBSHMPutImage
> > that uses SHM if available and core X otherwise would be great. This
> > is one of the few convenience functions I feel comfortable putting in
> > libXCB itself. If that function also split images into chunks smaller
> > than 256kB when using core X, that would be nice too (but possibly
> > harder).
> 
> I have already written the code for XCBImage and all the related
> functions. I does not work yet, but i've just finished it yesterday...
> After that, i'll see about the shm port of it.

Ooh, that's cool. If you've implemented everything that XImage supports,
then you've figured out possibly the most confusing part of the core X
protocol. Congratulations! You'll have to explain it to me sometime. :-)

Unfortunately, if your code does everything XImage does, that means that
it's more complicated than the piece I want to put in XCB, which I think
shouldn't do any format conversion -- just image splitting for core X,
and SHM where possible. Fortunately, I think that's probably easy
functionality to separate, so we can put the little stuff in libXCB and
make the rest available as a separate library or something.

I look forward to seeing your code, anyway.

Jeremy, the SHM work is separable. Also, it's just confusing enough to
be interesting. If you want to, you might see if you can put together
the code to detect whether SHM is applicable, and to use it if possible;
Vincent can continue work on his XCBImage bits at the same time.

--Jamey