Except for very, very rare cases or debugging purposes, doing this is just BAD practice (or an indication of BAD application design)! For the very, very rare cases (or debugging), you can do it like this: Access an element that you know is part of the app and wrap it as a jqLite/jQuery element. Get … Read more
I’ve answered this in the past, but it’s good that you’re asking these questions. $rootScope exists, but it can be used for evil Scopes in Angular form a hierarchy, prototypally inheriting from a root scope at the top of the tree. Usually this can be ignored, since most views have a controller, and therefore a … Read more
$rootScope basically functions as an event listener and dispatcher. To answer the question of how it is used, it used in conjunction with rootScope.$on; $rootScope.$broadcast(“hi”); $rootScope.$on(“hi”, function(){ //do something }); However, it is a bad practice to use $rootScope as your own app’s general event service, since you will quickly end up in a situation … Read more
Variables set at the root-scope are available to the controller scope via prototypical inheritance. Here is a modified version of @Nitish’s demo that shows the relationship a bit clearer: http://jsfiddle.net/TmPk5/6/ Notice that the rootScope’s variable is set when the module initializes, and then each of the inherited scope’s get their own copy which can be … Read more