Alex.
don'tSince I did look into all the issues before that are mentioned in this thread, let me respond to them.
The applications of dynamic keycaps are pretty broad. To people on this
list the need to remember different keyboard layouts, dead-keys, compose
sequences, level and group shifts, are a daily necessity and could be
greatly simplified. The counter-argument is often that touch-typists
look at the keys anyway, which is under closer examination actually notused
true. Even a proficient touch-typist will have to find less frequently
key combinations and often will end up writing a key sequence cheat sheetlike
or mark up keycaps. The benefit for learning a new keyboard layout or for
accessing rarely used characters is obvious. I very occasionally would
to be able to access Cyrillic or Greek characters, yet have to relearnthe
layout or use an on-screen display to find them every time.it.
Another application I was eluding to was what I termed modal (or complex)
input environments. What I mean by that is that despite the efforts of
human interface researchers, many computer programs constantly shift
between different input modes and key sequences change meaning based on
For UNIX users, VI and Emacs are a painfully obvious example. But evenless
extreme cases come to mind. When hitting the ALT key in Windows, themenus
of your window become accessible through keyboard shortcuts. If the 'F'key
would then read "File" or maybe 'F4' would read "Quit", shortcuts wouldbe
more easily learned and user efficiency would go up. If you remember thethat
WPS word-processing keyboards DEC used to ship or the lay-on templates
came with every copy of Wordstar, the utility of this too should belabeled
obvious. After all, there is a reason why we have some keys already
'Home' or 'Backspace'.is
The issues of implementation technology, cost and price came up. I talked
to the eInk folks a while back and while their technology looks like it
going into the right direction, matrix addressable eInk isn't quite thereone.
yet. LCD, OLED, and related technologies seem more practical, but power
consumption would be a problem. In a first generation product a separate
power supply could be acceptable, but most users would not want to deal
with it. Cost is uncertain and will be necessarily much higher than for a
regular keyboard. Off-setting the initial R&D through the price of the
product seems like a bad idea since that would increase the price
differential even more. The corollary being that a large company has a
better chance of manufacturing such a device successfully than a small
In terms of price, I have talked to numerous people and the generaland
consensus seems to be that people would expect to pay more that US$100
less than US$1,000. The cost savings are hard to quantify, but in thecase
topic,of a multi-national IT manager, not having to stock different devices for different locales, does introduce a tangible saving.
While I am happy to have an opportunity to share my thoughts on this
I am not sure how appropriate further discussion on the Unicode listwould
be. If anybody who reads this is in a position to more seriously investigate this topic, please contact me directly since it is an area in which I am greatly interested.
Alex.