Skip to content

R360: the ease and its switch come out again (#153, #175) - #177

Merged
Devski merged 1 commit into
mainfrom
claude/175-drop-easing
Sep 12, 2026
Merged

R360: the ease and its switch come out again (#153, #175)#177
Devski merged 1 commit into
mainfrom
claude/175-drop-easing

Conversation

@Devski

@Devski Devski commented Sep 12, 2026

Copy link
Copy Markdown
Owner

Dawid's decision of 12.09.2026, the day after it shipped: the product is losing functions rather than gaining them.

Out: the eased travel from #153 and the owner's Motion switch over it. #175, which was to turn that switch into two owner-set amounts, is closed unmerged — none of it ever reached main.

What is left

A release still coasts: a thrown orbit keeps turning and slows to a stop. That is the one curve the arithmetic keeps, and it is not kept for the look of it — constant slowing is where the motion coastAfterDrag measures out actually puts a thing.

A click on the ring, on a marker, or on a cue button travels at one pace from beginning to end, as it did before 11.09.

What that touched

  • orbit.ts: the eased curve and glides() are gone; TravelCurve is steady | slowing. The coast no longer asks the switch for permission — a release coasts unless the pointer was cancelled rather than lifted, or the visitor's system asks for less motion.
  • frame-set-shared.ts: glide is out of the params schema, and out of isDefaultR360Params.
  • r360-params.tsx: the Motion control is gone from the edit form; five parameters again.
  • The dictionaries lose four keys in both languages; schema.ts loses the field from the stored-row type and says five parameters in its comment; the unit tests lose the glide cases; works.spec.ts loses the switch walkthrough.
  • SPEC A13 says five parameters, and says plainly what happened to the sixth and why.

Saved works

A work saved while the switch existed may still carry glide in r360_params. Nothing breaks and nothing needs doing: the params object drops keys it does not know on the way in, so such a work reads as one without a switch — which is what it now is. No migration.

Verified

pnpm check green, pnpm build green, r360.spec.ts + works.spec.ts 20/20 against the test database — including the #153 case that a reduced-motion visitor is not thrown, which is still true and still the coast's own rule.

🤖 Generated with Claude Code

Dawid's decision of 12.09.2026, the day after it shipped: the product is
losing functions rather than gaining them. So the eased travel goes, the
owner's Motion switch goes with it, and #175 — which was to make the ease
two owner-set amounts — is closed unmerged and never reached `main`.

What is left is what a thrown orbit cannot be without: a release still
coasts and slows to a stop. That is the one curve the arithmetic keeps, and
it is not there for the look of it — constant slowing is where the motion
`coastAfterDrag` measures out actually puts a thing.

The coast used to ask the switch for permission. It asks nobody now: a
release coasts unless the pointer was cancelled rather than lifted, or the
visitor's system asks for less motion.

A work saved while the switch existed may still carry `glide` in its
parameters. Nothing breaks: the schema object drops keys it does not know
on the way in, so such a work reads as one without a switch, which is what
it now is. No migration, and none needed.

SPEC A13 says five parameters again, and says what happened to the sixth.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Devski
Devski merged commit 60f41bd into main Sep 12, 2026
7 checks passed
@Devski
Devski deleted the claude/175-drop-easing branch September 12, 2026 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant