|
|
Donner SVG 0.8.0-pre
SVG editor and embeddable C++20 engine.
|
Status: Implemented. Donner provides an on-demand showcase sample and the editor operations needed to create the release showcase interactively. Final styling and screen recording happen in a live editor session rather than being frozen into a checked-in derived SVG. Author: unknown (historical provenance debt) Drafted by: unknown (historical provenance debt) Reviewed by: GPT-5.6 Sol Related: Editor Architecture, Editor Design Language, Structured Source Editing, v0.8 Showcase Demo Checklist
The v0.8 showcase demonstrates Donner editing its own splash artwork. The repository keeps the original donner_splash.svg as its single canonical root asset. Derived showcase SVGs are created on demand and stay in memory or at a caller-selected temporary path.
The built-in generated sample is a reproducible starting point and regression fixture, not the final art direction. The release showcase is performed live in Donner Editor, styled during that session, and screen recorded. This keeps visual decisions in the interactive authoring workflow while retaining an automated smoke path for CI.
GenerateShowcaseAsset parses the canonical splash, adds an SVG text label through structured document edits, converts it with convertTextToOutlines, and exports the current viewport with ExportViewportAsSvg. The generated result contains static outline paths and a <g id="donner-editor-overlay"> selection overlay.
EditorSampleCatalog invokes the in-memory generator when the catalog is first accessed, so the Donner Showcase sample does not depend on a committed derivative. The //donner/editor/tools:generate_showcase_asset command exposes the same operation for temporary files and automation.
The interactive workflow remains the release-facing path: open donner_splash.svg, make the desired artwork and styling changes with editor tools, convert final text to outlines when appropriate, frame the composition, and record the live editor session. The generated sample does not constrain that composition or styling.
The v0.8 Showcase Demo Checklist separates the automated reproduction from the live, operator-directed showcase recording. The Editor Architecture documents runtime ownership and mutation paths, while Structured Source Editing documents how DOM changes remain synchronized with source.
See the v0.8 showcase retrospective for review findings and remaining release actions. The original design and implementation plan remain available in git history.