ngXenophilous

A collection of functions which make Angular a little less of a pain to work with from jQuery or common JavaScript.

These functions are designed to be as stand-alone as possible and complement Angular without being too confusing.

var app = angular.module('app', []);

app.controller('widgetController', function($scope) {
	$scope.widgets = [];
});


// Now for some jQuery:

$(function() {
	$.getJSON('http://somewebsite.com/api/json', function(data) {

		// Use ngApply() to run code or manipulate variables as if we were inside the Angular environment

		ngApply('widgetController', function($scope) {
			$scope.widgets = data;
		});
	});
});

Installation

Install with bower:

bower install ng-xenophilous

And insert the script loader into your header file:

<script src="/bower_components/ng-xenophilous/ngXenophilous.js"></script>

NOTE: Due to the complex nature of actually finding the Angular controllers this module has a dependency on jQuery.

FAQ

• Why this module - Because I was having problems getting Angular to work with jQuery or any other JavaScript library without a load of faff.
• Why the stupid name - The internet informs me that Xenophilous is the opposite of Xenophobic (self contained). Which is certainly the attitude we are trying to foster here.
• How do you recommend using this module - Really this is just an add-on to Angular which enables it to work a bit better with external libraries. Use Angular for the majority of your coding and the functions provided by ngXenophilous for small jobs. I would certainly not recommend writing anything more than single liners - move your complex stuff to an Angular controller.
• Arn't all of the methods outlined here bad practice - Yes and no. Angular recommends dropping jQuery entirely in its documentation - while this is a nice idea in a perfect world a lot of us still have legacy applications or JavaScript components that are not directly Angular compatible. This module attempts to cater for these without breaking the Angular framework too badly.
• Can't I just use angular.element($('#userCtrl')).scope() to find the scope of an object - Certainly! Unfortunately Angular has lots of weird behaviours such as ensuring your within an $apply container and checking we are not already in a $digest phase before we can even begin. This module works around all these difficulties and provides a clean a way as possible to address Angular without having to deal with these problems every time.
• I know of a better way of finding Angular controllers without using jQuery selectors - Yey! Please contact the author so he can update this module.

Features

ngApply(controllerName, function)

Run a function as if we were executing inside a controller.

This function will find the controller by its name and execute code within its local scope.

Example:

ngApply('userController', function($scope) {
	$scope.user.name = 'John Smith';
	$scope.user.message = 'Buwhahaha';
});

ngBroadcast(eventName, parameters...)

Broadcast an event downwards though all controllers.

This is functionally identical to $rootScope.$broadcast() except that its called externally from Angular.

Example:

ngBroadcast('myCustomEvent', 'foo', 'bar', 'baz');

Utility functions

The following functions are also provided but they are not really intended to be called directly. They are provided here in case you ever really want access to Angular controllers and so on but its recommended you use the above wrapper functions when manipulating things.

ngGetScope(controllerName)

Retrieve the scope of a named controller. This is really just a utility function which gets used by the other functions to properly look up the controller. Its not a good idea to use this directly as updates to the object wont be detected by Angular. See ngApply() for the recommended way to execute Angular scope-aware code.

Example:

var widgetScope = ngGetScope('widgetController');

ngGetRootScope()

Similar to ngGetScope() but this time returns the Angular $rootScope object.

Example:

var rootScope = ngGetRootScope();

ngRegister(controllerName, controllerObject)

ngXenophilous generally does a reasonable job of finding the relevant Angular controller by their given names but if you are doing something strange you can force a controller to resolve to the correct object by registering it with ngRegister(name, object)

Example:

app.controller('widgetController', function($scope) {
	ngRegister('widgetController', this);
	// ... Lots of code .. //
});