Update menuTemplate.html searchPlaceholder so that it binds to the correct model
All column headers were receiving the ngSorted style. This is because existing code only tests for the existence of a noSortVisible function. we should be executing the function.
Modified code to allow for sub objects to export in csv
PDF Plugin, uses https://github.com/MrRio/jsPDF
Update grid template / compiling to work with the latest version of angular
Closes #869
fixes #614
Fix for: Sorting when external sorting is enabled is broken

Provides fix for the following condition:
When external sorting is enabled, attempting to sort via multiple
columns is futile because as soon as you click the column, all of the
sorting turns off.  The problem is related NG-Grid improperly handling
an unexpected DOM event.
Fix for: Sorting when external sorting is enabled is broken

Provides fix for the following condition:
When external sorting is enabled, attempting to sort via multiple
columns is futile because as soon as you click the column, all of the
sorting turns off.  The problem is related NG-Grid improperly handling
an unexpected DOM event.  Behavior is unmodified if no externalsorting
is false.
Phantom calls Array.prototype.forEach

So the build fails. I guess we should just ensure than angular.forEach is called since angular.forEach will handle the presence/absence of Array.prototype.forEach 

It's weird that this is passing in the main branch and failing in 2.0.8 (newer version of Angular? Something we did?) I just want to get 2.0.8 sorted, so here it is.
bumping version number to match the fork

-- added shane and myself to the team
Fix searches of dates that have filters applied to them
Fix null reference exception if missing opts
Ignore unnecessary files in bower
Update ngtemplates module and settings to fix template prefixes
Create nl.js

translation for Dutch usage
Avoid various memory leaks
- Removing window resize handlers on destruction
- Stop watching from parent scope on destroy so we can hopefully let go of the grid
- Added cleanup to avoid leaking grid through additions to the options object

Conflicts:
	src/directives/ng-grid.js
Add $destroy events handlers to elements

Add a handler for Angular's $destroy event to any element where we're
binding event handlers. This should help with memory leaks.
Try to unhook event listeners and watchers on element and scope destroy events. Also remove elements from DOM that are manually added on  destroy
Fixed memory leak. Had to manually remove references to DOM elements in grid instance