tmeasday/meteor-router — pull request #3 by thiagofelix (2012-09-19 20:15:09+00:00)
Title: Simplifying the routes configuration with a automatic callback

Hello Tom

First of all congratulation for all your effort and participation on meteor community, im trying to follow the meteor development, and yours posts and smart packages gave some insights about how meteour works.

Theses PR is just a little purpose of change in the way we have to declare the routes.
What i did was eliminate the callback function that update the current_page variable on the Router every time a route is matched by the Backbone.history.

I think that callback will always do the same thing for all routes, i mean change the current_page on the Router to point on the associated template.

I change the Router to automatically change the current_page to the router's name, i assume the route's configuration will point to a valid template name.

I also create a 'start' method on the Router, this way we dont need to know that the Beckbone.history is working behind the scenes, i think this should make the api more cohesive