Hi Sander: I revisited to just now to see if you had another follow up, only to find that my browser ate my previous response back to you!
To repeat, but in half the text, thank you! Couldn't have asked for a better response. I was under the impression from prior docs that a service was stateless object. The 'providers' docs tell me that each provider is instantiated once, then passed as ref where injected later on. Thus, i created a simple service, and am now able to use my dummy library in my controllers where I inject it as a dependency. You stated that sometimes you'll create a higher scope used by appController. I tried doing this as well, but it raised another Q. If I have nested controller directives like this, I have a case where the child controller processes some data, then I want to shove it back up explicitly into appControllers scope. For instance, I do some simple validation on a <select> (i.e. not null) and if it it passes, want to bind that value to appController's scope. Right now I just did $scope.$parent.value = newValue to assign it to appController's scope. Is there a less scary way to do this? I'd be in big trouble if template changes to add/remove layers of nesting! Thanks again! I'm off runnin! -- 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.
