- the icalHandler in the backend is used in two instances. First, when
the user adds a new ical calendar into the database, routes.py passes
the information (name and url) to the ical Handler. The calendars are
saved in the database as type 'ical'.
Then, when a connected device pulls current events, all the calendars
which are of type 'ical' are pulled and parsed for current events.
See the backend commit for details on what happens there.
- All google Calendar related functions now have an additional check,
to make sure that the calendar they are working on is of type 'Google'.
- landing page shows two images of google calendar and tizen watch
and how the calendars corelate
- routes redesigned to fit this landing page
- redesign of coloring in css
- fingerprint generated first time device connects
- saved to database and served to device
- connection status set to true, once device requests first package
- user can link device via online form
- form added to push new device id to backend
- device added to db model (needs to be pushed still)
- form return right now just prints
- design for device list created, still needs some updates
- using flask-wtf forms to create login and registration
- saves and compares input data with database
- generates user if need-be
- same user form as google user
