6.8 KiB
Implementation and acceptance plan
Product requirements — agreed 2026-11-19
The goal is a blazingly fast PDF presenter in the spirit of Pympress. Reliability of the two display roles and presentation speed take precedence over matching the Canvas Pilot technology stack. This is the implementation brief, not a claim that these capabilities already exist.
- Dual-screen operation is a hard requirement on Windows, macOS and Linux. The operator explicitly selects the display for the presenter view and the display for the audience presentation. Both roles start fullscreen by default, with an explicit windowed mode for rehearsal/troubleshooting. This is foundational work, not a later enhancement or an optional platform feature. The user will test iteratively until it works. Do not declare the application ready with an unresolved display-placement failure on any of the three operating systems.
- Presentation speed is the primary performance goal. Show a usable first page
as soon as possible and prepare the rest progressively. Pre-rendering pages to
images and keeping them beside the PDF with an
extraction.jsoncontaining source SHA and extraction metadata is explicitly acceptable. Any practical implementation technique may be considered for speed, including native platform code, background workers, renderer subprocesses, disk caches, decoded-image caches, texture preloading and lower-resolution previews followed by sharper images. Benchmark choices; avoid committing to a stack solely for consistency with another tool. - Presenter mode must show the current and next slides. Include notes when they can be extracted reliably; current/next previews are the required fallback when notes are absent or unsupported. Notes extraction must not delay presentation or leak notes onto the audience output. Always fit all presenter notes to the available notes pane, recalculating wrapping and font size on content, pane and DPI changes.
- Picture folders are also slide sources. Order images by natural filename
ordering (for example, slide_2 before slide_10). Support matching
.txtnotes (such asslide_01.txt) and globalnotes.jsonornotes.toml. The planned folder and notes contract defines the direction; folder loading and notes layout are not implemented in the mock proof.
The hard reliability requirement is an acceptance gate, not an assertion that an OS, compositor, GPU or disconnected monitor cannot fail. Handle failures explicitly, keep presenter content private, and make output recovery possible without restarting or losing the selected slide. Do not silently demote an affected OS to unsupported.
Portable distribution is also mandatory: one launchable executable per target with all required non-system dependencies bundled. No runtime downloads, dependency installation or separately installed PDF backend. See implementation choices for static linking, embedded assets and clean-machine acceptance.
Completed foundation — 0.1.0
Independent workspace, source license, app/repository icon, agent instructions, Jenkins pipeline, badge helpers and tests. The presentation core has bounded zero-based navigation and audience blanking, with output initially blanked. The bootstrap established the initial CLI and tests. Native mock windows were added in 0.1.3, as described below.
Implemented display proof — 0.1.3
Dual-screen proof: two native mock windows, primary/secondary defaults, explicit display selection, swap, fullscreen and blanking controls. Tested locally on one Linux/X11 display; physical dual-screen acceptance on all three OSes remains pending. One-process prototype only; production isolation and sleep guards are not implemented.
Implementation work
The ordered task list owns implementation and completion tracking. Implementation choices specify the stack, process isolation, cache pipeline, keep-awake APIs and initial performance/recovery budgets.
Dependency count, build time and package size are not priorities. Fast startup, responsive controls and resilience are. Automatically inhibit idle display/system sleep during presentation, including blanked and paused output, to the extent the OS allows. Native integration and measured, reversible OS tuning are authorized.
Display acceptance gate
Record OS/version, window backend (including Linux X11/Wayland), GPU, monitor setup, app commit, reproduction, result and remaining defects. The user will provide physical testing; automated tests and headless CI do not establish this acceptance.
For each of Windows, macOS and Linux, verify explicit presenter and audience display selection, both role assignments, swap, fullscreen exit/re-entry, focus and keyboard navigation while both windows are active. Cover mixed DPI, differing resolutions, portrait orientation, negative desktop coordinates and primary-display changes. Exercise disconnect/reconnect, sleep/wake and missing saved displays. Never place notes or operator controls on the audience display as a fallback. Keep selection and blanking stable; report unavailable output and offer reassignment. With only one available display, offer rehearsal and explain that dual-screen output is unavailable. No unresolved hard-requirement failure is accepted as a finished implementation.
Speed acceptance gate
Use fixed synthetic and user-approved decks, with simple/vector-heavy/image-heavy pages, rotations and mixed sizes, plus large decks. Compare equivalent workloads against Pympress on the same machine, resolution and cache conditions when available. Record hardware, app/backend versions, deck SHA, display resolution, page count, cold versus warm cache and test method. Do not infer speed from language choice.
Measure time to first visible page, time to presentation-ready dual windows, and input-to-visible slide latency (median, p95 and worst case). Include rapid next/back, uncached random jumps, notes extraction and background cache work. Record peak RAM, GPU memory when measurable, disk-cache size and extraction time. Distinguish actual visible-output timing from CPU submission timing. Use the proposed numerical budgets in the implementation choices as initial engineering gates; validate them against reference hardware and user testing. No claims of "blazingly fast" acceptance without recorded measurements and user validation.
Scope after the core requirements
Mirroring either role onto several monitors and a windowed slide browser are now required presenter workflow (see the task list). Independent decks per display, remote control, annotations, embedded media and transitions are later scope. Native PPTX playback is not implied. No network service or presentation-switcher integration is required. Preserve source PDFs and never show a wrong or stale slide to achieve a lower latency measurement.