[PATCH] Replace libx11 by libxcb
thiago at kde.org
Wed Jul 28 09:29:34 PDT 2010
On Wednesday 28. July 2010 13.01.54 Julien Danjou wrote:
> On Wed, Jul 28 2010, Havoc Pennington wrote:
> > Given that libX11 now uses xcb as backend, I don't understand the
> > value of porting to use libxcb directly when there isn't an issue of
> > round trips or other stuff.
> The (very) long term goal is to drop libX11. At least as much as
> possible. For the best.
Well, no. The very long term goal is to drop X11 completely, both the
protocol, the library and XCB.
So, from where I stand, XCB is just an intermediate step in making the library
"suck less" and bringing in some modern functionality like asynchronous calls
> I'm not sure of the meaning of 'port' here. If you mean packaging, I
> If you mean make XCB compiles everywhere, that should already be the case.
> There's even an almost finished port to Win32.
Win32 is one of the two systems where XCB doesn't matter (the other being
Mac). Does it compile and work on the other X11-based Unix platforms?
And can we expect those systems to start shipping XCB any time soon?
Anyway, I think we're going off-topic here. So, to bring it on-topic: thanks
for the patch, but like Havoc I am unsure of the value. We can't drop the X11
codepaths now because too many systems exist without XCB. Adding the XCB
codepaths only made it more complex, even though you did a good job.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the dbus