I've done this recently and it worked out really well. Was in a standard ASP.NET MVC application, but there was a particular component that needed to be built that was really complex and Angular made my life much easier. Still made use of filters / services / controllers / directives - just didn't do anything with the routing module at all.
It will be easier if the entire page is Angular - but if it's a small control within an Angular page, there are ways to get the angular and non-angular portions talking. This stack overflow question<http://stackoverflow.com/questions/10490570/call-angular-js-from-legacy-code> has some information on how to get this wired up. Some people asked why we didn't use knockout or a smaller framework for it (which would work also), but we already have two full-SPA Angular applications in the works, so made sense to stick with it. On Tuesday, March 4, 2014 9:22:55 AM UTC-5, Fhenon De Urioste Mariaca wrote: > > Hello, > > I need to create a very complex widget and I was thinking about using > angular. But I'm not sure if it is a good idea to use angular only for the > widget since I don't need it for the rest of the website. Is angular only > intended to be used only to create SPA? > > > -- 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/groups/opt_out.
