contents of this directory

 BlindTypingTest         07-Feb-2004 21:55     2k  
 Notes.txt               07-Feb-2004 21:57     3k  
 TSkeys.90.B.N.ps        09-Feb-2004 13:44   103k  
 TSkeys.90.D.K.ps        09-Feb-2004 13:44   103k  
 TSkeys.90.Tab.rsb.ps    09-Feb-2004 13:44   103k  
 TSkeys.90.til.bs.ps     09-Feb-2004 13:44   103k  
 TSkeys.ps               07-Feb-2004 21:34    77k  
 example                 07-Feb-2004 21:36     1k  
 keyloc.dat              07-Feb-2004 21:34     3k  


what these files are:

keyloc.dat:  

	a parse of the xml file that defines the default layout 
	for the TouchStream LP keyboard, into a tabsep data file
	that you can manipulate with the app of your choice.  
	the file contents look like

	4       4.13    2.91    E:1.30    Space  
	6       1.70    0.60    E:1.10    Enter (Thumb)  
	8       -4.03   2.91    E:1.30    BackSpace  
	...
	14      -12.4   12.00   C:1.0     1  
	16      -10.4   12.37   C:1.0     2  
	18      -8.4    12.5    C:1.0     3 
	...
	122     -15.7   4.25    R:2.5,2.0       Left Ctrl
	124     -13.1   4.2     R:2.5,2.0       Left Win/Cmd/Meta
	126     -10.6   4.15    R:2.5,2.0       Left Alt (Option)
	128     16.1    4.25    R:2.5,2.0       Right Ctrl

	the first column is an arbitrary key number generated by
	the xml parsing code, which as you can see is having a bit
	of difficulty -- all key numbers are even, that's just how
	it is until I fix the code.  don't let it bother you, these
	numbers are merely an artifact of the xml parse and a way
	to give your app a unique record id for each key.

	the second column is the x position in centimetres.  the
	third column is the y position in centimetres.

	the fourth column is more interesting, being a portmanteau
	for several attributes.  the initial cap letter preceding the
	colon is the shape of the key:  C for circle, E for ellipse,
	R for rectangle.  this initial letter tells you how to interpret
	the following data, which are floating point and consist of 
	either one f.p. quantity or a comma-sep list of two.  if the
	key is of type C (circular) then one quantity, the radius, is
	provided.  if it is of type E (ellipse) then either one or
	two values are given, these being the X and Y radii.  if only
	one quantity is given then it is the X radius and the Y radius
	is implicitly 1.0.  if the key is of type R then two values
	are given, the X and Y dimensions of the key (or TapArea, to
	be precise).

	the final column is free text, and consists of the official
	key "label" or macro reference, which is mapped by the rest 
	of the TS configuration into a keysym.

TSkeys.ps:

	a PostScript file generated from a Tk canvas drawn from a
	parse of the keyloc.dat file.  this shows you the default
	or platonic TS key coordinate system.  keys are labeled 
	with their text "meaning" where the text is brief, but
	where it's too lengthy they're labelled with their arbitrary
	even-number key ids, which you can look up in keyloc.dat.
	the invisible keys are labelled "I.K." plus their id 
	number.

	I think this ps file will print on tabloid sized paper to
	actual scale, i.e. the centimetre coordinate system will
	be in centimetres on the paper and you can try putting your
	fingers on the paper printout to get a feel for the key
	positions.  but I'm not sure how good the scale is yet.

TSkeys.*.*.*.ps:

	various Postscript files showing the active typing key
	matrix scaled to 90 percent (lineal not areal) w/the 
	scaling and centered on various L/R key pairs.  there is
	hope for the stubby-fingered!

example:

	if you use the little key layout editing gizmo in the 
	FW Gesture Editor, change the position of one key, then
	write an xml config file, you'll find an entry like the
	text in this file.  this is all it takes to relocate a key,
	apparently.  NOTE that the coordinates are absolute, not
	relative!  which is why it's useful to know the default
	absolute positions of all keys.

BlindTypingTest:

	some notes on how to do a blind typing test to see whether
	you make consistent, characteristic key location errors.