C version of TypeTime.
Bluntly, you probably don't want to use this. Unless you're averse to .NET or Mono, your best bet is the current TypeTime, written in C# and far more configurable and complete.
This version of the program was my original prototype, issued from a morning shell script that fills in the current date.
It works. It just lacks more than rudimentary bells and whistles and it's little more than a quick hack.
Using TypeTime is straightforward, because there are only two configuration options. To use it directly, run as,
This will only print results to the standard output.
The full invocation looks like this.
./typetime [-f output.csv] [-l length]
The options are:
output.csv>: TypeTime prints the summary to the console, rather than the full log entry, and logs the full results to the specified CSV file. Again, note that TypeTime assumes that the date has been inserted into the file first.
-l: Sets the length of TypeTime's target string.
TypeTime defaults to no log file and a string length of five characters.
The session will look something like the following.
First, after a random delay, TypeTime displays the target string.
kmukt - Repeat!
The user then repeats it.
Finally, assuming the user logs the specifics to a file, the summary report gives a quick idea of how well the user did.
0 errors, 2 seconds
Errors are tallied based on the Levenshtein Distance. Time is rounded to the nearest second.
CSV output (to
stdout if no file is specified, instead of the summary) looks something like the following.
These items are:
Date, not printed by TypeTime.
Delay: The time (in seconds) before displaying the target string.
Length: The length of the target string.
Errors: The number of errors made by the user repeating the string.
Time: The duration (in seconds, down to the microsecond) taken by the user in repeating the string.
Note that, if used, uManage-reports assumes that the date information is presented as year
,day of week.