Reverse Feature about backbone.subroute

[geekdave]

@schacki : This looks great! I've been thinking about doing something similar for awhile now.

Generally in my apps, I avoid using the router as the navigation mechanism from within the app. Instead, I use an event-based system for page changes, and then my router listens to those changes and updates the URL accordingly.

The problem with this is that I've been forced to have my router interpret every type of navigation event, and conditionally construct the URL based on hardcoded logic in a nasty if/else block. With your solution, this logic would be much cleaner.

Please submit a pull request and I will accept it. This repo is in dire need of a sample app so that we can test features such as this, but I haven't had time to make one.

Thanks for contributing!

[schacki]

I am happy to send you a pull request, just be aware that it is completely
untested. Not even the syntax is tested, since I only had the chance to
edit the code in the Github edit mode last days.

On Wednesday, August 22, 2012, Dave Cadwallader wrote:

@schacki https://github.com/schacki : This looks great! I've been
thinking about doing something similar for awhile now.

Generally in my apps, I avoid using the router as the navigation mechanism
from within the app. Instead, I use an event-based system for page
changes, and then my router listens to those changes and updates the URL
accordingly.

The problem with this is that I've been forced to have my router interpret
every type of navigation event, and conditionally construct the URL based
on hardcoded logic in a nasty if/else block. With your solution, this logic
would be much cleaner.

Please submit a pull request and I will accept it. This repo is in dire
need of a sample app so that we can test features such as this, but I
haven't had time to make one.

Thanks for contributing!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9#issuecomment-7938996.