Clyune Component GalleryScroll Timeline · How it works & code
A vertical line spans the page, with each event as a node on the line and a card.
Runtime logic
Visiting `/scroll-fx/timeline`, DemoHost lazy-loads `demos/kits/kit-scroll.js` (registry `mod: 'kit-scroll'`) and calls `mount(host, { variant: 'timeline' })`. mount resolves the variant to family `timeline`; `withControls` builds the control panel (6 presets + sliders). `createCanvasStage` creates the `<canvas>` (HiDPI ≤ 2×, ResizeObserver) and the info panel. The family’s `build(S)` initialises state and returns the per-frame callback. Every `requestAnimationFrame`: read controls, advance a speed-scaled clock (dt ≤ 50 ms), run the frame callback; returned readouts go to the info panel. Changing parameters: colour/speed/size apply live; structural ones remount; leaving the page cancels rAF, removes listeners and frees resources.
Environment
Canvas 2D: 2D canvas drawing; requestAnimationFrame: Display-synced animation loop; ResizeObserver: Canvas follows container size; Pointer Events: Unified mouse/touch/pen events; devicePixelRatio: Crisp HiDPI rendering (capped at 2×) · react 18.3.1, react-router-dom 6.30.6, vite 5.4.21
Dependencies
react 18.3.1
Imported APIs
withControls — Wraps the demo in the shared control panel (presets, sliders, reset); hot-updates or remounts on change; paramsFromSpec — Turns the spec (colour/speed/size/count/extras) into control-panel parameter definitions; createCanvasStage — Shared Canvas 2D stage: canvas + info panel, HiDPI, one rAF loop, pointer state, idle auto-pointer; hueOf — Hue of a colour (0–360°); clamp — Clamps a value to a range; TAU — Constant 2π; fmt — Number formatting (fixed decimals); F — Formula block HTML; S.clear — Clears with the background colour (translucent = trails); S.isAutoDemo — Whether auto demo is on; S.onFrame — Registers a per-frame callback; its return value feeds the info panel; ctx.fillRect() — Fills a rectangle; ctx.fill() — Fills the current path; ctx.beginPath() — Starts a new path; ctx.arc() — Adds a circular arc (center, radius, start/end angle); ctx.stroke() — Strokes the current path; ctx.fillText() — Draws filled text; ctx.moveTo() — Moves the pen without drawing; ctx.arcTo() — Adds an arc using tangent lines; ctx.closePath() — Closes the current sub-path; ctx.save() — Saves the drawing state (transform, styles, clip); ctx.rect() — Adds a rectangle to the path; ctx.clip() — Turns the current path into the clipping region; ctx.translate() — Translates the coordinate system
Source code
frontend/src/demos/kits/kit-scroll.js: FAM.timeline (L439-L456)
Code walkthrough
L439-456: Calls the factory `scFam()` to produce the full definition (spec + doc + build) from the options below. L439-439: Title shown in the info and control panels: “timeline”. L439-439: Range/default of the count slider. L439-439: Extra demo-specific slider/toggle: left-right alternation. L439-439: Range/default of the size slider. L439-439: Default main colour. L440-440: Help text of the count parameter. L440-440: Help text of the extra parameter. L440-440: Help text of the size parameter. L441-441: Preset buttons: name → parameter overrides (4). L442-442: Body of the “Notes” section. L443-443: Main formula of the “Formula” section. L443-443: Second formula line. L444-456: Per-frame draw function: draws with Canvas 2D `fillRect`, `fill`, `beginPath`, `arc`, `stroke`; math via `Math.min`, `Math.abs`; returns readouts `mode`, `cell`, `pageH` to the info panel.
Principles
Filled length = scrollY + 0.6 · High—axis starting point Card progress e = card((fill point - node y) / 80) Time axis: A vertical line runs through the page and each event is a node and a card on the line. When you scroll, the vertical line is 60% from the top of the "long" to the view, the node passing through is lit and the corresponding card slips from the side. The narrow screen is automatically changed to a one-sided layout. Image simulates a scrollable web page: scrollY 表示页面已经向上滚过了多少像素，这里它自动来回滚动（右侧细条就是滚动条）。元素在屏幕上的位置 = Page Location − scrollY；The degree to which the elements enter the vision is usually used scroll Event or event IntersectionObserver Let's figure this out 0~1 The progress is driven by animations such as transparency, offset, scaling, etc.