figcraft/apps
bflatastic ef15ab67cf Spike (gap #7): GPU canvas (vello) behind a feature flag
New figcraft-render-gpu crate (L4): the scene graph as a vello scene on
wgpu 30 (the version eframe 0.36 uses), kept per top-level layer, culled
to the view, read back to the canvas texture. Off by default: the
gpu-canvas cargo feature plus Preferences > GPU canvas or ui.set
{gpuCanvas}. Effects, masks, pattern fills and outline views fall back
to the CPU renderer per frame (ui.inspect canvas.gpuFallback). Exports,
CLI and MCP stay on the CPU. Parity test against the CPU renderer
(ignored: needs a GPU) and a CPU vs GPU frame-time bench example.
2026-10-11 16:30:13 +07:00
..
figcraft Spike (gap #7): GPU canvas (vello) behind a feature flag 2026-10-11 16:30:13 +07:00
figcraft-cli M8: canvas fixes: boolean hit testing, group drags, frame outlines and slices view, a flaky idle test (#123) 2026-10-11 14:25:25 +07:00
figcraft-server M9: team libraries on the server; swap library (#117) 2026-10-11 13:05:46 +07:00
figcraft-web M9: live sessions in the browser; join links and dialog polish (#106) 2026-10-11 09:10:59 +07:00