replace should with chai
run tests in browser using karma
Merge pull request #179 from c089/example-tests-in-browser

Run example tests in browser
auto whitespace cleanup
removed global rendr.entryPath

in favor of passing entryPath as a server option.

modelUtils is now an object on App instead of a requireable util.

The viewEngine caches layouts based on entryPath.
Pass entryPath as a server option in the example instead of global rendr.entryPath
Version bump

Need rendr-handlebars to point to the new version of rendr
allow modelUtils to be passed in from the server to the server app instance.

This allows for the author to modify modelUtils at runtime.
Merge pull request #189 from givingstage/remove_global_entry_path

Remove global entry path
allows appData to pass in a rootPath

Backbone.history.start can take a rootPath if you're mounting the backbone app on nested url

http://backbonejs.org/#History-start
Merge pull request #193 from givingstage/mount_rendr_app_under_other_route

allow rendr to be mounted on nested url
Use rendr-handlebars@0.1.0
update versions of rendr modules in examples
ensure '' entryPath for templateAdapter on client

without this when you instantiate your app with an entryPath (as we do in our
unit tests), it will fail client-side because the `clientEntryPath` is only
passed to the ClientRouter, but not to the templateAdapter
Added check to see if local backbone router can handle the route or not.
Merge pull request #196 from c089/ensure-empty-entrypath-for-template-adapter-on-client

ensure empty entryPath for templateAdapter on client
Merge pull request #197 from modalstudios/master

Added check to see if local backbone router can handle the route or not.
The try / catch is making me crazy

if the app_view in my app has an error, rendr quietly falls back to using it's own app_view.  Which is tricky to notice, as rendr's app_view does most of the work already.

But this is only a partial fix.  Getting the customAppView set on the app requires overriding the `initialize` method in the app's app_view, setting the `customAppView`, and then calling ` BaseApp.prototype.initialize.apply(this, arguments);` at the end of it.  I'm not thrilled about that as a solution, so I wanted to check in and get people's thoughts before adding a `preInitialize()` method, or if I'm missing a better way to get this into the base app.
adding a method to app to allow overriding of the app_view class
Merge pull request #195 from bigethan/custom-app-view

The app_view try / catch is making me crazy