Add Sphinx documentation for the Homepage

I added sphinx documentation to the project and documented the homepage
view aspects of the project.
Spellcheck documentation

Updated documentation by using spellcheck.
Move documentation source/ directory to docs/source/

This commit consolidates Sphinx docs resources (specifically source
code) into its own subdirectory to separate documentation code and
feature code. This commit also updates image and code refs to match
new file locations.
Update Sphinx Makefile and make.bat to reflect new documentation resource location

Prior to this commit, Sphinx docs Makefile and make.bat did not point
to the new location of the Sphinx source code resources. This commit
updates makefile references to point to the correct location in the
project file structure.
Add labels to code examples and minor grammar edits

Prior to this commit, readers could not determine where included code
samples came from. This commit adds labels to code segments and makes
a few minor grammar edits.
Merge pull request #4 from osu-cass/maint-3803-edits

Maint 3803 edits
Merge pull request #27 from Free-BSG/feature-3803_HomeScreenDocumentation

Feature 3803 home screen documentation
Add store tests

Add the store tests and implement mocking.
Request code help from Jacob

I am trying to get jasmine testing working for the controller and distance
store, but I am not able to get the exists tests to work.
Work on controller testing and rm unused files

I got rid of some views, stores, and models we no longer need. I also
worked on trying to load the controller.
Fix store tests, add model tests, and clean app.js

I fixed the store tests so that they loaded multiple items, and commented
out the api test untill we implement the api. Also added model tests as
needed. Then cleaned up the app.js fiel so that the app would load
correctly after we got rid of some testing files.
Unhide autoload tests and scrub old comments

Prior to this commit, specs addressing the autoload requirement of
sencha stores were hidden in comments. While we do not want to derail
the test process with unimplemented features, we also do not want to
omit these requirements from the project specifications. This commit
uses Jasmine's "pending" spec feature to disable these autoload tests
and preserve them in the overall spec document.

During the development of this branch, comments describing bugs and
strategies persisted beyond the lifetime of the test code they
described. Since autoload spec was a member of these comments, this
commit also removes these comments from all store spec.js files.
Disable pending listspec.js test suite

Prior to this commit, the controller test suite in the List.js file
was being run despite being incomplete. This commit just disables the
test suite using Jasmine's pending spec feature so that the incomplete
test suite does not interrupt the testing process.
Merge pull request #5 from osu-cass/maint-3812/13-jasmine-practices

Maint 3812/13 jasmine practices
Merge pull request #29 from Free-BSG/feature-3812/13_JasmineTesting

Feature 3812/13 jasmine testing
Work on fixing map

Added map that works when it is the first thing loaded. If the listview is
loaded first the map centers, if the home screen is loaded first, the
center is pushed to the top left corner of the screen.
Fixing map centering on device

I was hindered by the lack of wifi in our work environment. This group of
changes works. I moved the scroll to function into the map view init
function, because otherwise it was not being run when moving between the
home and list screens. This occured, because the gMap value was
instaniated after the panTo function in the controller.
Dynamicly add all of the list items as map markers

I was able to add the list items into the map as specific map markers, by
adding a couple of for loops in the controller that found the lat/long
locations of the list items and set the markers to those coordinates.
Update map markers

I updated the map markers so that they would display an infowindow when
clicked on that shows the store name at that location. I also made it so
that only one infowindow shows at a time. There is also commented out code
in the sass formating folder that we can use to style and change the look
of the infowindows.Also removed the previous search's map markers so that
they didn't persist through different queries.
Add a button to the infowindow that has navigation

I added a button to the info window that lets the user navigate to the
detail page and view the selected vendor's items. I still need to update
the info and header sections of the detail window when navigating there
from a map marker. To do this I will need to set the toolbar in the
controller and set the detail view data to the selected vendors data.