Moving stuff over

Example page template, react component, split it up and cleaned it up, gulp build working correctly
Moving more stuff over from previous repo.

Added Gulp command for building js and watching
Table displays output now, no styling yet
Removing IIFEs for right now
Reapplying a bunch of styles.  Its actually going to look a little better than before.
Adding pagination and the top filter control.
Adding export controls
Merge branch 'feature/adding-controls-and-more' into develop
Adding demo page to readme
Paginator can change the page of the table now

Example page will refresh the data with a timeout when page is changed to simulate an AJAX request.

It's really fast to refresh.  It's instant after the AJAX is received.  We'll see how it holds up when we've got 20 columns with select boxes, each with 10-20 options.
Hook up the demo page count buttons so the active one is set
Merge branch 'feature/pagination' into develop
Refactoring into the OwlCell React class.
Rows now open input fields when clicked on.  Still text only for now.

Put specific order for the jsx task in gulpfile
Created input reactcomponent
Initial implementation of select boxes

ReactJS + Angular = match made in heaven
Can keep track of changed rows now.  Stub of save button handler.
Adding debounce to the input fields, courtesy of underscore
Do the debounce the right way, it actually works now

Some other cleanup as well
Merge branch 'feature/input-fields' into develop
Save button now posts changed data to the route provided.
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.