calendarwatch_frontend/app.py

# Configuration
from server import app
from backend import routine

routine.start()

if __name__ == "__main__":
    context = ('certificate/xip.io.crt', 'certificate/xip.io.key')#certificate and key files
    app.run('0.0.0.0', 1234, ssl_context=context, debug=True)
added second test login, moved into seperate folder 2020-04-02 14:22:59 +02:00			`# Configuration`
adds more advanced database handling unsing sql alchemy - moves app into package - adds sql alchemy equipment - moves templates into server package - add app.db sqlite file 2020-04-22 22:15:21 +02:00			`from server import app`
adds backend script which can be run as a cronjob every n minutes to generate new json files for google calendars - database updated to save google credentials - database updated to save json calendar information - json still saved as a json file under userinfo/<user.id>/calendarevents.json 2020-04-24 19:54:56 +02:00			`from backend import routine`

			`routine.start()`
adds sending toggle (true, false) information; adds color picker and sending that information back to server - the color picker is from 'colorPick' which makes implementation easy. It's only a .js and a .css file which need to be included and the color-picker is simple enough to handle on the client side. The only main problem with it, is that accessing the 'id' information of the css it was called from is not straightforward - the toggle switch which is just implemented in .css currently has the checklist inverted, works but ugly - The Client sends this information back to the server via a json file, which defines the calendar id and either color or the toggle information. The server currently just prints this information.great stuff. 2020-04-14 22:11:34 +02:00
added second test login, moved into seperate folder 2020-04-02 14:22:59 +02:00			`if __name__ == "__main__":`
restructured website into folders 2020-04-07 18:29:51 +02:00			`context = ('certificate/xip.io.crt', 'certificate/xip.io.key')#certificate and key files`
adds sending toggle (true, false) information; adds color picker and sending that information back to server - the color picker is from 'colorPick' which makes implementation easy. It's only a .js and a .css file which need to be included and the color-picker is simple enough to handle on the client side. The only main problem with it, is that accessing the 'id' information of the css it was called from is not straightforward - the toggle switch which is just implemented in .css currently has the checklist inverted, works but ugly - The Client sends this information back to the server via a json file, which defines the calendar id and either color or the toggle information. The server currently just prints this information.great stuff. 2020-04-14 22:11:34 +02:00			`app.run('0.0.0.0', 1234, ssl_context=context, debug=True)`
added second test login, moved into seperate folder 2020-04-02 14:22:59 +02:00