Admin: a page per playing game with its timeline, and a System page (complete redesign) #161
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The mockup is the Admin redesign canvas: the Playing page for the game being watched, the System page, and the Playing page on a good night and with no stream left. This replaces the nine-section page built in #103 to #110 and #105.
What happens
The owner's words, 2026-11-13: after two redesigns the page is still not intuitive, and "overall it's just noisy and filled with unnecessary nonsense UI elements". His priorities, in order:
Three more rules came out of the mockup rounds:
The idea
The frame. The masthead stays. Under it, a sidebar and one page at a time.
/adminopens the game someone is watching; with none, the Overview. Each page has its own address, so a reload stays on it.A game's page, top to bottom:
The game's name with its state tag. Buttons: Swap, Wrong game, and Stop re-encode only while the stream is re-encoded.
A row of fields: Problem, Sport, On since, Picture, Player, Playback.
Timeline: five rows on one time axis, in the order the video travels. A switch picks the last 10 minutes, the last hour or the whole game.
Each row starts with its name, a state tag and two fields (for example Pace
0.87×and Longest gap22 s).Links: every link of the game with site, stream letter, state tag, last result and when it was checked, and Play on every link that is not playing. Count tags on the heading: links, streams, ready.
Log: the game's events since the tune, as time, event and detail, with the freezes and the filler among them.
Grey means fine. Amber is a cause the app handles. Red is something the viewer saw, or a failure. Blue is what plays now.
System, Overview:
Sites, Log, Settings have no mockup. They follow the same forms:
What goes
The top bar, the collapsed cards, chips, verdict words, countdown rings, the buffer gauge, the waits strip, the Next panel, the standby search's tally, the Your games tabs, the coverage chart, the draggable history window and the settings pane. What they said moves into the fields, the timeline rows and the tables above. The full list of followed games stays on the Games page.
Data it needs
GET /api/channels/{game_id}/lanesanswers a window of it in at most 240 bins, with the counts the fields show.POST /api/channels/{game_id}/playwith the link's address. The standby and the backup are swapped in as they are. Any other link is read and verified first. If it does not play, nothing changes and the answer says why.Done when
/adminopens the watched game, and the Overview when nothing is watched;Merged in #162 (merge commit
b1a17da) and deployed frommainatc926431on 2026-11-14: the app was up on it at 16:40Z. The OpenSpec changeadmin-one-game-pageis archived inc926431.Checked on the live app right after the deploy:
/adminopens the Overview, and the Overview, Sites, Log and Settings pages draw from real data with no console errors.sites.json(48 half hours, 2026 reads), so the Sites history row was full at once./api/events?game=and/api/sites/totalsanswer;/api/channels/{id}/lanesanswers 404 without a channel.Seen on a live game at 16:58Z (Miami vs. Duke, watched in the web player, playing thetvapp.plus, three minutes after its tune):
/adminopened the game's page. The state read Playing and the Problem None.Not pressed on a real channel yet: Swap, Play and Wrong game.