Meta tags:

Headings (most frequently used words):

2010, xcb, gsoc, for, tuesday, xkb, mapping, improve, input, support, august, wednesday, 14, july, 15, june, friday, 28, may, pages, followers, blog, archive, about, me, it, compiles, switch, xml, language, internals, of, python, generator, code,

Text of the page (most frequently used words):
the (89), for (22), xcb (20), and (20), are (18), #switch (18), xkb (17), that (15), size (15), new (13), fields (13), 2010 (12), protocol (12), with (12), variable (12), xml (11), code (11), gsoc (10), mapping (10), fixed (10), support (9), input (8), types (8), type (8), functions (8), cases (8), special (8), data (8), some (7), introduced (7), list (7), can (7), extend (6), will (6), elements (6), newly (6), need (6), generator (6), all (6), from (6), request (6), comments (5), one (5), have (5), number (5), they (5), other (5), language (5), but (5), mapped (5), not (5), posted (4), next (4), this (4), still (4), into (4), first (4), has (4), last (4), issues (4), more (4), each (4), use (4), out (4), had (4), should (4), autogenerated (4), most (4), compiles (3), posts (3), extended (3), order (3), python (3), description (3), been (3), thanks (3), few (3), made (3), any (3), interfaces (3), field (3), statements (3), struct (3), which (3), interface (3), now (3), these (3), include (3), lists (3), length (3), valueparam (3), contain (3), set (3), auxiliary (3), _serialize (3), needed (3), _unserialize (3), also (3), expressions (3), complete (2), about (2), may (2), june (2), july (2), august (2), home (2), well (2), system (2), required (2), describe (2), extension (2), documented (2), files (2), part (2), described (2), here (2), utility (2), internals (2), time (2), tags (2), before (2), you (2), changes (2), existing (2), however (2), within (2), discussion (2), takes (2), mailing (2), bitcase (2), serialized (2), get (2), named (2), function (2), call (2), short (2), overview (2), there (2), value (2), params (2), util (2), aux (2), peter (2), harris (2), test (2), case (2), defined (2), valid (2), requests (2), sized (2), way (2), tag (2), deep (2), changed (2), enable (2), tuesday (2), additional (2), those (2), difficult (2), called (2), automatically (2), mentioned (2), easy (2), conditions (2), kind (2), same (2), moment (2), even (2), grouped (2), several (2), deal (2), treatment (2), accessors (2), evaluated (2), keyboard (2), item (2), was (2), main (2), turned (2), serialize (2), unserialize (2), side (2), improve (2), skip (2), view, profile, blog, archive, followers, doc, pages, subscribe, atom, step, think, topic, parser, underlying, soon, sure, describing, extensions, converted, written, basically, consists, two, parts, detail, parses, produces, goal, implement, bindings, thing, concentrate, generate, binding, done, mariusz, ceier, year, reading, friday, since, post, emerged, meanwhile, tell, functionality, let, fix, testing, start, writing, days, place, appreciated, please, feel, free, join, different, except, prefix, switch_struct, series, form, generated, encompasses, switch_expr, bitcase_expr, popcount, xcb_popcount, sumof, xcb_sumof, implemented, performs, summation, referenced, enum, simply, corresponding, integer, constant, remains, give, remain, properly, make, somewhat, easier, module, obsolete, rewriting, pointing, provides, excellent, descriptions, buggy, structs, following, addressed, changing, registered, context, lookup, anchestor, hidden, inside, parsing, autogenerating, requires, jamey, sharp, revealed, requirements, working, subset, consist, only, remaining, thus, debugging, prototype, createwindow, xproto, overhead, serialization, process, neglible, machine, best, using, _aux, take, argument, perform, necessary, allows, conditional, inclusion, achieve, compatibility, transform, structure, character, stream, vice, versa, evaluating, principle, rewritten, would, practice, relevant, change, reside, could, wednesday, while, trying, autogenerate, during, months, sometimes, felt, like, attempt, behead, hydra, whenever, problem, arose, intestines, seems, reached, state, where, heads, emerge, managed, cut, off, ugliest, cause, troubles, very, basic, distinguishing, everything, feed, sizeof, valueparams, padding, normally, together, collected, whose, purpose, translate, between, server, client, advantage, ordering, conveniently, fairly, involves, iterators, specific, depend, specified, runtime, breaks, pure, doctrine, core, intermixed, further, problematic, union, finally, defines, datatype, listofitems, referred, items, necessarily, whether, included, depends, separately, defining, goals, work, must, either, buffer, depending, concrete, means, especially, switches, once, autogenerator, spill, used, notably, above, intermixing, probably, appealing, feature, serializers, invisible, anyone, who, wants, helper, note, current, status, finished, tests, simple, programs, run, reply, renamed, _sizeof, currently, hosted, annarchy, export, repos, shortly, unaware, capable, aware, applications, sidebar,

Text of the page (random words):
gsoc 2010 improve input support for xcb skip to main skip to sidebar gsoc 2010 improve input support for xcb xcb keyboard support should be extended to enable xkb unaware xkb capable or even xkb aware applications tuesday 3 august 2010 xcb xkb it compiles while trying to autogenerate c interfaces for xkb during the last 2 months it sometimes felt like an attempt to behead the hydra whenever i fixed a problem a number of new issues arose deep from the intestines of the python code generator at the moment it seems i have reached a state where no new heads emerge and i even managed to cut off a number of the most ugliest the cause of most all troubles is a very basic way of distinguishing data types into fixed size everything you can feed to sizeof variable size data types lists valueparams and padding in the x protocol fixed size fields are normally grouped together so e g in a request all fixed size fields are collected before any variable size fields xcb whose purpose it is to translate between x server and client takes advantage of this ordering several grouped fixed size fields are conveniently mapped to a c struct so it is fairly easy to deal with the treatment of variable size data is more difficult and involves the use of autogenerated accessors and iterators also the specific number of elements in a variable size data type can depend on expressions that are specified in the protocol but need to be evaluated at runtime now xkb breaks with the pure doctrine of the x core protocol fixed and variable size fields are intermixed in several cases and new expressions are introduced further problematic cases include a variable size union lists with a variable number of variable size elements and finally the keyboard extension defines a new datatype listofitems which is referred to as switch in xcb switch is a kind of list but the items are not necessarily of the same type and whether an item is included or not depends on expressions that have to be evaluated for each item separately defining a c mapping for switch was one of the main goals of my work and it turned out that a set of new functions was needed these new functions must either serialize a switch into a buffer depending on the concrete switch conditions or unserialize it to some c struct as switch can contain any other data type valid in the x protocol which means especially that it also can contain other switches serialize unserialize had to be defined for all those data types once i had the autogenerator spill out _serialize and _unserialize it turned out they can be used to deal with some other special cases as well most notably the above mentioned intermixing of fixed and variable size fields but probably the most appealing feature of the serializers is that they are invisible to anyone who wants to use xcb as they get called automatically in the autogenerated helper functions a last note on the current status xkb c autogenerated from xkb xml compiles the request side should be finished more tests needed however simple xkb test programs run on the reply side special cases still need special treatment _unserialize should be renamed to _sizeof in some cases some special cases also need special accessors the code is currently hosted on annarchy but i will export the repos shortly posted by gsoc 2010 extend xcb input support at 13 12 2 comments wednesday 14 july 2010 c mapping for switch autogenerating c code from xcb s xkb xml requires mapping of the newly introduced switch tag discussion on the mailing list special thanks to peter harris jamey sharp revealed additional requirements valueparam a special kind of x protocol list type can in principle be rewritten to switch if one would do so in practice the relevant request interface should not change at the same time auxiliary functions that reside in util aux at the moment could be autogenerated from the protocol description switch is a special list type that allows conditional inclusion of fields in order to achieve the mentioned compatibility with request interfaces for valueparam a new set of functions is needed _serialize and _unserialize that transform an easy to use auxiliary data structure into a character stream and vice versa evaluating the switch conditions in each case requests that contain switch statements are best called from c using a newly introduced set of _aux functions that take an auxiliary data type for switch as an argument and perform the necessary call to _serialize automatically the code generator is now working for a subset of switch statements ie those that consist of fixed size fields only the remaining cases are more difficult and thus need debugging as a prototype i have changed the valueparam in the createwindow request xproto xml to switch the overhead introduced by the additional serialization process is neglible on my machine posted by gsoc 2010 extend xcb input support at 15 56 no comments tuesday 15 june 2010 xcb gsoc xkb xml c language mapping it s been some time since my last post and the first c language mapping for the newly introduced xml tags has emerged in the meanwhile but before i ll tell you about the new functionality let me first describe a few changes i made to the existing code to fix a few issues with xcb s internals there are a few issues hidden deep inside the xcb c code generator that had to be changed in order to enable parsing of the xkb protocol description here s a short overview for types with a variable length a length field has to be registered with the type system within the context of the newly introduced tag the lookup for the length field had to be extended to include all anchestor types in some cases no c mapping has been defined up to now for valid xml protocol descriptions these include 1 requests with fields that are not fixed size and not lists 2 request with list of variable sized elements buggy 3 structs with fixed size fields following variable sized fields these issues will be addressed by changing the way types are serialized in the c language mapping there is an interface to make value params somewhat easier to use in the util aux module this interface can be made obsolete by rewriting value params to switch thanks to peter harris for pointing this out it provides an excellent test case for switch the changes i made to the existing code still remain to be properly documented it remains to give a short overview of the mapping for the new xml tags enum is simply mapped to the corresponding named integer constant in c sumof is mapped to a function call to xcb_sumof newly implemented which performs a summation of the elements of the referenced list popcount is mapped to a function to xcb_popcount switch is mapped to a series of if statements each of the form if switch_expr bitcase_expr for each a struct is generated that encompasses all named bitcase fields bitcase fields are serialized no different from other field except they get a prefix switch_struct the new elements still need more testing however i will start writing xkb utility functions within the next days any discussion of new interfaces takes place on the xcb mailing list all comments are appreciated so please feel free to join posted by gsoc 2010 extend xcb input support at 14 58 no comments friday 28 may 2010 internals of xcb python generator code hi first thanks for reading the goal of my gsoc is to extend input support for xcb i e implement xkb bindings and utility functions the first thing i have to concentrate on is to generate a c language binding for the xkb protocol the required xml protocol description has been done by mariusz ceier in last year s gsoc the xml files describing the x protocol and extensions are converted into c code with a code generator written in python the code generator basically consists of two parts one part described here in detail parses the xml files the other part will be described in one of my next posts produces the language mapping i have extended the xml parser the underlying type system as a number of new elements are required in order to describe the xkb protocol extension the newly introduced types still need to be documented i will do that as soon as i am sure they are complete the next step will be to think of some c mapping for the new types this as well be the topic of one of the next posts posted by gsoc 2010 extend xcb input support at 12 15 no comments home subscribe to posts atom pages home doc followers blog archive 2010 4 august 1 xcb xkb it compiles july 1 june 1 may 1 about me gsoc 2010 extend xcb input support view my complete profile