path: root/Events/XDC2014/XDC2014Graesslin.mdwn
diff options
authormperes <mperes@web>2014-10-10 02:40:50 -0700
committerxorg <>2014-10-10 02:40:50 -0700
commitb1634edeb792d88fda4bc384ab50763e3f93f147 (patch)
treefbd7ad38f3a60b926fb8e745af369c95f0320f0a /Events/XDC2014/XDC2014Graesslin.mdwn
parent9c4f65003041a8437749c44f6d858998879d4693 (diff)
Diffstat (limited to 'Events/XDC2014/XDC2014Graesslin.mdwn')
1 files changed, 1 insertions, 1 deletions
diff --git a/Events/XDC2014/XDC2014Graesslin.mdwn b/Events/XDC2014/XDC2014Graesslin.mdwn
index 2b0a3ad3..986914f8 100644
--- a/Events/XDC2014/XDC2014Graesslin.mdwn
+++ b/Events/XDC2014/XDC2014Graesslin.mdwn
@@ -7,4 +7,4 @@ This talk will explain why we did a complete transition to XCB in KWin and the s
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.
+[[Slides|kwin-xdc.pdf]] (CC-BY-SA)