Temporarily use fork of jasmine-rails, which fixes cache issues
don't rotate the framerate :P
don't alter banner since framerate works now :P
prettification
translate to coffee
rewrite Jax.Shader.Program: now much smarter, with much better tests

New implementation is smarter about attribute enabling/disabling, and
also is smart about attribute location binding. Previous implementation
did no attribute binding, and consequently disabled attribute 0 in some
circumstances. New implementation should rarely, if ever, disable
attribute 0, and try to re-bind attribute locations if attribute 0 becomes
disabled. New implementation also fixes a bug where attributes that were
used by shader, but not given values by material, could be left enabled,
causing INVALID_OPERATION errors during rendering. New implementation
is also faster to the tune of 3-4 FPS on my machine.

Win win win!
fix specs to work with changes in Jax.Shader.Program API
remove useless `pass is 0` test since that arg is not used any more

also remove warnings about variables with no values. In practice this
is a false positive far too often.
useProgram optimization
{mat,vec,quat}.equalish
Jax.Mesh#toJSON() for easy serialization

Pro Tip: load your model (e.g. an OBJ file) via one of the loaders,
then call `toJSON()` on it to bake tangents, bitangents, and normals!
Store that off into a file somewhere and then load the baked data instead
of wasting time recalculating them!

Win!
translate to coffee
allow `parser` as an option to avoid an XHR when data is already known
Monkey!

Seriously, because I can.
added an OBJ format loader
update with changes from recent commits
how long has this been failing?

Must have been a caching issue: I never saw any test failures until
today...
include color data
stop ignoring Gemfile.lock

Some people don't like checking in Gemfile.lock, but I do.
I think it's important for people who clone the repo to be
able to use a known good configuration, and choose what to
update from there.
use jasmine-rails master until its next release; and update to rails 3.2.13

the pull request was merged to jasmine-rails AND rails 3.2.13 breaks
the previous jasmine-rails repo; bugs have already been fixed in master
so that is where we wait until the next release of jasmine-rails. At that
time it'll finally be safe to go back to using the released gem again.