raphael/calendarwatch_frontend
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
596f690cce
calendarwatch_frontend/template/sidebar.html

44 lines
915 B
HTML
Raw Normal View History

adds template structure
2020-04-10 11:53:25 +02:00
<!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">
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
<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>
adds template structure
2020-04-10 11:53:25 +02:00
<title>Index</title>
</head>
<body>
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
adds template structure
2020-04-10 11:53:25 +02:00
<!-- 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">
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
adds template structure
2020-04-10 11:53:25 +02:00
{% block body %}
// content here
{% endblock %}
</div>
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
adds template structure
2020-04-10 11:53:25 +02:00
</body>
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
adds template structure
2020-04-10 11:53:25 +02:00
</html>
Reference in New Issue Copy Permalink