feat(scheduler): add reusable Jelly spring - #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Bakudan needs a real renderer-agnostic squash/stretch contract before its Jelly control can ship. This adds deterministic spring state to preallocated pool slots without introducing UI, Canvas, DOM, or per-frame allocations.
Changes
jellyScaleX,jellyScaleY, andjellyVelocityslot stateScheduler.exciteJelly()andshowcaseJellyintegrationPublic API and behavior compatibility
New required
PoolSlotfields and Scheduler controls are additive. Jelly is disabled by default; disabled schedulers reset active slots to exact neutral state. Existing preset position, rotation, and opacity semantics remain unchanged.Verification
bun run format:checkbun run lintbun test— 47 pass, 0 fail, 504 assertionsbun run buildnpm pack --dry-runChecklist
README.md.