Ok, loading data through ajax and the demo Heroku Laravel machine.

Its still instantaneous after the ajax comes back.

I have some ideas for how to abstract this stuff into the owlTableService.

Next: client side pagination.  If the data is more than the count per page, only show that page's slice of the data.
First working implementation of client side pagination.

Oh man, its fast.  Pulling 1k 50 column objects from the Heroku server is limited by the AJAX request speed.  Pagination is even faster than it was before with creating new random data because there's no $timeout set on it.

And we can still apparently get the changed row information and save it.

Needs refactoring.  Everything pagination related should move into the service.  Its half and half right now.
Fix the styling on the input fields before I forget
Setting table to point to Heroku sample data
Move saving into owlTable service, and rename that service
Merge branch 'feature/get-remote-data-and-client-paginate' into develop