We use the Fullcalendar time grid view in week-mode for the week view. It also supports a day-mode which we could use and would reduce the code we have to maintain quite a bit, because it’d be a simple switch of the calendar mode.
One thing I have to note though is that the current view allows users to easily interact with slots that are very short (<15 minutes). This might be a feature of the current implementation that would be missed. We could increase the minimum event height for the day view, but this would be contrary to what I’ve done in #151 (closed).
If we only want to display the (unused) time between timeslots, another solution might be to simply add a little hint in that regard. Something like this maybe?
@kmohrf : After talking with the ProKos about the calendar day view, here is some more precise info on its usecase:
The week view is commonly used by ProKos to get an overview over the full program and plan the (re-)scheduling of shows. To check on details regarding shorter slots and seeing if a slot is scheduled for "live" or "preproduced" content, the day view will be used. Since they have to check on a lot of shows, functionality and clarity of information is generally preferred by ProKos over a detailed visual rendering of the calendar.
Reviewing the proposed grid solution against your last suggestion, I would suggest to implement your last suggestion with a division bar marking the empty timeslots between shows - if possible, the description on the division bar should show the free time (e.g. 11.30-13.30h) rather than "two hours between shows", since the time would give the ProKo a more precise info to use in case they want to fill up that empty slot. In the end, since the program will be mostly filled up with also music pools, there will be not so many empty slots in any case. Rendering the grid would take space while reducing some functionality.