I look closely at this stuff, and the two are compatible. xcb is a protocol generated from X, automatically, with adjustments to rid the synchronous waits. Works great.
To make xcb interface to Wayland is the reverse process, use the auto generated headers to make the graphical object templates needed for client API. I think this auto-reversal was on the minds of xcb developers as there is way too much redundancy in all the interfaces, most work fine on the generic interface structures. But by capturing it all with individual definitions, in name only, then they capture a complete reversal, and the xcb users can be unaware. If they follow the complete definition, xcb code will adapt to wayland with little work.
No comments:
Post a Comment