Re: [ANN] LJIT2X11 - These bindings go to 11!
- From: Cosmin Apreutesei <cosmin.apreutesei@xxxxxxxxx>
- To: luajit@xxxxxxxxxxxxx
- Date: Sun, 23 Aug 2015 18:16:28 +0300
Actually, the suggestion to open separate Xlib and XCB connections is
an EVEN BETTER idea. That way you can keep the crap cleanly isolated
away, so that the Xlib junk only has to be responsible for a single
rectangle, which you can abstract away with a fairly minimal amount of
code.
For this you have to add in threads because you can't just select() on
two connections yourself and then use the respective polling functions
without blocking.
Anyway, the XCB page makes it sound like Xlib is the real problem of
X, which is sad/amusing. There's actually very little difference in
practice between XCB and Xlib except Xlib has some useful utilities on
top (eg. image format conversions) and it's not a deployment problem
(not all libxcb extensions come pre-installed with X while libX and
libXext are), so it actually doesn't solve anything. And don't get me
started on Wayland (don't worry I won't - not on this list) :)
Other related posts:
