Chris Tate
8fc933b9db
* fix(windows): accelerate gpu surface presentation - Render retained binary canvas packets through Direct2D and DirectWrite. - Preserve dirty-region updates and GPU effects with a safe software fallback. - Wire and validate the renderer across supported Windows build paths. Co-authored-by: Omer Shatzberg <131801941+oshtz@users.noreply.github.com> * fix(windows): harden Direct2D presentation * fix(sdk): separate GPU backend request types * fix(windows): honor GPU surface fallback contracts * fix(windows): scale transformed blur kernels * fix: harden Windows GPU surface presentation * fix(windows): harden gpu blur and caption sampling * fix(runtime): bypass packets for software surfaces * fix(windows): preserve precise gpu surface updates * fix(windows): reconcile GPU presenter state * fix: preserve retained canvas resources * fix: preserve Windows canvas packet fidelity --------- Co-authored-by: Omer Shatzberg <131801941+oshtz@users.noreply.github.com>
Next Example
A super basic Native SDK example using Next.js for the frontend and Zig for the native shell.
Run
zig build run
The build installs frontend dependencies, builds the frontend, and opens the native app shell with WebView content.
Dev Server
zig build dev
This starts the Next.js dev server from app.zon, waits for http://127.0.0.1:3000/, and launches the native shell with NATIVE_SDK_FRONTEND_URL.
Frontend
- Frontend:
next - Production assets:
frontend/out - Dev URL:
http://127.0.0.1:3000/
Using Outside The Repo
This example references the Native SDK via relative path (../../). To use it standalone, override the path:
zig build run -Dnative-sdk-path=/path/to/native-sdk