OPTI II keyboard layout

[ubermensch]

due to my hatred of the default keyboard layout i was forced to go searching  for an optimized keyboard layout suitable for joystick input and came up with OPTI II from those nice guys over at IBM. ( http://www.almaden.ibm.com/u/zhai/papers/ZhaiHunterSmithHCIGalley.pdf )
try it out, seems to work ok so far. supposedly it's a pretty efficient layout so it should get pretty quick once youget used to it. fits the screen well on my gigabeat f20 using xtal-14 font

qkcgvj?789[]\~QKCGVJ
 sind ,456{}'^ SIND 
wtheam.123<>"@WTHEAM
 uorl !0()/$#% UORL
zbfypx;:*-+=_&ZBFYPX

opti2.kbd.txt attached




[attachment deleted by admin, too old]

[bascule]

Thanks for the link, that is a really interesting document.

Is that a patch? or can I just put it somewhere on the player?

Never mind, I eventually found it...

http://www.rockbox.org/twiki/bin/view/Main/LoadableKeyboardLayouts

However, a further question. Is the following the designed behaviour?:

I'm using an H120 and the vkeyboard is usually in the system font. However, loading this one caused it to change to my selected font, which is bigger and thus it did not fit well and was more awkward to use.

Any way of keeping the system font with a revised .kbd file?

*removes foot from mouth*

EDIT: The wiki page says that the current UI font is used...

[bluebrother]

This might be interesting for quite some users, so why not put it up in the wiki? I'm pretty sure it'll get lost here over time ...

[Yotto]

Done.

If you don't like my choices, feel free to change it, I won't get mad

[bascule]

I'm still finding this function awkward. Using nimbus-12 on an H120, the vkeyboard takes up a huge amount of space and spills onto a second screen because the font is rendered as fixed width, rather than proportional, thus making it display much larger than it needs to be.

It's layout could be adjusted to fit nicely if it displayed as proportional.

This is a shame, because the principle is excellent.

If somebody could point in the right direction (which function) to start with, I would take a look at the code to see how easy it would be to patch...