Call setCurrentPage() in the paginator parse() method
Save and render the result count when it is first created

This fixes the issue where the user would navigate to the query workspace first and then to the results workspace leaving the count empty. The reason for this was that the ResultCount view does not exist when the query workspace is hit so the trigger on change:objectcount event was not received by ResultCount since it didn't exist yet. This handles that case by showing the count when it is created and storing the count when the trigger occurs so any possible navigation path should always show the count now.
Merge pull request #307 from cbmi/issue-304

Call setCurrentPage() in the paginator parse() method
Pass model's objectCount directly in onRender instead of storing locally
Merge pull request #308 from cbmi/issue-306

Save and render the result count when it is first created
Merge branch '2.1' into 2.2