use ruby 1.9 hash syntax in examples
clarify installation of pre version
Merge pull request #50 from meleyal/patch-3

use ruby 1.9 hash syntax in examples
Merge pull request #51 from meleyal/patch-4

clarify installation of pre version
lazy load the view helper in a rails tie
Merge pull request #74 from sjltaylor/lazy-load-view-helper

Lazy load the React Rails view helper in a railstie
[#75] Fix a timing bug with poltergeist/turbolinks

There's a timing bug in ViewHelperTest that randomly results in
```ReferenceError: Turbolinks Not Found```. This causes unrelated builds
to fail, which gums up the whole open source works.

Per https://github.com/teampoltergeist/poltergeist#timing-problems, the
suggested way of fixing this is to just add calls to sleep.

If you wish to test this in the future, use the shell code:

```for i in `seq 1 10`; do rake appraisal; done```

This should give you enough test runs to hit the timing bug at least
once.
Fix asset reloading in development mode

The renderer was using a memoized class variable to cache the
concatinated react.js and components.js for server-side rendering. This
meant that when you updated a component, the server-rendered version would
not be refreshed.

Since #setup! is called every time a watched file is updated, it seems
like the natural place to reset the memozied string.
Kludge to fix Tubrolinks intermittent test errors

Sometimes Turbolinks hasn't fully loaded before Capybara attempts to
call 'Turbolinks.visit'. Adding a brief sleep gives Turbolinks a chance
to become availabe to PhantomJS
Fixes a gnarly test bug with server side rendering

Background: Running tests multiple times in a row could result in
errors, and could result in complete passing. In other words, the order
the tests ran in determined whether or not the tests would pass.

Ruby Test::Unit uses a psuedorandom seed to randomize the
order that tests are run in; you can specify a certain seed with
TESTOPS="--seed=xyz", which fixes the seed and thus the order the tests
will be run in.

The main source of the bug was that many of the tests rely on replacing
asset files and asserting that the results are as expected; however, the
asset pipeline uses mtime to determine when files have been changed.

*mtime's resolution is only 1 second, meaning that when a series of
actions took less than a second to run, the mtime wouldn't actually
change, and Rails asset pipeline wouldn't update the file list.*

This commit adds a hook to force reset the internal concatinated
react.js and components.js string. Another test requires a few calls to
sleep(1), because it is specifically testing that the asset pipeline
picks up changes to the file on disk correctly and renders them server
side.
Can't reliably reproduce this bug

Since I can't reliably reproduce the ```Turbolinks Not Found``` error,
this code is basically just hopeful thinking.
Revert "Can't reliably reproduce this bug"

This reverts commit 55d2a1d6aaffeb5f796989382a6ec7e825737436.
Heisenbug: http://en.wikipedia.org/wiki/Heisenbug

Really just trying to work around an incredibly annoying bug that only
seems to crop up once in a while.
Merge conflicts resolved
Merge pull request #59 from xionon/master

Fix server-side rendering in development mode
Update code comment referencing manifest location

Should the file locations be under the /javascripts folder?
Merge pull request #81 from hackjoy/patch-1

Update references for location of javscript assets
Merge remote-tracking branch 'upstream/master' into generators