Component improvements in event block

[cpvalente]

We are planning some work on restructuring some of the components. Mostly focusing on the usability of the app rather than adding new functionality

I thought it would be good to start a documentation on this, focusing for now on Event block which is next in line in worklist

• Improve time input workflow, lots of good stuff at Improve time input workflow #50 and Entering start and end times mixes 12h and 24h #46
• Show a small progressbar in running event when collapsed
• Add playbutton to event block
• Add skip action Possibility to skip event #172
• Allow more text to be added in notes (note field is text area) ability to enter posts with just a start time #59
• Add a note event: event with a single text field and time without duration. eg: 08:30 mic check.
• Ability to link event times
• Visually diferentiate past and upcoming events Change colour of last event #125

and some aesthetic stuff

• inconsistent border radius, see Selected text boxes changes corner radius #53
• use nore space in event list, see autoscaling of post area a bit weird #57

will also have to match styles to the other blocks, this should be mostly styling, but while we are here

• delay field is maxed at 60, however this correction only happens on submit and not onBlur
• When creating an event with the sortcut Alt+E, the option "Start time is last end" is not respected "Start time is last end" not working with ALT+E #171

Show a small progressbar in running event when collapsed

User request. In half window mode the app shows only the eventlist. Some people like using this and triggering events remotely. It would be nice to have a clearer indication of which component is running and its progress

Add playbutton to event block

User request. It would be nice to be able to trigger an event straight from its definition. I am assuming this is for people who use ontime as a stage timer application rather than a rundown list

Add a note event

User request. One of the oldest things in the list. Some workflows would benefit from having a simpler event type for things without a duration. eg: 08:30 Mic check Michael Fassbender.

Ability to link event times

We are looking at a possible workflow where the time start of an event could be linked to the end of another.
eg; event two would have as start time a link to its previous event and a duration of 30min.
This could significantly complicate the usability and clutter the interface with advanced features if not approached correctly

[xztraz]

add the text "delay" to delay-box. so it says "$$ minutes delay"

[xztraz]

Ability to link times, could in gui be as simple as just having a default end-time as the text "next" or a minus sign or alike. and if pushing it it assumes you want to enter something. no clutter.

[cpvalente]

Closing this as mostly implemented in v2