Add develop vtt.js portion of README.
Optimize the processing algorithm for large line values.

In the case where we have a large line integer value we should optimize
the algorithm so that we skip through all the individual 'step moves'.
To do this I've optimized it to calculate the amount it should move to
be just outside the container while preserving the interval of step
that it should be on.
Clean up Box.move function a bit.

Passing in an options object will make us less likely
to make mistakes when passing in parameters and 'toMove'
as a variable name for the amount to move the box is a
more descriptive name then 'val'.
Release v0.11.3
Don't clamp the line setting when it is parsed.
Fix issues with large line integer optimization.

A few things were going wrong:
1. I forgot to turn the test back on.
2. The previous optimization solution worked with most integers, however,
when the integer became to large it messed up due to JavaScripts way
of rounding floating point numbers over 64 bits.

This solution gets around the second issue by optimizing the amount it will
be moved to _before_ we have to do any real math on the line value,
whose value may be over 64 bits. However, we now have to disable the
'large-integer-value' test for another reason, which is known, having to
do with the computed value balancer messing up when the step direction
is flipped.
Release v0.11.4
Handle async code in TestRunner correctly.

This fixes the issues we were having with test print outs and also
not being able to run mocha directly on a directory. There were a
couple of issues:

1. We weren't stopping our calls to the next part of the test when
we failed one part.
2. Asserts in async code in Mocha fail really badly (uncaught assertions)
so instead of asserting fails we report an error to Mocha which fails
the test gracefully.
Use array.reverse() instead of custom reverseAxis function.

This was brought up as a potentially better method in pull
request #307.
Fix issues in line optimization.

I've moved back to the old Box::Move function and instead have put
the line optimization steps before we move the box for the first
time. This makes more sense to me as:

1. We only perform this operatrion once, right before we move the
box for the first time.
2. Putting it in the Box::Move function kind of ruins the abstraction
of it since it has to know that the box is moving in 'steps' and not
at an arbitrary amount to move.
3. It allows us to deal with negative line numbers easily. We optimize
the amount to move before we add the extra lenght/width of the box
to the position for negative line numbers. This was messing up the
previous algorithm since it wasn't taking into account this extra
amount added.

I've also fixed an incorrect comment left over from a previous
commit that was discovered by review happening in Gecko bug 974017.
Release v0.11.5
Use var keyword for _objCreate variable.
Lint all our lib and test files.

It's just easier to do a blanket lint for the lib
directory and it's good to have well formed JS in our
tests too.
Update cue2json.js documentation.

Cue2json.js now uses dev builds instead of dists
to run it.