Diego Chagas 235e7578f3 Print through CUPS over IPP and the print portal, so File › Print works in the Flatpak (#2728) (#3017) ... Main prints through craft-print, which runs `lp`; a Flatpak has no `lp`, so File › Print fails there. This keeps craft-print as the route wherever `lp` is on the path (and on Windows) and adds two more behind it: - `photocraft-ipp`, a pure-Rust IPP client (CUPS-Get-Printers/Classes/ Default, Print-Job over HTTP/1.1) that talks to CUPS over its socket or TCP; the Flatpak manifests grant --socket=cups for it. A `printServer` named in the request always takes this route. `file.print.printers` lists the queues. - The XDG Print portal as the app's spooler (`Session::print_spooler`), for a sandbox without the CUPS socket or a system without a printer: the system print dialog, seeded with copies, paper and orientation. PHOTOCRAFT_PRINT_PORTAL=1 prefers it, =0 removes it. A route that exists but fails (unknown printer, refused job) is an error; only a missing route moves on. Results gain `backend` (lp, windows, ipp, portal). docs/printing.md describes the routes.		2026-10-17 15:55:54 -06:00
..
photocraft	Print through CUPS over IPP and the print portal, so File › Print works in the Flatpak (#2728) (#3017)	2026-10-17 15:55:54 -06:00
photocraft-cli	docs(cli): write product name as PhotoCraft in USAGE and description (#5449)	2026-10-16 16:56:48 -06:00
photocraft-web	Web: Place Embedded and canvas drops place images (#5749) (#5817)	2026-10-17 13:20:44 -07:00
photocraft-web-boot	CI: fix the tests that keep main red, and ship the wasm as compressed parts (#5926, #5302) (#5941)	2026-10-15 09:21:30 +02:00