Skip to content

feat(ink): render dark paper without changing authored exports - #62

Draft
markm39 wants to merge 3 commits into
fix/seamless-canvasfrom
feat/dark-paper-display
Draft

markm39 wants to merge 3 commits into
fix/seamless-canvasfrom
feat/dark-paper-display

Conversation

@markm39

@markm39 markm39 commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Dark mode now renders authored ink on charcoal paper in iOS and Android while retaining the original stroke colors and light paper in saved documents and exports. A shared linear-lightness filter keeps native ink, text color helpers, and rendered diagram images consistent, including transparency. Older native binaries fall back to light document display.

Stacked on #61. Native GPU preparation precompiles dark compositing away from input handling; this change preserves the existing frame scheduler and serialization contracts.

Validation: 178 Jest tests, TypeScript, package build, release checks, native raster/shader comparisons, CPU/GPU live and committed RGBA comparisons, unchanged authored serialization, example TypeScript and iOS/Android bundle exports pass. CI passes at 8316b8c (run 39657401827), including the independent runner’s strict CPU/GPU color comparison. MathNotes Release build and direct dark paper/text/diagram display pass; switching appearance preserves its authored body byte-for-byte. The image wrapper measures its outer React Native view to avoid Skia 2.2’s onSize null-view race during Fabric mounting. OpenNotes native integration and complete application export verification remain pending. Existing interaction timing gates on #61 still fail; this PR does not claim stall-free behavior.

Simplify and security reviews completed; fixed missing source entries in the package whitelist and sanitized decoder errors so private diagram data URIs cannot appear in errors. Existing large native renderer/container and canvas files are deliberately kept intact: these changes only thread one display flag through their existing lifecycle and compose a filter at their existing output layer. New display logic is in small dedicated helpers; splitting native input/render ownership here would expand concurrency risk.

Keep unmerged pending independent engine review and application verification. No release requested.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant