Thumb Keyboard For PalmPilot
Cpt_Kirks writes "Wired has an article mentioning a new thumb keyboard for the PalmPilot that clips over the graphitti (sp?) area. The site listed is in Japanese, but it appears to just be push buttons that tap the screen. The rest must be done in software. " They claim you can use it as fast as you
can use grafitti, and at only $40 it doesn't seem that expensive.
My awesome x-roommate is native Japanese. I just asked him to translate the specs to me:
- it covers the touch panel part with the keyboard
- it's 60mm X 22mm sheet. the sheet can be put on/taken off without any cable, or somekind of connection. all the typing will be taken are of by the associated software.
- you can have the touch panel on top of the keyboard if you need. (the picture is listed in the wed site. second picture from top.)
- a part of the keyboard is customizable.
- they started shipping in this Oct.
- it does not take extra battery. it's just a sheet sitting on top of the screen.
- it works for WorkPad, WorkPad c3, Palm III, Palm IIIx, Palm IIIe, Palm V for now. not sure if this works for Visor. i don't believe Visor will be out in Japan for a while...
- the current cost is 6800 yen + tax. pretty much $70...
/will
- Sam
The secret to enjoying Slashdot is to realize that it should not be taken too seriously.
That was a joke. Lots of folks fell for it, though.
I haven't checked it out yet, but seeing these posts made me think of it.
- AC
On the surface, this seems like a good idea. But, if you think about it a little more, it's a really really bad idea.
Consider: Your device has a virtual input area. That area could presumably be controlled by the developer of the application you are using. They decide they need a little more screen space, and shrink it down, only, now you can't use your device for input, because you were used to the size and location it was at before. Do you really want to trust a developer with this important function? (face it, someone who knows how to make cool code usually doesn't realize that they don't know anything about interface design)
Ok, make it unchangeable by app developers, and only configurable in a control panel: You make your input area smaller, and the apps aren't written to take advantage of the extra space. Now you have wasted space. Make it bigger, and apps won't fit.
Basically, there is much to be said for having no control over something. If every developer changed your keyboard map to match their prefs, it would be a nightmare. This is a very similar issue.
The only reason I could see in creating a virtual input area is to be able to display information inside of it, like maybe a clock or the date, but, you must keep it the same size. Configurability creates confusion for most users, so you should keep configuration options down to a minimum.