Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Proposal: Web Worker support/example #128

Open
qrohlf opened this issue May 24, 2020 · 0 comments
Open

Feature Proposal: Web Worker support/example #128

qrohlf opened this issue May 24, 2020 · 0 comments

Comments

@qrohlf
Copy link
Owner

qrohlf commented May 24, 2020

I'd like to run some tests on how to move Trianglify computations off the main thread.

The main use case here is increasing the responsiveness of the sliders on https://trianglify.io/ - normally, for high-framerate use cases I would recommend implementing custom animation logic on the raw geometry output of Trianglify, but because the input sliders require mesh re-generation and re-coloring this is a unique situation that means I have to call the full trianglify().toCanvas() pipeline every time the user moves a slider.

Throttling to 15fps and/or using requestAnimationFrame can help in some situations, but ultimately moving pattern computation off the UI thread would be the most effective solution to this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant