You could isolate your main app in different smaller apps, and give them a smaller scope to run a $digest(). I know it would be a huge refactoring, but maybe it's a solution. I'm trying to do the same on some experiments here to see if it works well. I just don't know yet how you could make a channel to communicate between these blocks without using hacky solutions. Maybe a service-level channel via localStorage or something that mimics a socket.
To use resources shared between multiple micro-apps, you could brake apart your app into tiny modules with only the stuff at service level, as if they were just 3rd party libs, then put them into micro-apps' dependencies. These apps would be just a union of smaller modules and some controllers to run the features. I don't know if it's a nice way to use AngularJS anyway. I'm hoping the guys from Angular team show up to clarify that for us :) -- 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.
