Separate global status and global announce in UI

[peteritism]

Having one input for text is limiting to what can be done, especially with the 'announce' functionality. 'Announce' is difficult to use because the current UI configuration doesn't properly allow for message queueing as originally intended. 'Announce' also needs to work very quickly (e.g., after a goal scored), and the current UI is to clunky to allow it. Future templates may also allow both a 'status' and an 'announce' to be displayed simultaneously.

On the 'announce' side of things, I propose creating a front end queue on top of the back end 'announce' queue that would allow the user to organize a series of announcements, then send them to be displayed, rather than the current race to type in the next announcement before the current announcement fades away. This opens up the UI to better feedback as to which announce status is currently up, repeating announcements, and pausing announcements among other potential improvements.

[asquared]

The use case I originally imagined for the announce queue was a "goal announce" or "penalty announce" dialog. This would have auto-completing input boxes for players and automatically construct a set of announcements for an event. The manual entry was meant as a fallback until that functionality was fully implemented - which never happened. I'm starting to think maybe it makes sense to package up that data as a json object and let the template decide how it is presented. That way, a template could easily implement things like dropdowns under a team for goal or penalty announcements.