Give the pulse its own duration, and let the editor fill the screen

The shared duration tokens had been stretched to slow the pulses down, which
also slowed every panel and dock animation and left `motion.ts` out of step
with the CSS. Both are back to 200/300 ms, and the pulses use a new
`--duration-pulse` (500 ms): a message arriving is a signal, not a state
change, and it is the only thing here that should linger. The edge pulse read
its own 300 ms constant, so it now takes the token through `motion.ts` and the
two sides cannot drift again.

The code editor also expands: the same node panel fills the content region
beside the sidebar, the canvas chrome steps aside rather than floating on top,
and the settings above the editor keep a readable width.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WzrvW7rjQbynnhF6pxh6i
This commit is contained in:
Melvin Strobl
2026-08-15 20:03:21 +02:00
co-authored by Claude Fable 5
parent f05831b4a5
commit aa0e760615
8 changed files with 95 additions and 34 deletions
+5 -4
View File
@@ -8,10 +8,11 @@ Deferring because out of scope is fine, but don't mention deferring than.
## Open
- BUG/UI: the CSS duration tokens were retuned to 250/500 ms but `lib/motion.ts` still
carries 200/300, so JS animations (panels, dock, tabs) run at a different speed to CSS
transitions. They are meant to mirror each other; pick the intended values and update
`motion.ts` in both repos.
- BUG/UI: the sidebar background on dark mode does not match the background of the viewport/flow panel
- BUG/UI: there is some strage dot (li item) sitting next to the appearance button
- FEAT/UI: introduce User settings page showing up in the sidebar where the apperance, email password etc can be set (copy UX design from ../../n3xd/app)
- BUG/UI: edge value labels should be opaque
- BUG/UI: the popover which opens when clicking on an edge should be more compact, i.e. make label, value and last updated fit in a single row (truncate decimals)
- BUG/API: `pytest tests/` deletes every user on teardown (`tests/conftest.py`), so running
it against the development database logs you out of the running app. Point tests at their
own database, or reseed with `init_db` afterwards.