cutting the 2014-08-24 release
Rate limit display updates to the command log

Update the command log at most 5 times a second.

The command log internally can be updated very quickly if the connected
machine consumes the commands quickly. If we tried to update the
displayed log that fast, the machine would quickly get bogged down with
rendering and won’t send commands at the rate we need.

This change partially addresses issue #33.
Speed up command queue processing a bit

fix #33

Now that we rate limit updates to the command log UI, we can speed up
command processing without completely hosing lesser machines (I hope).

Note, there may still be issues if a machine is able to processes
commands with an average of less than 10ms (which is insanely fast for
a physical mechanism to move and likely means the commands aren’t
moving it very far).
Use fileSystem API for opening files

For the open file button, use the chrome fileSystem API instead of a
hack using forms. Also getting rid of some old jquery code in favor of
an angularjs way of displaying the file name and modification date.

note: this also fixes a long standing issue where you couldn’t open the
same file again with the open button (because the form field didn’t
change).
cutting the 2014.10.10.0 release