Began the scheduler page

Scheduler.mako now excists and we are able to switch to it from the pattern input age.
Paired by Michael and Richard
Fixed small text div in the pattern input pattern

Paired by Michael and Richard
Added a text telling the user to choose a date and time to go and see their
pattern on the display. Paired by Richard and Michael. (Feature #90)
Datepicker created. Paired by Michael and Richard.

A Datepicker has been put on the scheduling page so that people can choose the date on which they will view their pattern. This has also been made to point to the current date should no date already be saved to the session. The size of the datepicker was also changed so that it fits the style of the page. (Feature #90)
Further work done on the scheduling page. Paired by Geoff and Michael.

All the pieces for the scheduling page are now in place, but don't yet do
anything. (Feature #90)
Small features added to scheduling page. Paired by Michael and Geoff.

Some small textual features were added to the page introduction, and it was
made so that if the user leaves the page and comes back, all of their changed
data is retained. (Feature #90)
Further updates to the scheduler page. Paired by Michael, Richard and Geoff.

Further updates to the page were made so that the user can travel backwards
and forwards in the process with the simple click of a button. (Feature #90)
Grid pattern is retained when going from pattern creation to scheduler. Paired
by Michael and Geoff.

The Grid pattern is now saved to the session across all pages in the pattern
creation process and can be viewed on each of them. Additionally, the grid
itself was locked so that it cannot be edited outside of the pattern creation
page. (Feature #90)
Refactored code. Paired by Michael and Richard.

Refactored javascript code into deeper folders, so they are better sorted.
(Feature #90)
Began writing the event handling for the datepicker. Paired by Richard and
Michael.

Initiated the event handling for the datepicking, that will allow an AJAX
request to the database to pull the available five-minute slots. (Feature #90)
Deleted duplicate setting of the grid pattern

There was a second call to the grid setting function in
the scheduler.mako. This has been fixed.
Paired by Michael and Richard
Added event handlers for both the datepicker and the hour dropdown. Paired by Richard and Michael.

Event handlers for the datepicker and the hour dropdown are in place, meaning we are in position
to pull the available five-minute slots for a given hour on a given day. (Feature #90)
Disabled access to the view_slot when it is empty. Paired by Michael and Richard.

The view slot cannot be accessed while it is empty, so when there are no available slots
in the hour chosen by the user. (Feature #90)
Tests for scheduler.json wip

Paired by Michael and Richard
Tested the scheduler's ability to communicate with the database. Paired by Richard and Michael.

We have finished writing tests for the scheduler, and currently these tests fail because the tested
methods lack implementation. Among these tests however, is a test of whether the scheduler is capable
of properly connecting with the database, and we have discovered it can both push and pull information
with ease. (Feature #90)
Implemented the view without error checking. Paired by Richard and Michael.

The functionality of the view has been implemented but there is not yet any code in place for
checking whether the chosen date is too far in the past or too far in the future. We have switched
to postgreSQL, but it is currently hardcoded completely to Richards machine and that needs to be
fixed. (Feature #90)
Removed postgreSQL mentions

Paired by Michael and Richard
Moved the SQLalchemy calls to the models

This is more OOP
Massively improve the time slot query
Fixed the event handler for hour dropdown in sched

It may have been set to the wrong function *blush*