[Xcb] OK, I lied; one more image library update

[Vincent Torri]

On Thu, 29 Nov 2007, Barton C Massey wrote:

> In message <Pine.LNX.4.64.0711290829330.10218 at grozny.maths.univ-evry.fr> you wrote:

>> On Wed, 28 Nov 2007, Barton C Massey wrote:

>>> BTW, nothing's certain yet, but it looks like there's a good
>>> chance I'll be traveling to FOSDEM next February to talk
>>> about XCB and X images.  Big fun if it works out.
>>
>> if you want me to do some stuff about evas and ecore with xcb that you
>> want to add to your talk, tell me. Btw, I think i'll go to FOSDEM too :)
>
> It will be cool to see you there!  If you want, you could
> give your own talk about evas, ecore, and xcb---I think that
> would be great.  But if you'd prefer, I'd be happy to find
> out about what you've done and talk about it.

Actually, I don't know if I will do a talk or not. What afraids me is 
doing one in english :)

what is interesting with evas - ecore : you compile ecore with xcb 
support, you do minor changes to ewl (the toolkit) and hop, you have a 
toolkit that uses xcb :) There are still some problems with ecore-xcb, but 
not much.

> The main thing needed in util right now
> is Doxygen for aux and any other libraries we're sure we're
> keeping.  Thanks for starting out the Doxygen work---it
> really helped me.  I know that the core stuff in xcb.h needs
> Doxygen as well, and that it's probably my job to extract
> that from the wiki and get it on there.

afaik, I've already added the doc to xcb.h, unless someone removed it.

> I'm not sure what to do about
> xproto.h and all the extensions. I fear that somehow
> someone needs to get the protocol docs into the XML in a way
> that lets Thomas' bits (which I'm rooting for any day now
> hint hint :-) generate Doxygen for the generated header
> files.

It's my job : I'll add doc comments in sync.xml and Thomas will try to 
adapt his python parser to read the documentation for that file. It was 
the plan, afaik.

Vincent