Modify isNavigating that is always looking at child router's isNavigating property

This would fix cases where main router did not report that only the child router isNavigating
Merge pull request #211 from dotnetwise/patch-2

Modify isNavigating that is always looking at child router's isNavigatin...
Some minor tweaks in the router.

Making router.navigate pass history.navigate's return value though.
Making not found routes work a bit better.

Merged in some changes from the original backbone source that inspired
this router. One of the fixes helped improve missing route support.
Making multi-arg logging appear more naturally.

Fix courtesy of @dotnetwise.
Various fixes to platform support.

Removing old build events, improving shim config, updating nuget content
and removing old code.
Minor update to the readme file.
First take at mimosa starter kit for 2.0

-css combining is leaving out some files. not sure why
-need to find out how to tell mimosa to specificly include certain
modules when it creates the optimized build. it cannot detect plugins
and any modules configured only via the router
Added Bower source.
A bit of reorg for bower consistency.
Stubbed out the yeoman generator.
Adding headers to the css files.
Changed the folder for yeoman under source.
Configuring JSDoc
Starting to apply jsdoc tags to the activator module.
Updated jsdoc npm modules.
Switched over to yui for documentation.
Proving out yuidoc by documenting the activator module.
Removed the old optimizer.

It has been replaced by Weyland.
Added router:route:activating event.

-This event allows custom logic to gain access to the module instance
and route instruction prior to activation.
-Renamed event router:navigatedFrom to router:navigated:from
-Renamed event router:navigatedTo to router:navigated:to