omar/panopainter
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add explicit PPI project writer

Browse Source
This commit is contained in:
omigamedev
2026-06-02 11:05:08 +02:00
parent 1bc90d88b4
commit b3710498f3
6 changed files with 262 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/modernization/build-inventory.md
View File

@@ -120,11 +120,12 @@ Known local toolchain state:
frame counts, durations, and decoded face-pixel payloads when present; the
metadata-only minimal fixture remains covered by
`pano_cli_load_project_metadata_smoke`.
- `pano_cli save-project` writes generated multi-layer, multi-frame PPI files
with configurable layer opacity, blend mode, alpha lock, and visibility
through `pp_assets`; test dirty-face payloads can target explicit generated
layer/frame slots. It is covered by `pano_cli_save_project_roundtrip_smoke`
and `pano_cli_save_project_payload_roundtrip_smoke`, which reload generated
- `pp_assets::create_ppi_project` writes generated multi-layer, multi-frame
PPI files with explicit per-layer names, opacity, blend mode, alpha lock,
visibility, per-layer frame durations, and targeted dirty-face layer/frame
payloads. `pano_cli save-project` exposes that path for automation and is
covered by `pano_cli_save_project_roundtrip_smoke` and
`pano_cli_save_project_payload_roundtrip_smoke`, which reload generated
metadata-only and targeted dirty-face-payload projects through
`pano_cli load-project`.
- `pano_cli create-document` supports `--frames` and `--frame-duration-ms` and