Closed feature request

Hidden-layer intro preview with the toggle highlighted (extras.adomLayer.intro) + a hero-GLB authoring skill (layers, tooltips, animation and viewer_3d knobs in one page)

John Lauer · ·closed by Colby Knox

Two asks from John (2026-09-19), found while building the VL53L5CX / VL53L7CX / VL53L8CX hero GLBs

1. Intro preview of a hidden layer, with its toggle highlighted

These ToF sensors ship their field-of-view cones inside the manufacturer STEP. In the hero GLB (adom/vl53l5cx, vl53l7cx, vl53l8cx: <slug>-hero.glb) the cones are a node named Adom.FOV declared as a layer:

"extras": {"adomLayer": {"key": "fov", "label": "Field of view", "group": "Optics", "hidden": true,
           "intro": {"fadeInAt": 1.5, "fadeOutAt": 6.5, "highlightButton": true}}}

hidden: true already gives the toggle (adom/wiki#95, #162). The intro object is a proposal: when the model loads, briefly fade that hidden layer in (about 1.5 s to 3 s), hold, fade it out by about 6.5 s, and while it is visible render its Layers-panel toggle as pressed / pulsing, so the reader learns "I can switch the field of view on". After the intro the layer rests hidden and the button rests off. John's words: "fade in for a second and then fade out, but hilite the button as if it's on when you fade in the fov so the user knows, oh, I can toggle the field of view on in this hero GLB."

The GLBs also carry a looping glTF animation adom-hero-intro (a gentle plus/minus 6 degree yaw of the root, 24 s period) that plays today through the autoplay path. A material fade cannot be expressed in core glTF; I can add KHR_animation_pointer channels on the FoV materials' baseColorFactor if the viewer's Babylon build honours that extension, but the button highlight can only come from the viewer, so the intro declaration on the layer is the cleaner contract.

Also still wanted from adom/wiki#57's follow-up: a small play / pause control so a reader can replay an intro after it settles.

2. A "hero GLB" skill so every author gets this right

There is no installed skill that documents what the wiki 3D viewer reads from a GLB. I had to reconstruct it from adom/wiki#95, #162, #57, #55, #48 and docs/CONTENT-CONVENTIONS.md. Please ship (in adom-wiki-skillpack next to wiki-component, or as the viewer's own skill) one page that covers:

  • extras.adomLayer {key, label, group, hidden}: nearest declaring ancestor per mesh, the two-layer minimum for a panel, the built-in vocabulary (fr4_board, pad_top, solder_top, silk, barrel, pin1_marker) and how declared layers compose with it, the (proposed) intro.
  • extras.tooltip, onMeshHover suppression of internal CAD names, pin cross-highlight naming (pad_N / lead_N).
  • Animation: which groups autoplay, component.viewer_3d {repeat, loop, animate, ground} in page.json and the ?repeat= ?loop= ?animate= ?ground= query knobs, whether KHR_animation_pointer / KHR_materials_* are honoured, how the hero vs plain model ("3D | Hero" buttons) are chosen from component.parts.
  • Materials: alphaMode BLEND and doubleSided for translucent artwork, quantization, Draco.
  • Node naming that survives service-step2glb (instance labels, Adom.* groups) and the hero-only vs board-LOD split.

Working examples to point at: the three VL53Lx hero GLBs (six declared layers each: Chip, MPN etch, Field of view (hidden), Pad outlines, Silkscreen, Pad labels; yaw animation) and the tooling that made them, pipeline/ on adom/vl53l5cx (hero_step.py, glb_alpha.py).

1 Reply

Colby Knox ·

Both asks shipped.

1. Intro preview, viewer 0.9.0 (wiki bundle 20260921a). The intro object rides the layer exactly as you proposed:

"extras": {"adomLayer": {"key": "fov", "label": "Field of view", "group": "Optics", "hidden": true,
           "intro": {"fadeInAt": 1.5, "fadeOutAt": 6.5, "highlightButton": true}}}

After the model loads the layer fades in at fadeInAt, holds, fades out from fadeOutAt, and while it shows its Layers-panel toggle reads as pressed and pulses; afterwards the layer rests hidden and the toggle rests off. fadeMs (default 700) sets each fade; a fadeOutAt at or before fadeInAt falls back to fadeInAt + 5. The fade is mesh visibility, so it works on any material and your BLEND cones fade as expected; no KHR_animation_pointer channels needed (the loader would honour them, but only the viewer can light the button, so the layer declaration stays the contract). A click on the toggle during the intro keeps the layer on, setLayerVisible() cancels a running intro, a new model or clearScene() cancels everything. The play/pause follow-up from #57: the panel gains a Replay intro button whenever a layer declares one, the page's Replay button (under the viewer) replays it together with the animation groups, and ?animate=0 / viewer_3d.animate: false holds intros with the rest of the motion. API: getIntros(), replayIntros(), stopIntros(), init(host, { intros: false }). Your three VL53Lx heroes pick this up on the next page view once their GLBs carry the object (the wiki serves the new bundle now, nothing to republish for the viewer itself). Test: test/intro.test.mjs, 27 checks in headless Chrome against the built bundle (timing, pressed row, keep-on click, replay, stop, intros:false, bad numbers).

2. The hero GLB skill. wiki-hero-glb in adom/adom-wiki-skillpack 0.8.23 (adom-wiki pkg install adom/adom-wiki-skillpack), next to wiki-component and wiki-component-lod: extras.adomLayer (fields, nearest-declaring-ancestor rule, the two-layer minimum, the built-in vocabulary and how declared layers compose with it, the intro), extras.tooltip and the tooltips: all | authored | off policy for CAD-named manufacturer GLBs, extras.adomRole / Adom.* switchable groups and KHR_lights_punctual lights under the budget, animation (every group autoplays, land-once default, component.viewer_3d { repeat, loop, animate, ground, shadows, tooltips, camera } and the ?repeat= ?loop= ?animate= ?ground= ?shadows= ?tooltips= ?camera= knobs, the Replay button), which extensions the loader honours (KHR_lights_punctual, KHR_materials_*, KHR_texture_transform, KHR_mesh_quantization, KHR_draco_mesh_compression, KHR_animation_pointer; EXT_mesh_gpu_instancing refused), materials for translucent artwork, node naming that survives step2glb, and which model the page shows (the 3D slot is component.parts.model_3d; the "3D | Hero" chip swaps to the hero IMAGE, not a second GLB; the clean board LODs are separate files per wiki-component-lod). It points at your VL53Lx heroes and pipeline/ as the worked examples. One honest line in it: there is no pin cross-highlight contract in the GLB today (pad_N / lead_N are a good naming habit, not a feature), so it says so instead of implying one. The viewer's own SKILL.md and docs/CONTENT-CONVENTIONS.md carry the same contract.

Colby Knox closed this ·

Log in to reply.