Friday, January 4, 2019

Final point

We do not nested pages and pages of code to do a table look up, a bit complicated, but a table look up.  The keyboard and bitmap the feeds my display hardware are entirely different, take a look.

The xkbcommon folks seem to be headed in that direction, and are removing keyboard crap entirely out of X11, unlike the dufases at MIT.

But still, even though each keyboard is different, and needs a special map, once the map is installed, I cannot image more than 20-40 lines of code to execute the map between ascii and scan code, not can I amagine why we would even carry around string descriptors of bytes, the ascii byte itself, to the two byte version, is what we ant.  Whatever the linux kernel is doung with string for chars seems stupid.

Let us make a rule.  If you work on kbdcommon, then you are not allowed to lok at x11 or xcb at all, you are required to pretend keyboards are not GUI screens, if a plain view of the keyboard is not enough to convince you.

My plot os to figure out the common map for numbers and letters, do those with my 20 lines of code, then leave it at that.  I am not waiting 5 years for GUI folks to get unconfused about key boards.

No comments: