Sunday, March 14, 2010

Why Plover?

I first came up with the idea of learning how to program by writing open source steno software more than three years ago. I've been geeky all my life. I've been an internet addict since I first discovered Gopher and Usenet in '93. As a teenager, I spent my time reading The Jargon File, watching Sneakers, and calling up every BBS in my area code repeatedly and obsessively. I steeped my brain in old-school cyberpunk and thought somehow that coding knowledge would come to me automatically, by osmosis. Never happened. Both my brothers and many of my friends are programmers, but somehow I never wound up actually sitting my butt down and teaching myself how to code. Now I'm pushing 30, making a good living at something I love, but I feel my brain getting slower and less plastic every year, and so at long last I'm taking steps to fix the mistake I made in my youth. I'm learning Python, one hour a week, and in the process I'm making something that might do some good for a fair number of people.

I'm planning a post that'll talk about the various things I think Plover might be good for, but for now I just want to talk briefly about how the project got its name. I remember walking around Fort Tryon Park, trying to think up something snappy, easy on the ears, not too flashy, that actually had something to do with stenography. At first I was fond of Stentor, but it turned out to be taken already. I tried anagrams of "stenotype" and "stenographer" but got only "Testy Peon" and "Nasty Gopher", neither of which inspired me. I thought I'd go to the great natural philosopher Nicolas Steno, but when I proposed naming my program after his Latin name, Stenonis, my better half quite rightly laughed herself senseless.

Finally I decided that, since none of the obvious "This is a program about steno!" names seemed to work, I'd come up with a name wasn't necessarily related to steno, but which could be used to show how insanely cool steno actually was, once you figured out how it worked. I wanted to show the powerful, flexible ambiguity of the keyboard, the way a single chord could translate to "slung" or "shrunk", "apple" or "amp", "squarer" or "sierra", "castle" or "cavil". I wanted to show how a single steno stroke could represent two syllables and half a dozen letters. I also wanted it to sound distinctive and useful, a word that was familiar enough not to sound alien, but not so common that it was mundane.

Finally I hit on it: PHROFR. In most steno dictionaries, the steno outline "PHROFR" is defined as "moreover". PH- is pronounced as "M", and the "R-OFR" bit sounds pretty much the way it looks; put them together and you get mrovr, which is easy enough to parse. But because HR- can also be pronounced as "L", PHROFR is also the way you stroke the word "plover", a charming little wading bird of the subfamily Charadriinae. Court reporters use the word "moreover" a lot more than normal people do, because it's used so often in legal contexts. Since I intended to write the first steno program that almost entirely neglected the very specific needs of court reporters (sorry, guys), I thought that using the zoological rather than the legal reading of the stroke would not be out of place.

Plover is also one of those words that's not pronounced the way it's spelled. It's PLUH-VER rather than PLOE-VER, and the idea of using a non-phonetic word for a phonetically based system amused me. Finally, there's the whole obnoxious Web 2.0 trend of naming programs after random verbs and then adding an -R to the end without an intervening E, and it drives me mad. I figured Plover would be my way of fighting back; it sounded like a helpful utility to use whenever you needed to get some serious plovving done (whatever that might mean) but it was a proper English word, with a proper -ER ending instead of the ubiquitous tacked-on -R.

So... Plover. One stroke, two syllables. Counter-intuitive pronunciation to give the in-crowd a feeling of leetness. Cuddly little bird logo just waiting to be drawn. It might not be hard-bitten and foreboding like what I would have chosen back in the '90s, when I dreamed of being a teenaged gargoyle; but now that I'm grown up and boring, I think it'll do quite nicely.

Tuesday, March 9, 2010

Steno machines on the cheap

I bet you that there's plenty of people who are interested in tripling their typing speed but don't intend to make a career out of it. Steno could be of great benefit to them, but steno machines cost big bucks. Right now you can get ugly, bulky, ancient student machines for about $700 at the cheapest, and they have none of the ergonomic benefits of a machine like a Gemini ($1,000) or a Revolution Grand like I've got ($2,400), or even a Lightspeed ($2,000). Incidentally, did you know that the technology used in the Apple iTouch was purchased from a company that had been using it to make low-cost steno machines? Apple put a stop to that, of course, and we've been waiting for an affordable touch-based machine ever since. Story here and here.

I have high hopes for the MSI computer I posted about below, but the video showed only two channels of multitouch. That might be the case only for the prototype; if it's that way in the final version as well, we'll just have to keep on waiting. Then, of course, there's the question of how the haptics will work even if the multitouch is fully functional. Will they be laggy? Insufficiently well delineated? So well delineated it's impossible to touch two keys with one finger? Who knows? Maybe a keypad overlay system, similar to the LightSpeed's, can work where haptics don't; it's something to consider.

But until our dual-screen fully multitouch magic bullet comes along, what solution is there for people who don't want to drop a minimum of a grand on some bit of tech that they're not sure they'll ever use? There's a cheap ($60) qwerty keyboard from Microsoft that can supposedly recognize up to 26 keypresses at once. How possible would it be to strip the keys off and use the key-recognition circuitry with a new steno-based layout? I know very little about hardware hacking, but my Python tutor has done a fair bit of it, so I intend to bring this up to him once we're a bit further along in Plover's development. My instinct is that it will probably be possible to rig up something that works but that it'll be trickier to come up with something that's both comfortable and reliable. I'm holding out hope for the dual-screen solution because that makes it as easy as pressing a key to switch between qwerty and steno layouts, which seems pedagogically ideal. But if we could really rig up working steno machines out of $60 keyboards plus some minor parts and labor customization -- maybe even make it into a kit for hobbyists to assemble themselves -- it might give people a low-risk incentive to pick one up and play around with it.

Monday, March 8, 2010

Getting there

It's been a very productive few days. We've made it so that any number of asterisk keys are translated as only one asterisk; same thing for initial S- keys. We've made it so that an asterisk pressed by itself will delete the last stroke from the buffer. Finally, I changed stenoworking.py (the version I've been using as a dumb terminal while providing CART for a client using two computers with my Revolution Grand's dual Bluetooth output streams) so that it now displays the entirety of the buffer with each stroke, rather than just the last stroke in the buffer. It might look busier, but it's actually quite useful, because now when I delete misstrokes on the client's display (which is running Eclipse, the $4,000 proprietary steno software) I can confirm that I haven't deleted too few or too many. Here, have a screenshot!

Plover screenshot

Sunday, February 28, 2010

This needs to come out very soon!

Hands-on video with the MSI Haptic Dual-Screen Multitouch Laptop

And it needs to be wildly popular, and I need to have Plover ready by then. Yes? Yes. Here's hoping, on all counts.

Monday, February 22, 2010

Two things

One, Plover now has a Github account: http://github.com/stenoknight/Plover

Two, Plover Software, unaffiliated with the Plover Steno Project, has graciously put a link to this blog on their webpage, so it's only right that I return the favor.

Here's their blurb:

"I’m an independent software developer, working on a variety of projects. Current interests are the Twitter API, and iPhone/iPad software development. I’ve also done a lot with Amazon Web Services. You can also find me on Twitter, at @plover, or reach me via email at john@ploversoftware.com."

Saturday, February 20, 2010

Plover lives!

Well, a lot has happened since August. Starting in November, I've been taking weekly lessons with a Python tutor, and we've been working together developing (to be honest, he's pretty much done the developing, with me looking on trying to understand what's going on, adding occasional steno-specific interjections) our first working version of Plover. And, for a generous definition of "working", we've gotten relatively far!


If you've got a steno machine that uses the Gemini PR protocol (e.g., Gemini2, Gemini Piper, Evolution, Revolution, or Revolution Grand), you can use the two files above to display steno translations in a terminal (I think it should be platform independent since it's just a .py file, though I haven't tested it in anything but Windows XP). Stenoworking is the main file, and ploverbd is a modified version of my personal steno dictionary.

What it does:

* Translates words and phrases of up to 10 strokes in length.
* Displays raw steno when it can't find a translation.
* Updates the 10-stroke buffer so that new longer translations supersede older shorter ones.

What it doesn't do:

* Output to anything other than the terminal.
* Incorporate suffixes, prefixes, or punctuation.
* Delete strokes using the asterisk.
* Treat the double S- as a single S- or any combination of asterisk keys as one asterisk.
* Look very good if you concentrate on anything but the last line of text on the screen.
* Work with anything other than a Gemini PR protocol machine.
* Work with any dictionary other than the one I've turned into ploverbd, which involved stripping out and altering a lot of important entries.

I'm going to keep working on these issues week by week, while learning more about unit testing, version control, text parsing, and all that good stuff. If anyone out there is actually interested in the code and has the ability to play around with it, I'd love to hear from you! Go to my website, StenoKnight.com, and drop me an email. Plover is entirely free and open source, currently being developed by J. Lifton and M. Knight.

More to come!

Saturday, August 15, 2009

The Plover Project is not dead! I'm just taking a bit longer to learn Python than I should. But slowly, slowly, I'm getting there. I just spent a lovely week and a half with my brother, the programming wizard, learning the ins and outs of classes, objects, and Tkinter. When I get back to the city, I'll keep working on my little proto-steno programs, and hopefully by the end of this year I'll have a little more than I had at the end of last year. This stuff is too important to give up on.