path: root/Events/XDC2014/XDC2014Graesslin.mdwn
diff options
authormperes <mperes@web>2014-10-10 02:39:59 -0700
committerxorg <>2014-10-10 02:39:59 -0700
commit9c4f65003041a8437749c44f6d858998879d4693 (patch)
treefb6342cb1ddc3666a150f645f2aa9bffad218566 /Events/XDC2014/XDC2014Graesslin.mdwn
parent2de809ecb9dcee15af5f7c432ace9f3e5b4c4e5d (diff)
Diffstat (limited to 'Events/XDC2014/XDC2014Graesslin.mdwn')
1 files changed, 3 insertions, 0 deletions
diff --git a/Events/XDC2014/XDC2014Graesslin.mdwn b/Events/XDC2014/XDC2014Graesslin.mdwn
index 62a0aace..2b0a3ad3 100644
--- a/Events/XDC2014/XDC2014Graesslin.mdwn
+++ b/Events/XDC2014/XDC2014Graesslin.mdwn
@@ -5,3 +5,6 @@ Over the last two years KWin and other components of the Plasma workspace and th
This talk will explain why we did a complete transition to XCB in KWin and the state of the porting. The talk will highlight the issues we hit during the porting and also what we really liked about XCB in comparison to XLib.
As a C++ application using a low level C library is not particularly thrilling to the developers especially as it can be error-prone. The KWin development team went a long way to make using XCB inside the code base as convenient as possible and safe using advanced features of C++ like RAII and variadic templates. The talk will explain why we introduced wrappers for XCB and illustrates the advantages from a coding point of view. As these wrappers do not dependent on other parts of KWin and are mostly template based header only implementations they might be of interest for other C++ projects interacting with XCB.