Hi Derek, That goes indeed right into the intention of isolate scopes. Exposing the controller, and build an API for your widgets is one way to go. However, you can expose the isolate scope through your controller, but beware of your foot, as this is a big gun directly aimed at it. But how about a service that holds the shared data for every widget? its easy to generate an unique widget-id that you can use to 'target' the right widget, and this also opens up a way to communicate between widgets.
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.
