mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-01 19:42:03 +00:00
Miguel ÁngelandMiguel Angel Simon Sierra
1ae2067b8d
* 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>
544 lines
20 KiB
Plaintext
544 lines
20 KiB
Plaintext
---
|
|
title: "Conic Progress Ring"
|
|
description: "A token-driven conic progress ring whose angular fill and center count settle together from one registered percentage."
|
|
---
|
|
|
|
import { InstallCommand } from "/snippets/install-command.jsx";
|
|
import { VariablesExplorer } from "/snippets/variables-explorer.jsx";
|
|
|
|
<VariablesExplorer
|
|
previewSrc="/public/catalog/components/conic-progress-ring.json"
|
|
compositionId="conic-progress-ring"
|
|
compositionSrc="compositions/components/conic-progress-ring.html"
|
|
variables={[{"id":"progress","type":"number","role":"content","label":"Progress","description":"Target angular fill from 0 to 100.","default":100,"min":0,"max":100,"step":1,"unit":"%"},{"id":"thickness","type":"number","role":"layout","label":"Thickness","description":"Ring stroke thickness as a percent of the ring radius.","default":12,"min":4,"max":30,"step":1,"unit":"%"},{"id":"label","type":"string","role":"content","label":"Center label","description":"Numeric target shown in the center and counted in sync with the fill.","default":"100"}]}
|
|
>
|
|
|
|
```html conic-progress-ring.html
|
|
<!doctype html>
|
|
<!--
|
|
conic-progress-ring: HyperFrames video primitive (data / prove / demonstrate)
|
|
|
|
Concept: one registered percentage moves the hard frontier of a conic
|
|
gradient while a radial mask cuts out the center. The center value is
|
|
derived from that same percentage on every GSAP update, so fill and count
|
|
cannot drift apart.
|
|
|
|
Compiled-from evidence: hyperframes-research-css-gems.md, section 10,
|
|
"Registered conic progress ring". The finding specifies a typed percentage
|
|
as the seek handle for a conic-gradient frontier and a radial mask for the
|
|
ring cutout.
|
|
|
|
Use when: a scene needs to prove completion, attainment, or a measured
|
|
result with one immediately legible data mark.
|
|
|
|
Variables:
|
|
progress number 0 to 100 default 100 target angular fill
|
|
thickness number 4 to 30 default 12 ring stroke as a percent
|
|
label string default "100" center count target
|
|
|
|
Envelope:
|
|
IN 1.40s fixed fill and synchronized count, power2.out
|
|
HOLD elastic and deliberately still after the result settles
|
|
OUT 0.50s fixed opacity release, power2.in
|
|
For durations shorter than 1.90s, IN and OUT scale together. HOLD is the
|
|
only elastic phase. The timeline is never time-scaled.
|
|
|
|
Sync point:
|
|
progress-settled at the end of IN, always outside the elastic HOLD
|
|
|
|
Sound cues: none. A data proof should not claim an audio event for its host.
|
|
|
|
Mount contract: this file is a template-wrapped sub-composition. The host
|
|
owns dimensions. #root fills that box with inset:0 and has no data-width or
|
|
data-height. The hardcoded composition id matches the root and timeline key.
|
|
-->
|
|
<html
|
|
lang="en"
|
|
data-composition-variables='[
|
|
{ "id": "progress", "type": "number", "role": "content", "label": "Progress", "description": "Target angular fill from 0 to 100.", "default": 100, "min": 0, "max": 100, "step": 1, "unit": "%" },
|
|
{ "id": "thickness", "type": "number", "role": "layout", "label": "Thickness", "description": "Ring stroke thickness as a percent of the ring radius.", "default": 12, "min": 4, "max": 30, "step": 1, "unit": "%" },
|
|
{ "id": "label", "type": "string", "role": "content", "label": "Center label", "description": "Numeric target shown in the center and counted in sync with the fill.", "default": "100" }
|
|
]'
|
|
>
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<title>Conic Progress Ring</title>
|
|
</head>
|
|
<body>
|
|
<template>
|
|
<div id="root" data-composition-id="conic-progress-ring" data-duration="4" data-fps="30">
|
|
<style>
|
|
/* The registration must live in this document-level stylesheet.
|
|
Registrations inside shadow roots are ignored by the platform. */
|
|
@property --ring-progress {
|
|
syntax: "<percentage>";
|
|
inherits: false;
|
|
initial-value: 0%;
|
|
}
|
|
|
|
*,
|
|
*::before,
|
|
*::after {
|
|
box-sizing: border-box;
|
|
}
|
|
|
|
/* INVARIANT: #root is the mount contract owner. The host owns the
|
|
box, and every internal measurement is relative to that box. */
|
|
#root {
|
|
position: absolute;
|
|
inset: 0;
|
|
container-type: size;
|
|
isolation: isolate;
|
|
overflow: hidden;
|
|
color: var(--fg, #f4f7fb);
|
|
font-family: var(--font-display, Inter, system-ui, sans-serif);
|
|
}
|
|
|
|
.ring-clip {
|
|
width: 100%;
|
|
height: 100%;
|
|
display: grid;
|
|
place-items: center;
|
|
}
|
|
|
|
.ring-stage {
|
|
position: relative;
|
|
width: min(68cqw, 68cqh);
|
|
aspect-ratio: 1;
|
|
}
|
|
|
|
/* EDIT ZONE: --ring-thickness is the only geometry control.
|
|
--ring-progress is the only registered animation scalar. Paint
|
|
comes only from the host theme's surface and brand tokens. */
|
|
.ring {
|
|
--ring-thickness: 12%;
|
|
--ring-progress: 0%;
|
|
position: absolute;
|
|
inset: 0;
|
|
border-radius: 50%;
|
|
background: conic-gradient(
|
|
from -90deg,
|
|
var(--brand, #35d6a0) 0 var(--ring-progress),
|
|
var(--surface, #1b2938) var(--ring-progress) 100%
|
|
);
|
|
-webkit-mask: radial-gradient(
|
|
farthest-side,
|
|
transparent calc(100% - var(--ring-thickness)),
|
|
var(--fg, #f4f7fb) 0
|
|
);
|
|
mask: radial-gradient(
|
|
farthest-side,
|
|
transparent calc(100% - var(--ring-thickness)),
|
|
var(--fg, #f4f7fb) 0
|
|
);
|
|
}
|
|
|
|
.ring-label {
|
|
position: absolute;
|
|
inset: 0;
|
|
display: grid;
|
|
place-items: center;
|
|
color: var(--fg, #f4f7fb);
|
|
font-size: min(18cqw, 18cqh);
|
|
font-weight: 700;
|
|
font-variant-numeric: tabular-nums;
|
|
letter-spacing: -0.04em;
|
|
line-height: 1;
|
|
text-align: center;
|
|
}
|
|
</style>
|
|
|
|
<div
|
|
id="conic-progress-ring-clip"
|
|
class="ring-clip clip"
|
|
data-start="0"
|
|
data-duration="4"
|
|
data-track-index="0"
|
|
>
|
|
<div class="ring-stage">
|
|
<div
|
|
class="ring"
|
|
role="progressbar"
|
|
aria-label="Progress"
|
|
aria-valuemin="0"
|
|
aria-valuemax="100"
|
|
aria-valuenow="0"
|
|
></div>
|
|
<div class="ring-label" aria-hidden="true">0</div>
|
|
</div>
|
|
</div>
|
|
|
|
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
|
|
<script>
|
|
(function () {
|
|
"use strict";
|
|
|
|
var root = document.getElementById("root");
|
|
var compositionId = "conic-progress-ring";
|
|
var stage = root.querySelector(".ring-stage");
|
|
var ring = root.querySelector(".ring");
|
|
var label = root.querySelector(".ring-label");
|
|
var vars =
|
|
window.__hyperframes && window.__hyperframes.getVariables
|
|
? window.__hyperframes.getVariables()
|
|
: {};
|
|
|
|
/* INVARIANT: zero is a valid progress value, so missing and zero
|
|
are handled separately. Both numeric controls clamp to their
|
|
declared ranges before they reach layout or animation. */
|
|
var progressValue = Number(vars.progress);
|
|
var targetProgress = Number.isFinite(progressValue)
|
|
? Math.max(0, Math.min(100, progressValue))
|
|
: 100;
|
|
var thicknessValue = Number(vars.thickness);
|
|
var thickness = Number.isFinite(thicknessValue)
|
|
? Math.max(4, Math.min(30, thicknessValue))
|
|
: 12;
|
|
var labelText = vars.label == null ? "100" : String(vars.label);
|
|
var labelMatch = labelText.trim().match(/^(-?\d+(?:\.\d+)?)(.*)$/);
|
|
var labelTarget = labelMatch ? Number(labelMatch[1]) : null;
|
|
var labelSuffix = labelMatch ? labelMatch[2] : "";
|
|
|
|
ring.style.setProperty("--ring-thickness", thickness + "%");
|
|
|
|
function updateLabel(fillPercent) {
|
|
var ratio = targetProgress > 0 ? fillPercent / targetProgress : 1;
|
|
label.textContent =
|
|
labelTarget == null ? labelText : Math.round(labelTarget * ratio) + labelSuffix;
|
|
ring.setAttribute("aria-valuenow", String(Math.round(fillPercent)));
|
|
}
|
|
|
|
updateLabel(0);
|
|
|
|
/* RETIME RANGE: IN_BASE and OUT_BASE own the lifecycle timing.
|
|
The fill uses --ease-standard's GSAP form, power2.out. */
|
|
var IN_BASE = 1.4;
|
|
var OUT_BASE = 0.5;
|
|
var durationValue = Number(root.dataset.duration);
|
|
var duration = Number.isFinite(durationValue) && durationValue > 0 ? durationValue : 4;
|
|
var scale = duration < IN_BASE + OUT_BASE ? duration / (IN_BASE + OUT_BASE) : 1;
|
|
var IN = IN_BASE * scale;
|
|
var OUT = OUT_BASE * scale;
|
|
var HOLD = Math.max(0, duration - IN - OUT);
|
|
var OUT_START = IN + HOLD;
|
|
|
|
var tl = gsap.timeline({ paused: true });
|
|
|
|
tl.fromTo(
|
|
ring,
|
|
{ "--ring-progress": "0%" },
|
|
{
|
|
"--ring-progress": targetProgress + "%",
|
|
duration: IN,
|
|
ease: "power2.out",
|
|
onUpdate: function () {
|
|
updateLabel(parseFloat(ring.style.getPropertyValue("--ring-progress")) || 0);
|
|
},
|
|
},
|
|
0,
|
|
);
|
|
tl.to(stage, { opacity: 0, duration: OUT, ease: "power2.in" }, OUT_START);
|
|
|
|
tl.seek(0);
|
|
|
|
window.__timelines = window.__timelines || {};
|
|
window.__timelines[compositionId] = tl;
|
|
})();
|
|
</script>
|
|
</div>
|
|
</template>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
</VariablesExplorer>
|
|
|
|
## Install
|
|
|
|
<InstallCommand command="npx hyperframes add conic-progress-ring" item="conic-progress-ring" />
|
|
|
|
That writes one file: `compositions/components/conic-progress-ring.html`.
|
|
|
|
## Paste it into your composition
|
|
|
|
Open `compositions/components/conic-progress-ring.html` and copy what is inside into your own composition.
|
|
|
|
A component has no size or duration of its own. It takes both from the composition
|
|
you paste it into.
|
|
|
|
## 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 |
|
|
| --- | --- | --- | --- |
|
|
| `progress` | `100` | 0% to 100%, step 1% | Target angular fill from 0 to 100. |
|
|
| `thickness` | `12` | 4% to 30%, step 1% | Ring stroke thickness as a percent of the ring radius. |
|
|
| `label` | `100` | string | Numeric target shown in the center and counted in sync with the fill. |
|
|
|
|
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="conic-progress-ring"
|
|
data-composition-src="compositions/components/conic-progress-ring.html"
|
|
data-variable-values='{"progress":100,"thickness":12,"label":"100"}'
|
|
></div>
|
|
```
|
|
|
|
## Source
|
|
|
|
<Accordion title={`conic-progress-ring.html`}>
|
|
|
|
```html
|
|
<!doctype html>
|
|
<!--
|
|
conic-progress-ring: HyperFrames video primitive (data / prove / demonstrate)
|
|
|
|
Concept: one registered percentage moves the hard frontier of a conic
|
|
gradient while a radial mask cuts out the center. The center value is
|
|
derived from that same percentage on every GSAP update, so fill and count
|
|
cannot drift apart.
|
|
|
|
Compiled-from evidence: hyperframes-research-css-gems.md, section 10,
|
|
"Registered conic progress ring". The finding specifies a typed percentage
|
|
as the seek handle for a conic-gradient frontier and a radial mask for the
|
|
ring cutout.
|
|
|
|
Use when: a scene needs to prove completion, attainment, or a measured
|
|
result with one immediately legible data mark.
|
|
|
|
Variables:
|
|
progress number 0 to 100 default 100 target angular fill
|
|
thickness number 4 to 30 default 12 ring stroke as a percent
|
|
label string default "100" center count target
|
|
|
|
Envelope:
|
|
IN 1.40s fixed fill and synchronized count, power2.out
|
|
HOLD elastic and deliberately still after the result settles
|
|
OUT 0.50s fixed opacity release, power2.in
|
|
For durations shorter than 1.90s, IN and OUT scale together. HOLD is the
|
|
only elastic phase. The timeline is never time-scaled.
|
|
|
|
Sync point:
|
|
progress-settled at the end of IN, always outside the elastic HOLD
|
|
|
|
Sound cues: none. A data proof should not claim an audio event for its host.
|
|
|
|
Mount contract: this file is a template-wrapped sub-composition. The host
|
|
owns dimensions. #root fills that box with inset:0 and has no data-width or
|
|
data-height. The hardcoded composition id matches the root and timeline key.
|
|
-->
|
|
<html
|
|
lang="en"
|
|
data-composition-variables='[
|
|
{ "id": "progress", "type": "number", "role": "content", "label": "Progress", "description": "Target angular fill from 0 to 100.", "default": 100, "min": 0, "max": 100, "step": 1, "unit": "%" },
|
|
{ "id": "thickness", "type": "number", "role": "layout", "label": "Thickness", "description": "Ring stroke thickness as a percent of the ring radius.", "default": 12, "min": 4, "max": 30, "step": 1, "unit": "%" },
|
|
{ "id": "label", "type": "string", "role": "content", "label": "Center label", "description": "Numeric target shown in the center and counted in sync with the fill.", "default": "100" }
|
|
]'
|
|
>
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<title>Conic Progress Ring</title>
|
|
</head>
|
|
<body>
|
|
<template>
|
|
<div id="root" data-composition-id="conic-progress-ring" data-duration="4" data-fps="30">
|
|
<style>
|
|
/* The registration must live in this document-level stylesheet.
|
|
Registrations inside shadow roots are ignored by the platform. */
|
|
@property --ring-progress {
|
|
syntax: "<percentage>";
|
|
inherits: false;
|
|
initial-value: 0%;
|
|
}
|
|
|
|
*,
|
|
*::before,
|
|
*::after {
|
|
box-sizing: border-box;
|
|
}
|
|
|
|
/* INVARIANT: #root is the mount contract owner. The host owns the
|
|
box, and every internal measurement is relative to that box. */
|
|
#root {
|
|
position: absolute;
|
|
inset: 0;
|
|
container-type: size;
|
|
isolation: isolate;
|
|
overflow: hidden;
|
|
color: var(--fg, #f4f7fb);
|
|
font-family: var(--font-display, Inter, system-ui, sans-serif);
|
|
}
|
|
|
|
.ring-clip {
|
|
width: 100%;
|
|
height: 100%;
|
|
display: grid;
|
|
place-items: center;
|
|
}
|
|
|
|
.ring-stage {
|
|
position: relative;
|
|
width: min(68cqw, 68cqh);
|
|
aspect-ratio: 1;
|
|
}
|
|
|
|
/* EDIT ZONE: --ring-thickness is the only geometry control.
|
|
--ring-progress is the only registered animation scalar. Paint
|
|
comes only from the host theme's surface and brand tokens. */
|
|
.ring {
|
|
--ring-thickness: 12%;
|
|
--ring-progress: 0%;
|
|
position: absolute;
|
|
inset: 0;
|
|
border-radius: 50%;
|
|
background: conic-gradient(
|
|
from -90deg,
|
|
var(--brand, #35d6a0) 0 var(--ring-progress),
|
|
var(--surface, #1b2938) var(--ring-progress) 100%
|
|
);
|
|
-webkit-mask: radial-gradient(
|
|
farthest-side,
|
|
transparent calc(100% - var(--ring-thickness)),
|
|
var(--fg, #f4f7fb) 0
|
|
);
|
|
mask: radial-gradient(
|
|
farthest-side,
|
|
transparent calc(100% - var(--ring-thickness)),
|
|
var(--fg, #f4f7fb) 0
|
|
);
|
|
}
|
|
|
|
.ring-label {
|
|
position: absolute;
|
|
inset: 0;
|
|
display: grid;
|
|
place-items: center;
|
|
color: var(--fg, #f4f7fb);
|
|
font-size: min(18cqw, 18cqh);
|
|
font-weight: 700;
|
|
font-variant-numeric: tabular-nums;
|
|
letter-spacing: -0.04em;
|
|
line-height: 1;
|
|
text-align: center;
|
|
}
|
|
</style>
|
|
|
|
<div
|
|
id="conic-progress-ring-clip"
|
|
class="ring-clip clip"
|
|
data-start="0"
|
|
data-duration="4"
|
|
data-track-index="0"
|
|
>
|
|
<div class="ring-stage">
|
|
<div
|
|
class="ring"
|
|
role="progressbar"
|
|
aria-label="Progress"
|
|
aria-valuemin="0"
|
|
aria-valuemax="100"
|
|
aria-valuenow="0"
|
|
></div>
|
|
<div class="ring-label" aria-hidden="true">0</div>
|
|
</div>
|
|
</div>
|
|
|
|
<script src="https://cdn.jsdelivr.net/npm/gsap@3.14.2/dist/gsap.min.js"></script>
|
|
<script>
|
|
(function () {
|
|
"use strict";
|
|
|
|
var root = document.getElementById("root");
|
|
var compositionId = "conic-progress-ring";
|
|
var stage = root.querySelector(".ring-stage");
|
|
var ring = root.querySelector(".ring");
|
|
var label = root.querySelector(".ring-label");
|
|
var vars =
|
|
window.__hyperframes && window.__hyperframes.getVariables
|
|
? window.__hyperframes.getVariables()
|
|
: {};
|
|
|
|
/* INVARIANT: zero is a valid progress value, so missing and zero
|
|
are handled separately. Both numeric controls clamp to their
|
|
declared ranges before they reach layout or animation. */
|
|
var progressValue = Number(vars.progress);
|
|
var targetProgress = Number.isFinite(progressValue)
|
|
? Math.max(0, Math.min(100, progressValue))
|
|
: 100;
|
|
var thicknessValue = Number(vars.thickness);
|
|
var thickness = Number.isFinite(thicknessValue)
|
|
? Math.max(4, Math.min(30, thicknessValue))
|
|
: 12;
|
|
var labelText = vars.label == null ? "100" : String(vars.label);
|
|
var labelMatch = labelText.trim().match(/^(-?\d+(?:\.\d+)?)(.*)$/);
|
|
var labelTarget = labelMatch ? Number(labelMatch[1]) : null;
|
|
var labelSuffix = labelMatch ? labelMatch[2] : "";
|
|
|
|
ring.style.setProperty("--ring-thickness", thickness + "%");
|
|
|
|
function updateLabel(fillPercent) {
|
|
var ratio = targetProgress > 0 ? fillPercent / targetProgress : 1;
|
|
label.textContent =
|
|
labelTarget == null ? labelText : Math.round(labelTarget * ratio) + labelSuffix;
|
|
ring.setAttribute("aria-valuenow", String(Math.round(fillPercent)));
|
|
}
|
|
|
|
updateLabel(0);
|
|
|
|
/* RETIME RANGE: IN_BASE and OUT_BASE own the lifecycle timing.
|
|
The fill uses --ease-standard's GSAP form, power2.out. */
|
|
var IN_BASE = 1.4;
|
|
var OUT_BASE = 0.5;
|
|
var durationValue = Number(root.dataset.duration);
|
|
var duration = Number.isFinite(durationValue) && durationValue > 0 ? durationValue : 4;
|
|
var scale = duration < IN_BASE + OUT_BASE ? duration / (IN_BASE + OUT_BASE) : 1;
|
|
var IN = IN_BASE * scale;
|
|
var OUT = OUT_BASE * scale;
|
|
var HOLD = Math.max(0, duration - IN - OUT);
|
|
var OUT_START = IN + HOLD;
|
|
|
|
var tl = gsap.timeline({ paused: true });
|
|
|
|
tl.fromTo(
|
|
ring,
|
|
{ "--ring-progress": "0%" },
|
|
{
|
|
"--ring-progress": targetProgress + "%",
|
|
duration: IN,
|
|
ease: "power2.out",
|
|
onUpdate: function () {
|
|
updateLabel(parseFloat(ring.style.getPropertyValue("--ring-progress")) || 0);
|
|
},
|
|
},
|
|
0,
|
|
);
|
|
tl.to(stage, { opacity: 0, duration: OUT, ease: "power2.in" }, OUT_START);
|
|
|
|
tl.seek(0);
|
|
|
|
window.__timelines = window.__timelines || {};
|
|
window.__timelines[compositionId] = tl;
|
|
})();
|
|
</script>
|
|
</div>
|
|
</template>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
</Accordion>
|
|
|
|
{/* hf:generated-footer */}
|
|
|
|
Tagged `data` `progress` `ring` `conic-gradient` `prove` `demonstrate`.
|
|
|
|
## Related topics
|
|
|
|
- [Browse the complete Catalog](/catalog)
|
|
- [Add assets and Catalog items in Studio](/studio/assets-and-blocks)
|
|
- [Build a richer composition](/go-further)
|