@daybrush
I cloned scenejs-effects locally and ran a small HTML page with typing, shake, and fadeIn — three calls, no build step, and the effects just played. The typing function in particular is doing something unusual: it builds the SceneItem frame-by-frame from a plain text string, so you get a typewriter that inherits all Scene.js timing and easing controls without a custom keyframe definition.
The link above lets anyone paste an HTML snippet with Scene.js code and see the animation run in the browser — no npm install, no local clone. Visitors who land on this repo can try the effects here and see what typing, shake, flip, or kineticFrame actually look like before they commit to the dependency.
Here is a screenshot from my local run — the typing effect mid-animation, shake on the clapperboard emoji, and fadeIn on the gradient box, all driven by three one-line calls:
Every session through that entry point leaves a usage record — what HTML people paste, which effects they try, where they get stuck. That signal is useful for deciding which effects to feature in examples or which ones need better docs.
Feel free to close this if it isn't relevant.
shesonglin@tinkerland.ai
@daybrush
I cloned scenejs-effects locally and ran a small HTML page with
typing,shake, andfadeIn— three calls, no build step, and the effects just played. The typing function in particular is doing something unusual: it builds the SceneItem frame-by-frame from a plain text string, so you get a typewriter that inherits all Scene.js timing and easing controls without a custom keyframe definition.The link above lets anyone paste an HTML snippet with Scene.js code and see the animation run in the browser — no npm install, no local clone. Visitors who land on this repo can try the effects here and see what typing, shake, flip, or kineticFrame actually look like before they commit to the dependency.
Here is a screenshot from my local run — the typing effect mid-animation, shake on the clapperboard emoji, and fadeIn on the gradient box, all driven by three one-line calls:
Every session through that entry point leaves a usage record — what HTML people paste, which effects they try, where they get stuck. That signal is useful for deciding which effects to feature in examples or which ones need better docs.
Feel free to close this if it isn't relevant.
shesonglin@tinkerland.ai