The Rails app front-end that we develop on at UserTesting is not your typical setup. When first created, it utilized BackboneJS (and still does), but not in its true sense. BackboneJS was there for use of its inheritance of the DOM and how it makes working with objects a breeze. Where BackboneJS shines is with single page apps, but unfortunately on our site, we do not have any application currently for single page functionality.
So where does AngularJS fit in?
Skip ahead about two years and AngularJS hits the scene and gains popularity. We start to see its benefits, again outside of the single page application, and decide to bake it into our app with any new features. BackboneJS is still there and plays nicely with AngularJS on an as needed basis.
So what about this compiling stuff?
Like mentioned above, a lot of our app comprises BackboneJS views that render handlebar templates on the fly. Recently, I ran into a feature we were building where I wanted to render an AngularJS directive inside a dynamic handlebars template. Since AngularJS has already bootstrapped before the template is loaded — which is from a click event from a user, the directive never gets initialized.
Below is the coffeescript class for brevity purposes.
Our AngularJS app is bootstrapped on the
body element of the DOM, hence why we are calling out the element injector there. Also, we use
$rootScope here to compile against because we are grabbing the injector from our main app. This script could easily be changed up to allow for other angular elements to compile scope against instead of the full app, but at this time, it is not needed.
Next, take your element, throw it through the compiler and AngularJS will do the rest.
All your directive events, scope, etc. will now be bound and functional!