[Xcb] Bug 6254: remove XCB's xproto/X11 dependency

[Vincent Torri]

On Tue, 14 Mar 2006, Jamey Sharp wrote:

> On Mon, Mar 13, 2006 at 09:30:29PM -0500, Jeremy Kolb wrote:
> > > The <enum> construct generates very wordy symbols. (Example: enum  {
> > > XCBWindowClassInputOutput = 1 } XCBWindowClass; where previously  one
> > > only had to deal with InputOutput). You could argue that this is  a
> > > feature, though perhaps not for masks. Maybe an option to prefix  the
> > > members just with "XCB" and not the full name of the enumeration?
> >
> > I really think we need a better way of handling enums.  The names are
> > way too unwieldly.  Vincent and I have talked about this but we couldn't
> > come up with a good solution.  I really think it needs to be changed
> > though, not developer friendly at all.
>
> I like "developer-friendly" where possible, but one response to this is
> that I don't expect many people to program directly to XCB. Usually some
> toolkit is preferable; only the authors of toolkits, and some libraries
> like Cairo and libGL, should care much about XCB's API. My preference
> would be an API that closely reflects the protocol documentation. A bit
> of typing won't kill anyone.

For the toolkit, i don't know if gdk or qt can use xcb natively as their
backend, but ewl and etk will do (once raster and me will agree on how to
manage the requests/replies in ecore). Just fyi :)

That makes me think: bart, what about your toolkit ?

Vincent