Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics

pulled from upstream
Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics

pulled from upstream
Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics

pulled from upstream
wrote statement of need
Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics

pulled from upstream
Restructured DataList and its pagination. #130

- Moved the DataListView into the AppView.
- Changed the app.handlebars so that the AppView is a single view
  (instead of being split up into three sections (header, list of
  datum, pagination footer). Put these three things into
  data_list.handlebars instead
- CorpusView no longer cares about Datums or DataList
- DataList no longer needs a Datums, instead it is going to keep an
  array of Datum IDs.
- DatumsView is no longer being used, so I removed most of its contents
- Started adding the pagination logic to DataListView.js
- Removed pagination from Datums.js
Removed unnecessary parts of the pagination footer template. #130
Put the pagination footer in its own <div>. #130

This lets me replace it every time it needs updating.
Added Datum fields to the datum_latex templates just to make sure that the Datum is really there.
Reformatted. No code changes.
Removed a bunch of unnecessary pagination stuff. addOne() works. renderUpdatedPagination works. #130
renderNewModel works for the DataListView. #130

- Factored out the pagination information calculations
- Added real DatumIds to the default DataList in AppView.js
- Took out the pagination partial. Instead I'm just going to call
  renderNewModel() which will append to the data_list_footer div
Implemented the Next button on the paginator #130.

Removed currentPage from DataListView because I can calculate it based
on the length of datumLatexViews.
Now able to change the number of items on a page #130.

Current implementation does not make any changes to the View when the
number of items per page is changed; not even to update the number of
pages. Instead, the pagaination footer is updated with the rest of it
when the Next button is pressed.

This was done to prevent the Next button from disappearing if the user
increased the page size such that it is on the last page, but not all
the items that should be on its last page have been rendered yet.

For example:
datumsId has 5 ids.
perPage starts out at 3. Since there are 3 DatumLatexViews, it calculates
it's on page 1 of 2; therefore, the Next button is visible.
Increase perPage to 9. Since there are 3 DatumLatexViews, it calculates
it's on page 1 of 1; therefore, the Next button is invisible and there
is no way to display the last two datumIds.
Bug fix: CorpusView wasn't being rendered.

Had to change the way Authentication, Corpus, Search were rendered.
Because $(this.el) was undefined in render(). I guess the DOM wasn't
finished loaded.
added doc/Primer
Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics

Conflicts:
	docs/Primer.tex

pulled from upstream
edited Statement of need, goals and objectives, evaluation
Merge branch 'master' of github.com:mecathcart/Drag-and-Drop-FieldLinguistics
My attempt at nesting views.

Events are not being handled by anyone.