ext/hyperframes
2
0
Fork 0
mirror of https://github.com/heygen-com/hyperframes.git synced 2026-08-31 02:41:44 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
hyperframes/docs/catalog/components/input-feedback.mdx
T
Miguel ÁngelandMiguel Angel Simon Sierra 1ae2067b8d feat(catalog): put the variables panel back, on payloads (#3199) 
* feat(catalog): put the variables panel back, on payloads

The panel drove its preview by loading an .html from docs/public, a type the
host does not publish, so it showed an empty frame in production and was
parked when the catalog was re-landed.

It now mounts the same JSON payload the plain player uses and re-mounts it as
values change, injecting them as window.__hfVariables into the composition head
before any of its scripts run, which is where the runtime reads overrides from.
Doing it in the markup rather than after load is what stops the composition
initialising with the wrong values first.

172 items with variables get the panel back; the playhead carries across a
change so a tweak mid-shot does not jump back to frame zero.

* fix(docs): drop the unused url form and the needless escapes

* fix(docs): the panel cannot reference a binding beside the export

* feat(catalog): make importing an SVG the obvious move

A reader arrives at this control with a shape, not with path data, and the
panel asked for the coordinates first. Import is now the primary action in a
drop target you can see is a drop target, and the raw path sits behind a
disclosure for anyone who wants it.

* feat(cli): let a fruitless catalog search report the gap

An agent that searches by meaning and finds nothing worth installing knows
something we do not: the name of a move the catalog is missing. There was no
way to tell us, so that knowledge was lost at the end of every run.

hyperframes feedback --search-miss "<query>" --wanted "<the move>" records it.
It carries no rating, so it never lands in the rating metric, and it is a
separate deliberate command rather than something catalog --query does on its
own: plain search still sends nothing, which is what the CLI promises.

--rating stops being required at the arg level, since a miss has no rating to
give. The check moved into the run body, where an absent one is now handled
rather than crashing on undefined.

* feat(cli): carry tuned variable values into the install snippet

Someone who tunes a block on its catalog page had no way to keep those values:
the install command was the same one everybody gets, and the tuning stayed on
the page.

hyperframes add <item> --vars '<json>' now prints a mount element carrying
data-variable-values, so the values land where the block is used.

They ride on the host rather than being written into the installed file. That
keeps the composition on disk byte-identical to the registry's, so a later
reinstall can still tell an edit from an update, and it lets two mounts of the
same block carry different values.

* fix(catalog): serve the item's own directory so runtime paths resolve

Some compositions assemble their asset URLs at run time —
"compositions/components/" + texture + ".png" for the texture masks, a font the
compiler pulled into _remote_media — and no scan of the markup can see a string
that does not exist until a script concatenates it. Those items either rendered
black or were dropped to a video that had never been uploaded.

Each item that needs it now has its prepared directory published, and its
payload carries a <base> pointing at it, so any relative path the composition
invents resolves. caption-texture renders its masks again, and
variable-font-flex has a preview at all for the first time: its MP4 and poster
are both 403.

Both layouts are published, because which one a composition asks for differs
per item, and a directory only earns that if it is under 2 MB. The 12 MB
texture sheet keeps the recorded video it already had.

* fix(catalog): let the variables panel actually drive the composition

Every control on the panel was inert. The values reached the composition and
nothing repainted, because the payload had already been compiled: compiling
inlines a mounted component and resolves its variables into the markup and CSS,
so by the time a reader turns a knob there is nothing left to change.

An item that declares variables now ships uncompiled, keeping the mount the
runtime loads at run time, which is the only state where data-variable-values
still means anything. The component travels inline as a data URI rather than a
sibling file, because .html is the one type the docs host will not publish. The
demo's own pinned values come off, so the reader's choices reach the mount
instead of losing to the values the demo picked to show itself off.

Measured on the rendered frame rather than the DOM: green rgb(98,207,144),
blue rgb(6,6,199), violet rgb(177,147,230), and back to green.

docs/public/catalog drops from 48 MB to 35 MB along the way, since an
uncompiled payload carries far less than an inlined one.

* feat(catalog): keep variable changes in the url

A reader who tuned a piece lost it on reload, and had nothing to send anyone.
The values now live in the query string, scoped by composition id so two links
never read each other,and only the ones that differ from the defaults are
written, so changing one knob gives a short URL rather than every variable
spelled out.

replaceState rather than pushState: dragging a slider should not leave a trail
of history entries. An unreadable value is ignored rather than thrown, so a
truncated or hand-edited link opens the piece at its defaults.

* fix(catalog): only rewrite the url when a value actually changed

* refactor(catalog): memoise the declared defaults on their content

* feat(catalog): offer an install command carrying the tuned values

The Install block is generated before anyone touches a knob, so it can only
ever print the plain command. Someone who spent a minute tuning a piece copied
it and got the defaults back.

The panel now carries its own command in the Snippet tab, with --vars holding
exactly the values that differ. An untouched piece still offers the same short
command, so nothing gets noisier for the common case.

* fix(catalog): a piece with nothing to render is a skip, not a failure

caption-blend-difference is a stylesheet and a paragraph of prose — a class you
add to your own captions, with no standalone scene to show. The generator
treated that as a build failure, so every run ended by reporting something
broken when nothing was.

It now reports the shape it is and keeps its recorded video, which is the only
honest preview such an item has. A genuine render failure still throws.

* fix(catalog): restore variables from the url on a cold load

A shared link opened at the defaults. The first render happens on the server,
where there is no window to read the query string from, and React then hydrates
against that markup and never revisits it — so the values only appeared once you
touched a control.

The URL is read again after mount, which is the first moment it exists. The
value is also escaped once now rather than twice: URLSearchParams already
decodes on the way out, and decoding a second time turned an SVG path full of
percent-escapes into something that no longer parsed, besides doubling the
length of every link.

* fix(catalog): mount the preview with the values a link carried

The frame was built from the declared defaults and the shared values were
posted to it afterwards, which is too late for anything the composition reads
once at init: a path arrived after the mark had already been drawn from the
default one, so a link looked right in the panel and wrong on screen.

* feat(catalog): the install command follows the values you tuned

Copying the Install line gave the plain command back, because that block is
generated before anyone touches a knob and had no way to know what changed. The
tuned command only existed in the panel Snippet tab, which is not where anyone
looks for it.

The line now reads the same query string the panel writes, so the two agree
without either component knowing the other exists, and a shared link carries the
right command too. replaceState fires no event, so the panel announces its own
writes.

* fix(catalog): send a text variable to the preview once it is finished

Every other control in the explorer reports a whole value on every event: a
slider at any position is a position, a swatch is a colour. A text field is
not. Typing v3 into a badge posted v first, so the preview remounted and
rendered a composition built from half a word.

The post now waits while a text field has focus and goes out when the edit is
committed, with Enter or by clicking away. The field itself is unchanged and
still tracks every keystroke.

---------

Co-authored-by: Miguel Angel Simon Sierra <miguelangelsi07@gmail.com>
2026-08-10 22:40:01 -04:00

381 lines
13 KiB
Plaintext
Raw Permalink Blame History

---
title: "Input Feedback"
description: "A transitions.dev-inspired input feedback primitive with shake, clear affordance, and success state"
---
import { InstallCommand } from "/snippets/install-command.jsx";
import { VariablesExplorer } from "/snippets/variables-explorer.jsx";
<VariablesExplorer
previewSrc="/public/catalog/components/input-feedback.json"
compositionId="input-feedback"
compositionSrc="compositions/components/input-feedback.html"
variables={[{"id":"status","type":"enum","role":"style","label":"Status","description":"Whether the field reads as accepted or rejected, colouring the border, chip and hint.","default":"valid","options":[{"value":"valid","label":"Valid"},{"value":"error","label":"Error"}]},{"id":"value","type":"string","role":"content","label":"Value","description":"Text held by the field.","default":"mia@example.com"},{"id":"hint","type":"string","role":"content","label":"Hint","description":"Helper line under the field.","default":"Looks good."}]}
>
```html input-feedback.html
<!--
Input Feedback - transitions.dev-inspired primitive for HyperFrames.
Paste the markup, CSS and script into a composition. Use the timeline
integration note at the bottom as the starting point for deterministic GSAP
animation.
Variables. The script reads each one, falls back to the declared default on
anything missing or unrecognised, and writes the text or state attribute the
CSS below already keys off. The timeline recipe at the bottom is untouched
by them: it keeps shaking the same shell and popping the same chip.
- status (valid | error, default valid): whether the field reads as
accepted or rejected. valid is the green border, chip and hint; error
turns all three red and swaps the chip glyph to an exclamation mark.
Pair it with a matching hint.
- value (string, default "mia@example.com"): the text held by the field.
A blank or non-text override keeps the default.
- hint (string, default "Looks good."): the helper line under the field.
On every default the result is identical to the original: a green valid
field holding mia@example.com over Looks good.
-->
<div
class="hf-transition-input-feedback"
data-state="valid"
data-composition-variables='[
{ "id": "status", "type": "enum", "role": "style", "label": "Status", "description": "Whether the field reads as accepted or rejected, colouring the border, chip and hint.", "default": "valid", "options": [{ "value": "valid", "label": "Valid" }, { "value": "error", "label": "Error" }] },
{ "id": "value", "type": "string", "role": "content", "label": "Value", "description": "Text held by the field.", "default": "mia@example.com" },
{ "id": "hint", "type": "string", "role": "content", "label": "Hint", "description": "Helper line under the field.", "default": "Looks good." }
]'
>
<label>Email</label>
<div class="hf-transition-input-shell">
<span class="hf-transition-input-value">mia@example.com</span>
<button class="hf-transition-input-clear" type="button">x</button>
<span class="hf-transition-input-check">OK</span>
</div>
<p class="hf-transition-input-hint">Looks good.</p>
</div>
<style>
.hf-transition-input-feedback {
--hf-fb-border: #d4d4d8;
--hf-fb-chip-bg: #dcfce7;
--hf-fb-chip-fg: #166534;
--hf-fb-hint: #16a34a;
display: grid;
gap: 10px;
width: 430px;
color: #18181b;
font-family: Inter, system-ui, sans-serif;
}
.hf-transition-input-feedback label {
color: #52525b;
font-size: 15px;
font-weight: 850;
}
.hf-transition-input-shell {
display: flex;
align-items: center;
gap: 12px;
height: 62px;
padding: 0 16px;
border: 1px solid var(--hf-fb-border);
border-radius: 16px;
background: #ffffff;
box-shadow: 0 18px 50px rgba(0, 0, 0, 0.08);
}
.hf-transition-input-value {
flex: 1;
font-size: 20px;
font-weight: 760;
}
.hf-transition-input-clear,
.hf-transition-input-check {
display: grid;
place-items: center;
height: 28px;
border-radius: 999px;
font-size: 12px;
font-weight: 900;
}
.hf-transition-input-clear {
width: 28px;
border: 0;
background: #f4f4f5;
color: #71717a;
}
.hf-transition-input-check {
min-width: 38px;
padding: 0 8px;
background: var(--hf-fb-chip-bg);
color: var(--hf-fb-chip-fg);
}
.hf-transition-input-hint {
margin: 0;
color: var(--hf-fb-hint);
font-size: 14px;
font-weight: 800;
}
.hf-transition-input-feedback[data-state="error"] {
--hf-fb-border: #fca5a5;
--hf-fb-chip-bg: #fee2e2;
--hf-fb-chip-fg: #991b1b;
--hf-fb-hint: #dc2626;
}
</style>
<script>
(function () {
"use strict";
var vars =
window.__hyperframes && window.__hyperframes.getVariables
? window.__hyperframes.getVariables()
: {};
// Unrecognised overrides return to their declared defaults.
function pick(table, value, fallback) {
return Object.prototype.hasOwnProperty.call(table, value) ? value : fallback;
}
function text(value, fallback) {
return typeof value === "string" && value.trim() !== "" ? value : fallback;
}
var statuses = { valid: "OK", error: "!" };
var status = pick(statuses, vars.status, "valid");
var value = text(vars.value, "mia@example.com");
var hint = text(vars.hint, "Looks good.");
var roots = document.querySelectorAll(".hf-transition-input-feedback");
for (var i = 0; i < roots.length; i += 1) {
var root = roots[i];
root.setAttribute("data-state", status);
var valueEl = root.querySelector(".hf-transition-input-value");
if (valueEl) valueEl.textContent = value;
var hintEl = root.querySelector(".hf-transition-input-hint");
if (hintEl) hintEl.textContent = hint;
var chip = root.querySelector(".hf-transition-input-check");
if (chip) chip.textContent = statuses[status];
}
})();
</script>
<!--
Timeline integration:
tl.fromTo('.hf-transition-input-feedback', { y: 22, opacity: 0 }, { y: 0, opacity: 1, duration: 0.34, ease: 'power2.out' }, 0.3);
tl.to('.hf-transition-input-shell', { x: -12, duration: 0.06, repeat: 5, yoyo: true, ease: 'none' }, 0.72);
tl.fromTo('.hf-transition-input-check', { scale: 0, opacity: 0 }, { scale: 1, opacity: 1, duration: 0.28, ease: 'back.out(2)' }, 1.18);
tl.fromTo('.hf-transition-input-hint', { opacity: 0, y: -6 }, { opacity: 1, y: 0, duration: 0.22, ease: 'power2.out' }, 1.28);
-->
```
</VariablesExplorer>
## Install
<InstallCommand command="npx hyperframes add input-feedback" item="input-feedback" />
That writes one file: `compositions/components/input-feedback.html`.
## Variables
Every one of these has a default, so the piece works untouched. Set the ones you
want to change on the element:
| Variable | Default | Accepts | What it does |
| --- | --- | --- | --- |
| `status` | `valid` | `valid`, `error` | Whether the field reads as accepted or rejected, colouring the border, chip and hint. |
| `value` | `mia@example.com` | string | Text held by the field. |
| `hint` | `Looks good.` | string | Helper line under the field. |
Set them with `data-variable-values` on the element that mounts it. These are the
defaults, so this behaves exactly like the preview above until you change one:
```html wrap
<div
data-composition-id="input-feedback"
data-composition-src="compositions/components/input-feedback.html"
data-variable-values='{"status":"valid","value":"mia@example.com","hint":"Looks good."}'
></div>
```
## Source
<Accordion title={`input-feedback.html`}>
```html
<!--
Input Feedback - transitions.dev-inspired primitive for HyperFrames.
Paste the markup, CSS and script into a composition. Use the timeline
integration note at the bottom as the starting point for deterministic GSAP
animation.
Variables. The script reads each one, falls back to the declared default on
anything missing or unrecognised, and writes the text or state attribute the
CSS below already keys off. The timeline recipe at the bottom is untouched
by them: it keeps shaking the same shell and popping the same chip.
- status (valid | error, default valid): whether the field reads as
accepted or rejected. valid is the green border, chip and hint; error
turns all three red and swaps the chip glyph to an exclamation mark.
Pair it with a matching hint.
- value (string, default "mia@example.com"): the text held by the field.
A blank or non-text override keeps the default.
- hint (string, default "Looks good."): the helper line under the field.
On every default the result is identical to the original: a green valid
field holding mia@example.com over Looks good.
-->
<div
class="hf-transition-input-feedback"
data-state="valid"
data-composition-variables='[
{ "id": "status", "type": "enum", "role": "style", "label": "Status", "description": "Whether the field reads as accepted or rejected, colouring the border, chip and hint.", "default": "valid", "options": [{ "value": "valid", "label": "Valid" }, { "value": "error", "label": "Error" }] },
{ "id": "value", "type": "string", "role": "content", "label": "Value", "description": "Text held by the field.", "default": "mia@example.com" },
{ "id": "hint", "type": "string", "role": "content", "label": "Hint", "description": "Helper line under the field.", "default": "Looks good." }
]'
>
<label>Email</label>
<div class="hf-transition-input-shell">
<span class="hf-transition-input-value">mia@example.com</span>
<button class="hf-transition-input-clear" type="button">x</button>
<span class="hf-transition-input-check">OK</span>
</div>
<p class="hf-transition-input-hint">Looks good.</p>
</div>
<style>
.hf-transition-input-feedback {
--hf-fb-border: #d4d4d8;
--hf-fb-chip-bg: #dcfce7;
--hf-fb-chip-fg: #166534;
--hf-fb-hint: #16a34a;
display: grid;
gap: 10px;
width: 430px;
color: #18181b;
font-family: Inter, system-ui, sans-serif;
}
.hf-transition-input-feedback label {
color: #52525b;
font-size: 15px;
font-weight: 850;
}
.hf-transition-input-shell {
display: flex;
align-items: center;
gap: 12px;
height: 62px;
padding: 0 16px;
border: 1px solid var(--hf-fb-border);
border-radius: 16px;
background: #ffffff;
box-shadow: 0 18px 50px rgba(0, 0, 0, 0.08);
}
.hf-transition-input-value {
flex: 1;
font-size: 20px;
font-weight: 760;
}
.hf-transition-input-clear,
.hf-transition-input-check {
display: grid;
place-items: center;
height: 28px;
border-radius: 999px;
font-size: 12px;
font-weight: 900;
}
.hf-transition-input-clear {
width: 28px;
border: 0;
background: #f4f4f5;
color: #71717a;
}
.hf-transition-input-check {
min-width: 38px;
padding: 0 8px;
background: var(--hf-fb-chip-bg);
color: var(--hf-fb-chip-fg);
}
.hf-transition-input-hint {
margin: 0;
color: var(--hf-fb-hint);
font-size: 14px;
font-weight: 800;
}
.hf-transition-input-feedback[data-state="error"] {
--hf-fb-border: #fca5a5;
--hf-fb-chip-bg: #fee2e2;
--hf-fb-chip-fg: #991b1b;
--hf-fb-hint: #dc2626;
}
</style>
<script>
(function () {
"use strict";
var vars =
window.__hyperframes && window.__hyperframes.getVariables
? window.__hyperframes.getVariables()
: {};
// Unrecognised overrides return to their declared defaults.
function pick(table, value, fallback) {
return Object.prototype.hasOwnProperty.call(table, value) ? value : fallback;
}
function text(value, fallback) {
return typeof value === "string" && value.trim() !== "" ? value : fallback;
}
var statuses = { valid: "OK", error: "!" };
var status = pick(statuses, vars.status, "valid");
var value = text(vars.value, "mia@example.com");
var hint = text(vars.hint, "Looks good.");
var roots = document.querySelectorAll(".hf-transition-input-feedback");
for (var i = 0; i < roots.length; i += 1) {
var root = roots[i];
root.setAttribute("data-state", status);
var valueEl = root.querySelector(".hf-transition-input-value");
if (valueEl) valueEl.textContent = value;
var hintEl = root.querySelector(".hf-transition-input-hint");
if (hintEl) hintEl.textContent = hint;
var chip = root.querySelector(".hf-transition-input-check");
if (chip) chip.textContent = statuses[status];
}
})();
</script>
<!--
Timeline integration:
tl.fromTo('.hf-transition-input-feedback', { y: 22, opacity: 0 }, { y: 0, opacity: 1, duration: 0.34, ease: 'power2.out' }, 0.3);
tl.to('.hf-transition-input-shell', { x: -12, duration: 0.06, repeat: 5, yoyo: true, ease: 'none' }, 0.72);
tl.fromTo('.hf-transition-input-check', { scale: 0, opacity: 0 }, { scale: 1, opacity: 1, duration: 0.28, ease: 'back.out(2)' }, 1.18);
tl.fromTo('.hf-transition-input-hint', { opacity: 0, y: -6 }, { opacity: 1, y: 0, duration: 0.22, ease: 'power2.out' }, 1.28);
-->
```
</Accordion>
## Usage
Open `compositions/components/input-feedback.html` and paste its contents into your composition. See the comment header in the file for detailed instructions.
{/* hf:generated-footer */}
Tagged `transition-primitive` `transitions-dev-port` `input` `feedback`.
## Related topics
- [Browse the complete Catalog](/catalog)
- [Add assets and Catalog items in Studio](/studio/assets-and-blocks)
- [Build a richer composition](/go-further)
Reference in New Issue View Git Blame Copy Permalink