| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
A lot of time went by in the `time_f()` function, simplify it by not
using the JavaScript date formatting framework which is way overkill.
|
| |
|
|
|
| |
This makes the sort come out right, and there's no need to create a
bunch of objects we just throw away.
|
| |
|
|
|
|
|
|
|
|
|
| |
Use proper JavaScript Date objects for handling time and date
information.
Pick up the screening date from the starting time if not given
explicitly.
Dynamically set the with of each canvas based on the number of rooms
with screenings for that day.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
use relative links to resources, so we can deploy to sub-url.
explicitly set colours for canvas elements, styling did not work in all
browsers.
also make it white on black.
tighten fonts and make screening titles bigger.
|
| |
|
|
|
|
| |
Also fetch the json directly from a file on the server. Since we don't
really have any functionality in the backend app yet, we can deploy
without it.
|
| | |
|
| |
|
|
|
| |
This makes each screening record self-contained, and the json
payload more consistent with how it semantically fit together.
|
| | |
|
|
|
This also changes the structure of the app quite significantly. Instead
if generating the html for the index, we simply provide a public/index.html
static file instead. For now this seems to make sense, it may not hold in
the long run, but that's for another time to worry about.
|
