The last release was in may 2004.



Go get it before I change my mind.

The last keyboard I bought was a last-minute purchase, almost entirely at random. The keyboard that I really had my eyes on at the time was the Belkin
MediaPilot, which seems a rather transparent competitive answer to the DiNovo. Wandering through Microcenter this weekend, I saw a copy; and since I was still well within the "no questions asked" return period with my Eclipse, I purchased one to see how it would stack up.

See the "mood" header to see how it did.

Cons

The MediaPilot is a mediocre execution of a really great idea. On the surface this keyboard looks great: slimline form-factor; integrated pointing device; a few extended function keys without going insane; detachable "small" wireless keyboard while still providing full 104-key functionality when docked; dock to avoid batteries running out on you at an awkward moment.

Much as the Eclipse was a terrific keyboard that didn't look terribly good at first blush, this is a keyboard that looks terrific but somehow just doesn't measure up.

First of all, the key switches are absolutely the lowest quality that you can buy anywhere. Straight out of the box, this keyboard has keys that stick or randomly get double-typed. The keyboard actually shipped with the "0" key on the numeric keypad detached; I fixed it myself. The keyboard's plastic is so chintzy that it deformed before I opened the box; this means that when it's in "docked" mode, the keyboard has a tendency to rock diagonally, slightly.

While they haven't committed any unforgivable sins, there are still some serious problems with the layout of this keyboard. The right-most row of keys on the mini-board, for convenience, I suppose, is "Home, PgUp, PgDn, End, Right". This means that if I feel my way along the right edge of the keyboard to hit a key such as backslash or enter, I am always over one key too far. Because these keys are already provided on the mini-board, the dock-board provides "Insert/Sleep/ScrollLock/Delete/PrintScreen/PauseBreak" in the space where the 6-key set of Insert/Home/PgUp/Delete/End/PgDn is normally located,

Pros

It's not all bad, though. It is a slimline keyboard, it is relatively comfortable to type on; the wireless portion of the keyboard is extremely light and easy to toss around; the integrated pointing device also contains an integrated scroll wheel which is really handy. Pretty much all of the extended function keys work with Linux (although some only show up in 'showkey' and not in 'xev', so there are a few which would be impossible to bind to an X event out of the box).

Also, the "universal remote" functionality is very very cool if this is going to be hooked up to a computer hooked to a television set.

Conclusion

If I were going to buy a keyboard for a computer attached to a really nice plasma television, where I would frequently want to grab the keyboard and sit back on the couch to watch movies on it, but would sometimes want to sit closer-up to work on code, this keyboard would be ideal. In such a situation its sins would be forgivable and its features would be fantastic. However, in a normal office environment its warts are horrible and the fact that part of it is detachable does almost no good; in trying to experiment with different positions I could type with it in, I discovered that a major reason I like a wireless keyboard in an office is to move the keyboard aside to clear the desk real estate for some other activity, and the MediaPilot's wireless feature doesn't help with this at all.

I gave this keyboard a last chance by typing up this review on it, but my conclusion stands: as it is, though, I'll be returning this keyboard and sticking with the Saitek Eclipse.

... and I checked, I am not legally liable for this because it did not occur within the United States, even if it escalates Twisted to the literal status of a global cult:



His name is Ido Stepniewski, born 30 June 2005

Congratulations, and thank you for honoring the whole Twisted project by decorating your new child thusly.

(I just have to say it: doesn't this remind anyone of a certain comic?)

So I mentioned typing at 140 words per minute in my keyboard post; this is apparently a pretty surprising speed. I am not the fastest typist I know; I do know there are people out there who can do 200+WPM on a good day, with 0 errors.

However, in my case, I'm talking about raw speed, errors and all, and I can't always get 140; if I'm typing at a comfortable pace it's a lot closer to 100. However, I figured I'd hop into gtypist to just provide some documentary evidence that 140(raw) is not such an insane number:



I still practice typing on a regular basis. Mainly I'm focused on reducing my error rate right now.

This is not a tutorial for using wacom devices, just a fix for a particular problem. Maybe somebody else will run with it; the problem is now resolved to my satisfaction. It has only been tested on Ubuntu version 5.04.

I'm not liable for what you do with it. In fact, don't use it. It will harm you.

"Note that if I can get you to 'su and say' something just by asking, you have a very serious security problem on your system and you should look into it."
    - Paul Vixie, in the vixie-cron 3.0.1 installation notes

Any USB Wacom tablet owners out there running Linux? If you are, you're probably frustrated that plugging in any new devices will destabilize your tablet's event device location and make it impossible to reboot without editing your XF86Config-4/xorg.conf upon every boot.

Run this as part of your boot process, before X starts.

#!/usr/bin/python2.4

import os

def findtablet():
    data = file('/proc/bus/input/devices').read().split("\n\n")

    for d in data:
        if 'Wacom' in d:
            lines = d.split("\n")
            for line in lines:
                pdata = line.split('Handlers=')
                if len(pdata) == 2:
                    for pdev in pdata[1].split():
                        if pdev.startswith('event'):
                            return '/dev/input/'+pdev


device = findtablet()
os.symlink(device, '/dev/wacom')
print 'Tablet present at /dev/wacom =>', device

Then, rather than guessing at what event device the gizmo should be every time, just put something like this into your xorg.conf

Section "InputDevice"
        Identifier "stylus" # Wacom Graphics Tablet
        Driver "wacom"
        Option "Type" "stylus"
        Option "Device" "/dev/wacom"
EndSection