WIP Run Flare-JS in a WebWorker with an offscreencanvas #6
Conversation
This file contains 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
The key change here is swapping in svg.js for createElementNS in order to decouple Flare-JS from the DOM. The rest is fairly straightforward.
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.
This is not intended to be merged. The intention is to provide a working example of how Flare-JS, with some minor changes, could be run in a WebWorker using an OffscreenCanvas. In principle being able to run in a WebWorker is extremely useful for applications that need to keep the main thread free for heavy UIs or other intensive tasks that need to run on the main thread like video. For some reason the frame rate in this example rapidly declines but I have another more heavily modified example that maintains a high frame rate and I'm not sure what the difference is.
The key change here is swapping in svg.js for createElementNS in order to decouple Flare-JS from the DOM. The rest is fairly straightforward, though I don't know if there are other features that rely on the DOM that just aren't being used in this example.