If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

Using XCB is a great step forward and since XCB is closer in nature to how Wayland works, these changes will also make the port to Wayland easier to pull off. Great work!

Oh and P.S. --> Funkstar makes Quaridium look like an intelligent and rational poster. Larabel: If you want more people to turn off that hated Ad-block or pay for Phoronix, do a little housekeeping and get the goat to kick the troll off the bridge, mkay?

Comment

?? Could you elaborate? I don't see how XCB is closer in nature to how Wayland works..
I'm not saying that you're wrong but I'd like to understand what you mean.

I'm not saying that the XCB API == Wayland API (far from it). However, both XCB and Wayland are highly asynchronous in nature, while the traditional Xlibs are synchronous (e.g. blocking waits, poor multi-threading, etc.). Getting large parts of Kwin and other KDE components written so that they work properly with an asynchronous model will make interfacing with Wayland easier to do.