reload for any file change
Merge pull request #9 from fortnightlabs/asset-loading-fix

reload for any file change
update spec runner
reorganized dirs, added dummy project
Re-implemented the Sprockets directive so that it would behave just like jasmine-headless-webkit to avoid config conflicts (which were extraordinarily easy in the past).
Merge branch 'new-dirs'
cowardly bump to 0.1.0
rewriting docs
Was running into problems due to Sprockets caching
assets (as it should), and it turned out to be
because the entire approach of using a directive
wasn't really appropriate. Fixed it by simplifying
and just using a normal include tag.
Fixes #14 as proposed by @rzw:

https://github.com/rwz/jasmine-rails/commit/9c3a229aed572f58c66aa7e8985a0ba813caa065
patch bump
This covers an edge case where the user doesn't
have qt installed (or otherwise has not compiled
it on a first run with jasmine:headless), and
are then greeted on the web with a NoRunnerError.

Well, since we don't need the headless runner to
actually work when we're running specs in the browser,
this hack will just rescue the exception and then
do a head-fake by creating the file that JHW is
actually looking for, instantiate the runner, and
then delete it.

We need an instance of the runner to get at the 
Jasmine config in the same way JHW is.
0.2.2
Updated to latest jasmine-core.
Lots of tweaks in prep for jasmine 1.3 upgrade

- Fixes #21 (thanks for pointing this out)

- Forces /specs to serve up a page with debug_assets
enabled (regardless of the app's config), which
is apparently necessary for it to find the individual
scripts appropriately

- Adds a capybara/rspec test to verify that the dummy
app is working in a browser

- Enforces the lower version of jasmine for folks
not ready for jasmine 1.3.
0.2.3
adding travis
add xfvb
Failed to force jasmine-core <= 1.2.1 previously
0.2.4