raphael
596f690cce
- 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.
44 lines
915 B
HTML
44 lines
915 B
HTML
<!DOCTYPE html>
|
|
<html lang="en">
|
|
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
|
<meta http-equiv="X-UA-Compatible" content="ie=edge">
|
|
<link rel="stylesheet" type="text/css" href="/static/css/main.css">
|
|
<script src="static/js/jquery-3.5.0.min.js"></script>
|
|
|
|
<link rel="stylesheet" href="static/css/colorPick.css">
|
|
<!-- OPTIONAL DARK THEME -->
|
|
<link rel="stylesheet" href="static/css/colorPick.dark.theme.css">
|
|
<script src="static/js/colorPick.js"></script>
|
|
|
|
<title>Index</title>
|
|
</head>
|
|
|
|
<body>
|
|
|
|
|
|
<!-- Side navigation -->
|
|
<div class="sidenav">
|
|
<a href="/view">View</a>
|
|
<a href="/calendar">Calendar</a>
|
|
<a href="/account">Account</a>
|
|
<a href="/devices">Devices</a>
|
|
</div>
|
|
|
|
<!-- Page content -->
|
|
<div class="main">
|
|
|
|
{% block body %}
|
|
// content here
|
|
{% endblock %}
|
|
|
|
</div>
|
|
|
|
</body>
|
|
|
|
|
|
|
|
</html>
|