Creating a Router for neo

Let me explain the current logic first. main.DomEvents will forward hash-change events to the app worker: https://github.com/neomjs/neo/blob/dev/src/main/DomEvents.mjs#L497

worker.App will push the new values into util.HashHistory: https://github.com/neomjs/neo/blob/dev/src/worker/App.mjs#L277

This Singleton will store the last x hash values inside a stack: https://github.com/neomjs/neo/blob/dev/src/util/HashHistory.mjs

Now every controller (including view controllers) will subscribe to the HashHistory change event: https://github.com/neomjs/neo/blob/dev/src/controller/Base.mjs

As a result, developers need to override onHashChange() inside their controllers and act accordingly to modify their views as needed. This can be cumbersome.

It would be nice, if controller.Base would provide a routes_ config, where you can directly specify handlers. This should include variables (could be wrapped inside {}), so we need a bit of regex parsing.

Example how it could be:

routes: {
    '/home'                         : 'handleHomeRoute',
    '/users/{userId}'               : 'handleUserRoute',
    '/users/{userId}/posts/{postId}': 'handlePostRoute',
    'default'                       : 'handleOtherRoutes'
}

The route callback handlers should receive params for the new & old route, as well as used ids inside the route definitions.

Since controller.Base does nothing else except for working with hash related changes, I would drop the logic in there. An alternative would be to extend the class => controller.Router. In this case controller.Component (view controller) would need to extend the router.