It's easy to embed Angular components in a non-angular page unless the framework is something that constantly rewrites the DOM from javascript like Extjs or React. You can see an example in my LeanPub book here: https://leanpub.com/web-component-development-with-angularjs/read#leanpub-auto-salvaging-legacy-applications-with-angularjs-ui-components
Client-side routing is a global window/application function because it messes with the window.location object. So if Angular is not the controlling framework in the page, it should not be doing any routing, period. For any component to be handling page or application level functions outside it's boundaries (hierarchy level in the DOM) is a bad practice and bad architecture. On Wednesday, August 21, 2013 7:29:44 AM UTC-7, James Cook wrote: > > I have a need to embed AngularJS components (think of a Discus comment > system) into existing web pages. These components will use controllers, > directives and service factories, but the entire page will not be an > AngularJS app. I don't want to embed these compoennts using an IFrame, I > want to attach them to existing DOM elements on the page. > > My concern is how does Angular deal with routing in such a configuration? > Are there any examples or docs (or anything at all) that you can point me > to in order to understand how to handle transitions in my component that I > would normally handle using URL routing? > -- 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.
