gets angular app, and controller and template binding working
- note: interpolation junk to get around handlebars for the time being
gets default loadout units rendering
Creates Units as an angular service
clarified service and added a comment
loadout_slot.showOverlay conversion to angular

pain points:
- using a directive on a child element to set a binding on a parent
- having to convert scope.$index.toString() to match attribute value 
even if I omit quotations

questions:
- how do i even update model attributes or create a model?
- ng-model is useless except for input, textarea, select
- i want a way to do collection.get(0).set("name", "dave") in angular
Figuring out how to manage changes to a service

pain points: 
- it was totally not obvious that I had to use {{ model.attr }} inside an ng-repeat and I was using {{ attr }} expecting the DOM update to occur.
Defaulted max_stat_points to 11 for the template

Also created a controller function to handle the
display of the stats, which seems clunky.

pain points:
- having to use the unicode character representation of "nbsp;"
- i'm not sure what the Handlebars.SafeString equivalent in Angular is
Refactors rendering of the CharacterSelector to ng

pain points:
- some convenience functions on backbone.collection would be nice, but 
it's not too hard to refactor to the underscore functional style

cool things:
- scoped ng-repeat="(type, group) in unitGroupings", this is pretty neat
- i like having only to look to the controller and service for where the
data comes from
- template is much easier to parse with all the markup in place
- working with JS simple arrays and objects is really nice
upgrades underscore to 1.4.4 for findWhere
Loadout slot assignment when clicking character

pain points:
- not sure if updating a model directly is the "angular" way to do this,
but it was pretty easy
- I can foresee problems managing serialize/deserialize when inflating
loadout units from the base64 encoded path in the url, not sure how to
deal with internal angular model attributes like $$hashKey

positives:
- I really like how simple the domain code is coming, @kbaribeau would
probably like this code a lot better than the backbone codes (i think).

:)
Smoothing out bugs in display of default stats
Wires up the slot ordering arrows to move units

pain points:
- is passing around the indexes ugly?
- having to pass indexes instead of having an abstraction to snag the
index of a unit in Units is kind of ugly… would be nice to have a unique
identifier for a model other than the internal $$hashKey
Reworks basics of showing/hiding stat editor

This is probably not ideal, using a service to manage the app state to 
determine whether the user is editing a unit or not, but I opted for it
over storing a unit.editing flag because I don't want app state to leak
into the models and then have to prune keys if/when saving would happen.

pain points:
- forgetting to uncomment the manual show/hide state management in the
stylesheet; backbone was using this and i thought things was broke for
quite a while before realizing :(
- $rootScope.$broadcast from a service wasn't initially aware, but I 
suppose this is similar to broadcasting events on Backbones global
Backbone.Event bus
- naming: AppStateService? TransitionService? UIControlService? no idea
what to call this thing :P
Added log and alert to $rootScope in app.run, and
logged out the stat for debug purposes.

pain points:
- wasn't initially clear where to add things to $rootScope so they are 
available to all child $scopes, seems app.run is the right spot
- remembering that any ng directives will look first on their $scope and
then on the $rootScope (or any parent $scopes) if the function is not 
defined
Removes unneeded dependencies
Eliminates Backbone, cleans up sugar functions
Adds stat editing with left/right click

pain points:
- having to manually pass the event object to the controller function,
perhaps this is a smell that a directive is more appropriate but it's 
not clear how a directive could solve this
- tried to remove jquery but all my element.bind bindings broke inside 
of directives; it seems like when angular detects jquery is loaded it
just uses it transparently (I'm not sure this is a bad thing, because I
don't want to learn another API, but it seems like I thought I _was_ 
using the angular API for directive element binding when I really wasnt)

cool things:
- learning that scopes inherit prototypically so you don't have to do
lookups on the parent scope, it just happens for you
Cleans up this lib for concat
Stops propagation so editing isn't triggered on move

pain points:
- seems like there's got to be a better way of managing these than 
passing the $event in to the controller function, again directives? not
sure if everything as a directive is just another smell
Comments out Backbone code that I still need to 
port so it doesn't issue a compile error.