From d967b8e955e966ccffdc94607ed1de4e61dc56ef Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Thu, 5 Nov 2026 14:23:41 -0300 Subject: docs: the effects programme's documents go with it: docs/effects.md (its catalogue, its feel reviews) and docs/next-anim.md (the animation plan) are gone, and docs/render-pipeline.md says only what is left: the core's frame (the pump, its deadlines, one Surface that does not move) and what each frontend draws on its own clock from it (the glide, the window's caret, the blink, a jump's trail, InactiveDim, the Pet) and the window's four draw groups; the changelog says what left and what stayed; code comments and docs that cited the old sections or files cite the new note or nothing (building.typ, next-pdfrender.md, config.zig, gui.zig, glide.zig) Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge --- docs/next-pdfrender.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/next-pdfrender.md') diff --git a/docs/next-pdfrender.md b/docs/next-pdfrender.md index 4c8565d8..9e2e34b8 100644 --- a/docs/next-pdfrender.md +++ b/docs/next-pdfrender.md @@ -1,7 +1,7 @@ # pdfrender: PDF pages rendered off the loop The author's ask: "add concurrency to the mupdf build so its smoother". The -open item of `next-anim.md` (7): the bridge rendered on the loop through one +open item of the animation plan (7): the bridge rendered on the loop through one MuPDF context and a one-page cache, so a PDF's first frame, a far jump's page and every page a held PageDown reached cost the frame they landed in. Later asks from the coordinator, answered here too: the Intel SDM (combined -- cgit v1.3