← all recipes

Weak applied

Selection Wake

leave a subtle trail of user interaction and selection

frame bodies 0 relationships 0

Running the actual recipe live via applyRecipe() — not a mock.

"Selection Wake" — leave a subtle trail of user interaction and selection. It has a memory layer (a decaying trail / hysteresis), a diffuse layer (spread a quantity over the medium), a fieldflow layer (solar prominences, aurora, plasma streams, guided matter), and a stream layer (flow matter along a heading). Matter follows the field geometry because of fieldflow, not the field-owning force itself. The active render stack is trails, heatmap, particles.

Memory holds the wake while diffuse lets it fade, and fieldflow carries repeated paths into usage trails — transport that remembers where attention has been.

Runtime tokens
memory diffuse fieldflow stream
Concepts
wake
Metrics
memory recency trail trail is a host-supplied lane — drive it with data-field-<metric> (or a domain model); without that, its --field-* stays inert.
Diagnostics
heatmap contours force-vectors
Conditions
selected
Render
trails · heatmap · particles
Reduced motion
selection-history marks with recent-item badges and a static trail rail
Without motion
a static history rail lists recently touched items with recency badges in place of a fading wake

Copy this recipe

<field-root></field-root>
  <div data-body="memory" data-strength="0.9" data-range="300" data-feedback></div>
  <div data-body="diffuse" data-strength="0.6" data-range="280"></div>
  <div data-body="fieldflow" data-strength="0.6" data-range="0"></div>
  <div data-body="stream" data-strength="0.5" data-range="320" data-angle="0"></div>

See also