Hi Derek, The new router works differently from what you are used to. And indeed, it is a wip, and I expect a couple of breaking changes any day now. ng-view will become ng-router-outlet, and a few other housekeeping things. Child-routes do work now, but are indeed a bit troublesome to get right. There are a few bugs in the current available version that cause this. Most of these issues are solved already, just not readily available. The key issue, is that the routing-system, and the way they will interact is very sound, and are truly well-thought. It is written in such a way, it will enable almost every use-case you can come up with. Without needing to to adapt the router.
The word is still out on dynamic routing. There is no technical reason to disallow those. The current incarnation can work fine with dynamic routes. However, currently you can not add those :). The reason being, that routes need to be analyzed statically(for reasons outside the router) We have to see how this will land. The plan (as far as I know it!) is still to have the router available with 1.4 Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
