feat: orient each gauge like the gesture that drives it - #103
Merged
Merged
Conversation
The y-axis was driven by an up/down swipe and drawn as a horizontal row, so it had no spatial relationship to the thing that moved it — you had to decode which row belonged to which direction. It now stands as a column beside the deck, and the x-axis stays a row above it. The compass reads at a glance rather than being read. Labels on the vertical gauge use writing-mode: vertical-rl. A column of horizontal words would need more width than a 390px screen can spare next to the card. Top is the NEGATIVE pole, because swiping DOWN moves toward the positive one — the label order follows the gesture rather than the convention that up means more. One gauge builder still, not two. Only the orientation differs, so the two cannot drift apart. Two things this exposed: - paintGauges queried els.gauges only. With the y gauge moved out of that container it would have silently stopped painting, leaving the vertical mark frozen at its starting point while its axis moved — a gauge lying about position. It queries both now, and a guard pins that. - The mark only transitioned `left`, so the vertical mark would have jumped rather than slid. Now both. The controller tests hand-copied the page markup into a fixture, and every one of them failed the moment the DOM changed — for reasons that had nothing to do with the controller. They now read public/drift/index.html off disk, so they exercise the page that actually ships and a markup change that breaks the controller fails in the suite rather than in production. typecheck clean; 770 tests passing, 0 failing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
dewpt | 14db490 | Aug 29 2026, 02:28 AM |
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 y-axis was driven by an up/down swipe and drawn as a horizontal row — no spatial relationship to the thing that moved it, so you had to decode which row belonged to which direction.
It now stands as a column beside the deck; the x-axis stays a row above it. The compass reads at a glance rather than being read.
Labels use
writing-mode: vertical-rl— a column of horizontal words needs more width than a 390px screen can spare next to the card. Top is the negative pole, because swiping down moves toward the positive one: the label order follows the gesture, not the convention that up means more.One gauge builder still, not two. Only the orientation differs, so they can't drift apart.
Two things this exposed
paintGaugesqueriedels.gaugesonly. With the y gauge moved out of that container it would have silently stopped painting — the vertical mark frozen at its start while its axis moved, a gauge lying about position. It queries both now, and a guard pins it.left, so the vertical mark would have jumped rather than slid.The controller fixture was a hand-copy
Every controller test failed the moment the DOM changed, for reasons unrelated to the controller. They now read
public/drift/index.htmloff disk, so they exercise the page that ships and a markup change that breaks the controller fails in the suite rather than in production.🤖 Generated with Claude Code