Using prototype methods so public methods don't get reinitialized every time.
Fixed #326; Travis CI integration added

.travis.yml is currently set up to track all branches. We may restrict
this in the future.

The build status image has also been added to README.md
Fixes #363, allow displayName to be empty string

When the columnDef displayName property was an empty string, the column
class was defaulting to using the field name in the header template. Now
it will allow an empty string and will only use the field name if
displayName is undefined.
Fixes #366, column enableCellEdit overrides config

If a column has enableCellEdit set, it will now override the default grid
config enableCellEdit setting.

Added browserTrigger.js for triggering events while testing. This is the
tool angular uses for its internal tests

Added test spec for enableCellEdit. Had to use jasmine's async helpers to
get around a setTimeout in the ng-cell-has-focus directive.
Fixing testing on travis

There is now a grunt task 'test-ci' that will build from source prior to
running the karma:ci task. I have updated the README.md to reflect this as
well
Fixes #332, #369. Watchable totalServerItems

Thanks to @keithharvery for the PR. The `totalServerItems` grid option can
once again be set to a string, which will be watched by the grid and
reflected in the footer if updated.

Also added tests to directivesSpec.js for using a normal number and using
a string.
Adding basic test specs for i18n
Adding pt-br.js (Brazilian Portugeuse) to i18n

Fixes #371

Thanks to @dipold for the translations and pull request.
allow optional '+' prefix to trigger numerical sort
Fixes #394, Array.forEach() assumed to exist

IE8 doesn't support the Array prototype's forEach() method, and I used it
in grid.initTemplates(). I've fixed this to use angular.forEach() instead
and added a test to catch calls in initTemplates() to
Array.prototype.forEach()
added some tests for "optional '+' prefix to trigger numerical sort" feature
Merge branch 'allow_plus_for_numeric_sort' of https://github.com/a5sk4s/ng-grid into a5sk4s-allow_plus_for_numeric_sort
Reverting build/ng-grid.debug.js to 2.0.6's version
Fixes #399, making cell editing work again

This is an issue with how src/ng-input.js is handling the value of the ng-input directive. The current default template contains an $eval, which means that when ng-input.js runs a $parse on it, it gets the evaluated value of the cell itself. For a string, (which is an object) this ends up not actually modifying the cell contents but at least it doesn't fire an exception. For an integer primitive you would end up with an undefined setter and a noop getter, which would throw exceptions when you try to use undefined as a function to set the cell value.

The fix, as I see it, is to use a regex to strip out the $eval statement from the ng-input in the editable cell template.

I've also cleaned up ng-input.js, added some comments, and added handling
for when the enter key is used to modify a cell's contents
Adding a test for editing complex properties

Making sure that editing of columns bound to multilevel objects, like
'person.demographics.name' works as expected
Fix wysiwyg-export plugin.

Add jasmine specs for plugins.
Fix plugin initialization when passing in function literal..
In order for "getInstanceType" to work correctly, function literal must
be declared in form "function SomeClass () {}".
Change "export" to "exportData" because of IE8

IE8 thinks export is a reserved word even for identiferName
Adding sublime text ignores
Merge branch '2.0.6' of https://github.com/angular-ui/ng-grid into 2.0.6
Compile CSS from less files.

Using grunt-contrib-less task