Lutra/docs/development.md
danny f49b42836a F2: ui.screenshot captures the webview without focusing the window
On Windows the webview renders itself into a PNG through WebView2
CapturePreview (scheduled on the main thread via with_webview, 10 s
timeout, PNG signature and 64 MiB cap checked). macOS and Linux keep the
xcap screen-region capture as a documented fallback, now without focusing.
app.focus is the only control method that changes focus. A --control
instance opens its window without taking the foreground. An ignored live
test samples the foreground window while the app starts and takes five
screenshots and fails if Lutra ever owns it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 17:13:38 +01:00

2 KiB
Raw Blame History

Development

Status: draft · Last updated: 2026-10-14

Prerequisites

  • Rust stable (via rustup), edition 2024
  • Node.js 22.12 or newer (Vite 8 needs it) and pnpm 10
  • Tauri 2 system prerequisites for your platform (WebView2 on Windows, WebKitGTK on Linux)
  • Optional: Phpactor on the PATH for language features, PHP 8.2+ and Composer for reference projects

Everyday commands

cargo xtask dev        # run the app in development mode
cargo xtask dev -- --control 7979 .   # with the JSON control channel
cargo xtask ci         # the full quality gate, run before every commit
cargo xtask fixtures   # create Symfony and Laravel reference projects in target/fixtures/

A --control PORT instance keeps its settings, recovery journal and webview data in <temp>/lutra-control/<port>/, never in your own data directory; --data-dir DIR or LUTRA_DATA_DIR=DIR pick another directory. Delete the folder to start fresh. Its window opens without taking the foreground, and ui.screenshot never focuses it; only app.focus does. To check that on Windows, build with --features bundled-ui and run LUTRA_DESKTOP_EXE=<target>/debug/lutra-desktop.exe LUTRA_CONTROL_PORT=<port> cargo test -p lutra-desktop --test screenshot_focus -- --ignored.

Robustness: Lutra never crashes

Shipped code returns errors instead of panicking (see AGENTS.md › Never crash). The engine guard catches panics at every entry point, keeps buffers intact and reports an internal error. Unsaved buffers are journaled so a restart can restore them.

Code style

No inline comments. Doc comment blocks above modules, functions, types and fields explain purpose, parameters, return values and errors.

Revision history

Date Change Summary
2026-10-27 minor Unfocused --control windows and the screenshot focus check (F2)
2026-10-25 minor Isolated data directory for --control instances (H6)
2026-10-14 minor Node.js 22.12+ required by the frontend toolchain
2026-10-13 major Initial draft