Created the initial user voting sub-panel that creates a field for the user to enter a number
Adds the controllers for getting, updating and adding an Estimate. An Estimate is a code which has the name of the owner, the vote, the ID of the requirement, the ID of the estimate, and the ID of the owner. The managerLayer also now has a path in there for planningpoker/estimate.
Adds the controllers for getting, updating and adding an Estimate as well as the Estimate, EstimateEntityManager, and EstimateModel classes. An Estimate is a code which has the name of the owner, the vote, the ID of the requirement, the ID of the estimate, and the ID of the owner. The managerLayer also now has a path in there for planningpoker/estimate. Changes from last commit: added the WPI-suite header to the classes
Created separate sub-panels for voting when using a deck or no deck
Merge pull request #88 from TheTeam8s/feature-votingPanel

Feature voting panel
Merge pull request #87 from TheTeam8s/feature-estimateRequirementsControllersandModel

Estimate models and controllers
Merge pull request #89 from TheTeam8s/feature-votingDeckSubPanel

Created separate sub-panels for voting when using a deck or no deck
Modified the Session Detail panel to call the correct Event controller function to vote.
Fixes a line in AddEstimateRequestObserver that was refering to a PlanningPokerSession not an Estimate.
Merge pull request #90 from TheTeam8s/feature-estimateRequirementsControllersandModel

Fixes a line in AddEstimateRequestObserver
Instantiates panel for displaying requirement details
Merge branch 'feature-estimateRequirements' of github.com:TheTeam8s/wpi-suite into feature-estimateRequirements
remove incomplete references to requirement table
ensures that each half of the voting page can't be minimized too much