This is probably not the answer you are looking for, but from my w / AngularJS experience, it seems that you are looking in an anti-angular anti-template. In particular, angular is large in scope - therefore, the controller and view will only “know” about their things. Any other controllers / views on one page or other windows, etc. They will not necessarily refer to each other. Rather, the application on the page will have $ rootScope, which can serve as the w / $ emit () message bus, on $ ().
So, perhaps look at it as loosely coupled parts with a centralized message bus that determines which windows receive which events. Then each part (application / controller / view) simply responds to these events.
Note. We had a test application that simulated several UIWebViews in a mobile application, placing each angular application in iFrames and successfully using this approach. Very sophisticated, very verifiable. NTN
Mark nadig
source share