Plover must take arguments in its command line. It's very frustrating not to be able to enter "eclipse 0416ap.ecl -mz_edit" or something like that and have the program open up the file of my choice, applying the settings of my choice, all in one step. Instead I have to open Eclipse, then select the user settings I want, and then open the file manually from the menu. Frequently the last-used file in a particular user folder isn't even on my most recent files list, since all my students' classes are aggregated together.

Yet another Eclipse bug:



I suppose it's conceivable that this one might be attributed to human error, though if it is, I need to find what the error is so I can never make it again. Am I inadvertently turning stitching on? What the hell's going on? It's happened twice, and as far as I can tell all I've done to cause it is use the "?" key (set to "Find above - RT" in Hyperkeys) to find a word earlier in the document while my steno machine is still realtiming. This is what happens, and the only cure I've found is to stop translation and start another one in a new file. Seriously not cool.

Another baffling Eclipse bug:



The text was intended to be in all caps, but when I started writing, it came out mixed case. So I closed the file and started a new one. Now, going back to the transcript of the original file, I find that it appears to be mixed case initially (top picture), but as soon as I press page down, it transforms into all caps (bottom picture). Page up, and it's mixed case again. What in the flurgh?

A wacky bug in Eclipse:



As far as I can figure out, I defined -FP as {FLUSH}, and so every time I tried to write FPLT and it came out FP (as it often does), instead of a period, I got what appeared to be dead space. The first line is what it looked like on screen; the last line is what I originally intended. But the middle line is what I got when I positioned my cursor after the word "tidbits" and pressed "." to insert a period. Now, how the hell did that happen? And what does it mean for Plover, if anything? Something to consider. I've now defined -FP as {.}, so here's hoping that'll solve the problem.

It's ridiculous that Eclipse prevents multiple occurrences, and that I'm not able to have different user settings apply to different opened files. So I'm unable to set Eclipse running, start a job with the user settings of the student's next class, and then open another file up with another student's settings so that I can get some transcript editing done without having to worry that the class will start and catch me unprepared to start writing immediately.

I NEED A QUARANTINE FUNCTION, ARRGH!

Could I write a plug-in module as a sort of precursor to Plover, to plug into Eclipse? I might try. It's maddening not having one.

It's all getting more complicated. But, to be fair, more interesting. Back when I've got actual content.

Proper toggle; going to to gonna after the fact.

Have I mentioned Eclipse's jumping bug? I may have. I don't remember. For some reason, it clears the screen whenever a) you're writing in the lower half of the screen, b) you just changed speaker attributions, and c) the first thing the new speaker says starts with a number. Bloody, bloody annoying. And what on earth could be causing it?

So as soon as I got to the beginning of the flow control section of Learning Python, I was all "I can do this! Just let me start writing some code already." And of course now I've got all my elements in place but I'm driving myself nuts trying to work out the flow control, which is not cooperating. Should I give up and go back to the book? But this brick wall is so cuddly on my brainpan!

*BONK* *BONK* *BONK*

Using Python in Vim. I've been using IDLE so far, just because it's simple and familiar, but when I get around to it I'll definitely tweak my vimrc to turn on syntax highlighting when I'm editing .py files and all that.

The due date for ISWC papers is the 21st. I was considering hacking together a purely conceptual paper to send to them, but I think it'll have a lot more weight if I wait a year and can incorporate some actual demos of Plover in (fingers crossed) action. I wonder how rapidly cheap programmable touchscreen technology will develop. I'd love to think that my retractable gauntlet idea is not so very far away. I just checked back to this thread and realized I never actually described my brilliant gauntlet idea. How could this be? It's much better than gloves or bicep keyboards or hoody-belly keyboards with dangling hoody hood screen (adorably monkish as that might be). The gauntlets are just sheaths for flexible touchpads with tactile feedback that extend outwards when unlatched (preferably by means of some cool-looking gesture) to just beneath the the fingers in their relaxed state. A slight convex bend might be nice. I wish I could draw; it's very simple and elegant as I imagine it. You do your data entry and then stow the touchpads back into the gauntlets until needed. They don't get in the way of anything, and should be light enough that you barely notice them while stowed. Man, I want a pair of these things so bad.

I've determined the first task Plover needs to fulfill.

Given a dictionary with four entries, {KA-T: cat, HR-OG: log, KA-T HR-OG: catalogue, HR-OG KA-T: Log Cat}, produce the following input/output results:

>>> KA-T
cat
>>> HR-OG
catalogue
>>> KA-T
catalogue cat
>>> HR-OG
catalogue catalogue
>>> HR-OG
catalogue catalogue log
>>> KA-T
catalogue catalogue Log Cat
>>> HR-OG
catalogue catalogue Log Cat log

(Log Cat is Log)