freenode/#clim - IRC Chatlog
Search
15:35:13
loke
I think the protocol and Xlib implementations were implemented hand-in-hand, and the protocol spec was written after the fact.
15:36:13
loke
There is a section called "Common types" which lists datatypes used in the protocol in multiple places, so they document their format in one place. That sounds good, no?
15:37:36
loke
Well, I found some references to the explicitmask (as far as I understand, this mask should be AND'ed with the modifier bits to determine what explicit role it has (or something to that effect)
15:38:08
loke
Well, turns out that the only mention of explicitmask in the entire spec is in the common section. I have no idea how it's supposed to be used.
15:39:04
loke
It may be mentioned somewhere in the spec but under a slightly different name? (wouldn' tbe the first time)
15:42:01
pjb
Or may be it's not used anymore. check old versions of the standard or implementations.
15:43:03
loke
I have been cross-referencing against libX11 all the time. Unfortunately, the client-side of XKB is pretty large. I have no intention of implementing most of the spec for now, but the libX11 code handles everything.
15:43:30
loke
Also, of course it handles multiple encodings as well, which any sane modern language shouldn't have to.
15:48:28
loke
I'm able to properly map keycodes+modifiers to the correct keysyms now. That's progress. However, I can't for the life of me figure out how to determine that a key is a dead key. And, even if I could, I don't know how to map a dead-key sequence to a string. I think the old code that I'm working off of is not complete here, since when fetching the entire keymap from the X-server, the character (or string) "รก" (which is written
15:48:47
loke
And of course, the word "dead" only occurs in the list of default keysyms in the protocol spec.
19:04:08
scymtym
loke: for the ffi-based font renderer, how does font loading work and which interface is used?