Hi Chris, Your lib sounds a lot like a angular service. I think that's the best suited place for it too. Not knowing how you need to instantiate your lib, I can't detail on what provider to use, my initial instinct is yelling angular.provide however ;) With that out of the way, its time to look at your second part of the question. You say you are needing this lib all the time in every part of your app? The easy way out is indeed injecting it into your rootScope. However, I don't like that solution. In every app I create, I create a top-level scope, usually created by an controller aptly named 'appController'. I would put it in there. As all other scopes inherit from this one, you will have your lib available in all controllers. When creating directives or other services that need your lib, you can simply inject it there.
Does this help? need me to go a bit deeper on (some of) this? 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.
