some links related to my voice coding talk at #pycon

links.txt

Resources: 
http://code.google.com/p/dragonfly
http://sourceforge.net/projects/natlink/
http://tech.groups.yahoo.com/group/VoiceCoder/

Inspirations:
http://emacs-vr-mode.sourceforge.net/
http://sourceforge.net/projects/voicecode/
and especially http://shorttalk-emacs.sourceforge.net/ShortTalk/index.html from which I've stolen a few key ideas and utterances.

I have been also looking for any updates on the subject, but with no luck :(
I have already installed Dragon and started some experiments with dragonfly, but there are some gaps and holes in the way to have a fully usable system.
It would be amazing to have at least a general guide to shorten the path for others. Something simple (that doesn't take too much Tavis's time) like:

(maybe im a bit lost in some points... thats why im asking for it :S :) )

• install the software

  blablabla

• create your basic vocabulary

  blablabla you might find this issues, blablabla, use shorttalk for this blablabla,

  • knowledge about grammars and contexts in Dragon NS can be found example link
  • quick guide to add custom commands to dragon
  • a recommended way to define the "language" you are going to use with speech recognition
    • shorttalk is good for blabla
    • you wiil need you own words for this blablabla

• configure you usuall applications

  for emacs blablabla, for vim blablabla, for the shell, blablabla

• improve you customizations

  blablabla

it seems that more people is trying to use this also... :)

In this repository you will find all the support files for my "code by voice" setup using Dragon Naturally Speaking and DragonFly. I was inspired to do this by Tavis Rudd

I too was inspired by his talk.

Here is my own progress, and some other links and information in the readme.
https://github.com/synkarius/caster

I've also seen projects inspired by Tavis's talk, and while fresh starts are good for cleaning out the "duct tape," voice coding is an area that would be very good to standardize conventions. Two thousand voice commands sounds about right, but what if each implementation had a different two thousand commands?

Please, at least put your list of commands out there! It should be a selling point that a system is Tavis-compliant. After all, you've used this for years, culling the hard-to-pronounce words, eliminating ambiguities, adding missing commands, and everything.

(Slap.)