updated for blaze layouts

I used 'region' instead of 'yield' since you define it now with the region variable.
Fix this.redirect in RouteController...

- Closes Issue #469.
- We now give the user a warning if they call stop() in a RouteController
  function during a run. This is because it is unlikely the user wants to stop
  the entire controller from running. They just want to pause downstream
  functions from running (e.g. before/action/after) if some condition is not
  true in the current computation's run. But when you redirect you *really* do
  want to stop the controller.
- Solution: The Router can call a "private" function to stop the previous
  controller from the run method of the router.
- Test it out.
Fix standard hooks...

You no longer get these hooks for free. You need to ask for them. You can pass a
string name for the hook. For example:

// run the loading hook for all routes as a before hook
Router.before('loading');

// run the notFound hook for all routes as a before hook
Router.before('notFound');

Remember that the order of hooks matters. In this example, you want the notFound
hook to come last since we want to show a loading indicator until the controller
is ready. The notFound hook checks whether the data value is falsy and if so,
renders the notFound template. But we don't want to do that until the data is
actually ready!
Fix up the data API on RouteController and fixes...

This makes the `this.data()` and this.data({title: 'example'})` api more
consistent and predictable. When you define a controller or route you can
provide a data property like this:

data: function () {
 return Items.findOne({_id: this.params._id})
}

Now, you can call this.data({...}) to set the data value at a later time, or
this.data() to get the value from inside one of your controller functions.
Minor cleanup on pr/474.
Merge branch 'pr/474' into blaze-integration
If controller stopped, don't run hooks or action.

- Issue #475
- The runHooks and _run methods need to check whether the controller is in a
  stopped state so that if you redirect, the previous controllers functions
  don't continue to execute for the first time.
Merge remote-tracking branch 'origin/blaze-integration' into new-location

Conflicts:
	lib/client/router.js