Conversation
- Composite glyph pixels directly to avoid per-sample canvas traversal - Render and encode PNGs in strips without allocating a full canvas - Reuse prepared text and repeated background and shadow rows
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
1 participant
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.
DISCLAIMER: Most of the code in this PR was generated with AI assistance
Large snapshots become expensive once the canvas exceeds tiny-skia's 8191 px tiling threshold: drawing individual glyph samples repeatedly traverses canvas tiles, while full-canvas buffers increase memory usage.
This change:
My local benchmark with 800 lines of code:
Strip clipping still produce small anti-aliasing differences at fractional rounded corners but I think that's tolerable