Add Rspec save_fixture helper for generating jasmine html fixtures.

The goal of this change is to support automatically generating HTML
fixtures for Jasmine tests when you run your Rspec view tests.
0.4.9
add spec for JasmineRails::SaveFixture#save_fixture method
Merge pull request #90 from wireframe/rspec-save-fixture

Add Rspec save_fixture helper for generating jasmine html fixtures.
0.5.0
Adds tmp_dir() method to get a path out of the config value
Adds tmp_dir in the default config
Makes use of JasmineRails.tmp_dir
Lets peeps know they can configure the tmp directory
Merge pull request #92 from shariffy/tmp-dir-config

Make the tmp dir configurable
0.5.1
add jasmine_rails:install generator to setup Rails project.

Simplify installation steps for new projects to run a Rails generator
to automatically setup project to run the Jasmine testsuite.

example command to run:
```bash
$ rails generate jasmine_rails:install
```
asset_path helper in tests fail due to computed path hardcoded.

The computed offline asset path and by association the jasmine runner
fail because the asset path is hard-coded to /assets rather than using
Rails.configuration.assets.prefix
use phantomjs path if it's not in PATH
Merge pull request #94 from wireframe/generators

add jasmine_rails:install generator to setup Rails project.
Clean the readme a bit
Turns out this was causing a conflict every time

Since jasmine_rails has its own initializer that 
creates the jasmine.yml whether you like it or not,
they need to be identical to avoid every single
install from resulting in a conflict prompt for the
user.

Did you somehow avoid seeing this @wireframe?
0.5.2
killed dead links. Fixes #96
Makes this example look less important

Fixes #97