Merge branch 'master' into feature/checks
Fix name of getTextCount function
WIP on feature/checks: Get text count for project

Unfortunately, this approach, while straightforward, is too slow:
it ends up making several database round-trips too many, for reasons
that are probably connected to Angular internals. So I'll probably
have to try a different approach.
Revert "Get text count for project"

This reverts commit 68bab5925ebf65466cdfe9d33175e47343968f07.
Merge branch 'feature/questiondto' into feature/checks

I'll need the DTO classes from the questiondto branch in order to
replace the "fake" data with real data from the database.

Conflicts:
	src/angular-app/sfchecks/partials/projects.html
Use real data for getAnswerCount(question)
Use real data for getQuestionCount(text)
Use real data for getTextCount(project)
Consolidate list and dto in sfchecks API

Since the dto functions (on the Javascript side of the interface at
least) were written to be drop-in replacements for the list functions,
we should just use one function, not two -- and call it list, not dto.
Merge branch 'feature/questiondto' into feature/checks

Continue to track the questiondto branch so I can write tests against
the latest changes to, say, the QuestionModel, rather than writing tests
against an older version that will fail as soon as the two branches
are merged.

Conflicts:
	src/angular-app/common/js/services.js
PHP unit tests for new DTO classes
Merge branch 'master' into feature/checks

I'll be merging this branch into master soon, so let's first make sure
that all conflicts have been resolved, by merging master into this branch.
Remove "N views" from projects/texts/questions

Tracking how many times a particular project/text/question has been
viewed turns out not to be necessary here: our users aren't likely
to be interested in that information, and it adds unneeded complexity
to the interface and to the implementation.

"Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away." - Antoine de Saint-Exupéry
Fix Jasmine test

The breadcrumbs controller was moved to the main sfchecks.js file,
and Angular no longer has a module named sfchecks.controllers. Test
has now been updated to ask for the correct module.
Add a Jasmine test for the project (texts) page

More tests are needed, obviously, but this is a good framework to build
them from.
Improve Jasmine test for project page

The test data should go *inside* the function, not as global variables.
Otherwise when a second test is created, its copies of testData and
any other global variables may shadow these, leading to either this
test or the other one failing because the test data isn't what was
expected by that particular test. If the test data is *inside* the
test function, though, it will be scope-limited, and two variables with
the name testData can't shadow each other.
Add Jasmine tests for projects & questions pages

I'm sure plenty more tests could be written, but now we at least have
a test that exercises the query() function for each of the three
controllers. A good start.
Merge branch 'feature/checks'