docs: re-cut the TUI GIF so you can actually read it - #108
Open
DLANSAMA wants to merge 1 commit into
Open
Conversation
The first cut was recorded in a 31-row window sized for the prepare screen, so the dashboard floated in a third of the frame with two thirds dead space, and the whole thing was unreadable. Re-recorded at 1200x570 — about 103x24. 24 rows is the TUI's supported minimum, which makes it both the honest framing and the tightest one that still fits everything, and the holds are longer (12 s on the dashboard, 9 s on the monitor) so the screens can be read rather than glimpsed. The dashboard's 10 s refresh timer now ticks on camera: progress moves 69% -> 71% mid-shot, which is the point of a live view and something a static frame cannot show. Recorded against the same real print: nozzle 219.97 -> 220C, bed 60 -> 60C, layer 115/240, and the monitor's "nothing here can stop it" line. Frames extracted and read again for this cut — no IP, serial, access code or home path. Sizing is now documented in the tape, including the failure on either side: at 17 rows the dashboard's progress bar scrolls out of frame, and a much taller window is what made the first cut unreadable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The GIF that landed in #107 was unreadable. This replaces it.
What was wrong
I recorded it in a 31-row window sized for the prepare screen, then used it for the dashboard. Result: content in the top third, two thirds dead space, screens teleporting past before you could read them.
What changed
Re-recorded at 1200x570 — about 103x24. 24 rows is the TUI's supported minimum, which makes it simultaneously the honest framing (it is what a user on a standard terminal sees) and the tightest one that still fits everything.
Holds are longer: 12 s on the dashboard, 9 s on the monitor. That matters for more than reading time — the dashboard's 10 s refresh timer now ticks on camera, so progress moves 69% → 71% mid-shot. A live view that never visibly updates is indistinguishable from a screenshot.
Scope trimmed to the dashboard and job monitor. The README section this sits under is "Watch the printer while it works"; the prepare screen was a third subject competing for the same frame.
Sizing is now documented, with the failure on both sides
vhs
Width/Heightare pixels, not cells, which is the trap underneath all of this. The tape header now records the working range and what breaks outside it:Still the same real print
Nozzle 219.97 → 220°C, bed 60 → 60°C, layer 115/240, and the monitor's honest "the print keeps going; nothing here can stop it". Frames extracted and read again for this cut — no IP, serial, access code, or home path, and the shell prompt is bare.
No code or docs prose changes;
README.mdalready points atdocs/tui.gif, so the file swap is the whole change.