Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
## editors
|
|
|
|
|
/.idea
|
|
|
|
|
/.vscode
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
## system files
|
|
|
|
|
.DS_Store
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
## npm
|
|
|
|
|
/node_modules/
|
|
|
|
|
/npm-debug.log
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
## testing
|
|
|
|
|
/coverage/
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
## temp folders
|
|
|
|
|
/.tmp/
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
# build
|
|
|
|
|
/_site/
|
|
|
|
|
/dist/
|
|
|
|
|
/out-tsc/
|
2024-11-17 04:07:16 +00:00
|
|
|
|
Updated movement code for performance and accuracy.
This was a learning experience.
The transform controls `rotate`, `scale`, and `translate` have independent CSS names now, so I don't
have to memorize the transformation pattern needed to make them go as expected. On the other hand,
`transition` is still how you describe the speed and easing. And even though they're not
officially transformations, `transitionend` is how you detect when one has completed.
All of the various different techniques for figuring out where something is on the page with respect
to another element can be terribly confusing. Ultimately, I went with offsets-from-viewport, as that
seems to be the most common way of doing the calculations.
Separating `pointermove` from the animation frames used to update the page is a very nifty technique
that I learned from the Svelte guys. `pointermove` only updates an (x,y) coordinate pair that you
keep in memory; as long as you're "tracking a drag," you just update on every available animation
frame, using the last (x,y) pair that it saved. This gives you much smoother animations.
2025-01-21 00:03:18 +00:00
|
|
|
storybook-static
|
2024-11-17 04:07:16 +00:00
|
|
|
custom-elements.json
|