We don't have a component for that, but given that one of our main audiences is on-device applications where the URL isn't visible to the user (think PhoneGap or webOS), this wasn't super important.
We do have some apps that do their own routing. Look at the code for gallery (https://github.com/enyojs/gallery) and api-tool (https://github.com/enyojs/api-tool). We're also adding routing to the sampler app, and that may result in some core framework support for this method.
As for other state handling -- we've been working on documenting best practices on using Enyo with Backbone, with Enyo handing views, and Backbone handling state management and syncing.
We do have some apps that do their own routing. Look at the code for gallery (https://github.com/enyojs/gallery) and api-tool (https://github.com/enyojs/api-tool). We're also adding routing to the sampler app, and that may result in some core framework support for this method.
As for other state handling -- we've been working on documenting best practices on using Enyo with Backbone, with Enyo handing views, and Backbone handling state management and syncing.