PPTX reporter
Documentation · Changelog · Visual walkthrough · Report formats
Create video timing reports from a PowerPoint presentation using the desktop app or CLI. Python and PowerPoint are not required for the Rust application. For a walkthrough with screenshots, see the user guide.
cargo run --locked --bin pptx-reporter-gui
cargo run --locked --bin pptx-reporter -- presentation.pptx --timings-only --report all
cargo run --locked --bin pptx-reporter -- presentation.pptx --extract-only
Drop PPTX files or a folder into the window, choose multiple presentations, or use Choose folder…. Check the save location, choose extraction/report mode, select formats, then use the purple action button. The Setup tab contains inputs, output location, mode, and common formats. More formats… offers every format and presets: Reading & printing selects HTML, PDF and compact PDF; Defaults selects Markdown and Ontime. Settings contains video replacement and FFprobe location controls. The action/progress bar stays visible at the bottom. Successful runs open Results, with file actions and collapsible diagnostics. The default window is 760 × 560; long input/result lists scroll within their panes. The app remembers options and the last eight presentations. Completed files can be opened directly or their paths copied.
Progress estimates apply to the current counted phase. Cancel interrupts FFprobe and stops between steps; an active PDF compilation finishes first. Activity & diagnostics retains warnings and details.
Files and dependencies
Output defaults to <presentation>_videos/, with videos/ and reports/
subfolders. Reports are regenerated; extracted videos are reused unless
--overwrite is selected. Empty presentations create no output.
HTML, Markdown, plain text, JSON, Typst, PDF, compact PDF and Ontime are supported. Durations account for per-shape trims. Loops and unsupported timing stay visible in reports but are omitted from Ontime and playback totals. Extracted media remains unchanged. See report options and semantics.
PDF compilation and fonts are embedded; no Typst installation or package
downloads are needed. FFprobe is discovered beside the app, in its bin/
subfolder, or on PATH. Override with --ffprobe PATH or Settings in the GUI.
On Windows, extract the whole portable ZIP and launch pptx-reporter-gui.exe.
pptx-reporter.exe provides the CLI and opens the GUI when given no arguments.
Linux desktop builds need windowing/OpenGL libraries at runtime.
See development for source checks and releases for Cross builds, packaging and dependency provenance.
Batches and video folders
# Multiple presentations: sorted by filename regardless of argument order
pptx-reporter B.pptx A.pptx --timings-only --report ontime,json -o show-timings
# All PPTX files and video subfolders directly inside a folder
pptx-reporter ./show --timings-only --report ontime,json
# A single folder of videos, treated as one presentation
pptx-reporter ./clips --timings-only --report all
Each run creates one combined set of reports. In Ontime, batches have one named
group per presentation or video folder in a continuous rundown. Import
reports/timings.ontime.json once, then set the first cue’s start time. Groups
with no eligible cues are omitted. The export follows Ontime’s
group import structure. Original local slide numbers are retained;
source names prefix video names in combined reports. JSON includes groups
with zero-based start (inclusive) and end (exclusive) playback indices.
A video folder uses each supported video’s full duration as one slide, in
natural filename order: media2 precedes media10, and media 2 precedes
media 10. This default also applies to presentations and subfolders in a batch,
and media names within the same PowerPoint slide. PowerPoint slide order is
preserved. Text remains case-sensitive; equal numeric values use the original
filename as a deterministic tie-breaker (for example, media02 before media2). Non-video files are ignored. Supported extensions:
MP4, M4V, MOV, AVI, WMV, WebM, MPG, MPEG, MKV, ASF, 3GP and TS.
PowerPoint trims still apply to PPTX inputs; plain video files have no PowerPoint
trim or looping metadata. These are video timings, not slide-transition timings.
A parent folder includes its immediate PPTX files and immediate subfolders that
contain videos. Deeper folders are not traversed. A folder mixing loose videos
with presentations is rejected: select the inputs separately to make the order
explicit. Duplicate input paths are processed once. Legacy .ppt files are not
supported; save them as .pptx first.
The default output remains <first-input>_videos/ (use -o to choose a batch
location). Copied/extracted batch media lives in numbered 001/videos/,
002/videos/, … directories to avoid filename collisions. --timings-only
reads source videos directly and extracts PPTX media only temporarily.
--extract-only copies/extracts media without reports. Existing media is reused
unless --overwrite is set; keep input selection/order stable when reusing a
batch output folder, or choose a fresh output folder. Source files are preserved.
PPTX Reporter user guide
The desktop app turns PowerPoint videos and video folders into timing reports. The Windows GUI has been confirmed working by the project owner. Screenshots below show the compact interface running on Linux with a sample video folder; window borders, file dialogs and path separators differ on Windows.
1. Open a presentation
On Windows, extract the whole portable ZIP and launch
pptx-reporter-gui.exe. Keep ffprobe.exe beside it. No Python, PowerPoint or
Typst installation is needed.
On Setup, drop PPTX files or a folder anywhere in the window, or use
PPTX files… / Folder…. Recent… reopens a previous input; Enter a
path lets you type a path. The input list uses natural filename order, so
media2 comes before media10. Long lists scroll within their own area.
The default window is 760 × 560. Setup and Results stay at the top; the action button, progress and Cancel stay at the bottom. At smaller sizes or with enlarged text, the active pane can scroll without hiding those controls.
2. Choose what to create
Check the selected inputs and Save to path. Use Change… for another destination, type into the output field, or use Use default to reset it. Hover a shortened filename or path to see its full value.
| Mode | Result |
|---|---|
| Extract + reports | Save embedded videos and generate reports |
| Reports only | Generate reports without keeping newly extracted videos |
| Extract only | Save videos without generating reports |
Ontime, PDF and Markdown checkboxes are on Setup. More formats… opens all formats and presets. For easy reading, choose Reading & printing: it selects Web page, PDF and Compact PDF. Add Ontime if you need a rundown import. Defaults selects Markdown and Ontime; All selects every format. Individual checkboxes let you adjust any selection.
The example below uses Reports only, with PDF, Markdown and Ontime selected.
Click the purple action button. Its label follows your mode: Generate reports, Extract videos, or Extract & generate reports.
3. Open your results
During processing, the app shows the current step and progress where measurable. Time estimates apply to that phase. Cancel stops between steps and interrupts FFprobe; an active PDF compilation finishes before stopping.
After successful completion, the app switches to Results. Click Open beside a report or Open output folder. Copy path copies a file’s location, not its contents. Results scroll independently of the bottom action bar. Activity & diagnostics contains warnings and detailed progress messages. You can switch tabs during a run; input and format controls stay disabled until it finishes. Errors remain visible in the bottom bar.
The default output is beside your presentation:
Showcase_videos/
├── reports/ timing reports and editable Typst sources
└── videos/ extracted media, when requested
The .typ files are editable PDF sources; open .pdf for normal reading.
Existing reports are regenerated. Existing videos are reused unless Settings
→ Replace existing extracted or copied videos is enabled. The source PPTX is preserved.
A presentation with no embedded videos produces no new reports. Settings
also contains the FFprobe location override.
4. Read the timings
Reports follow slide order. Durations account for PowerPoint start/end trims; trim details appear under the media name. A Looping marker identifies a video without a usable finite playback duration. Loops and unsupported timing are excluded from playback totals and Ontime. Extracted videos remain untrimmed.
Compact PDF keeps the slide, media name and duration in a portrait layout. Here is the top of the sample report:
To use the rundown, import timings.ontime.json into Ontime 4 via
Editor → Project → Manage projects. This is different from timings.json,
which contains general report metadata. See Ontime details
for skipped events and choosing your show start time.
If something needs attention
- FFprobe cannot be found: keep the bundled executable beside the app, or select it under Settings → FFprobe → Locate….
- Generate is disabled: choose a presentation and at least one report format, or select Extract only.
- A warning or failure appears: expand Activity & diagnostics for details.
- A report will not open: use Open output folder and open it with an installed PDF reader or browser. Ontime JSON needs to be imported into Ontime.
For CLI options and exact playback semantics, see Reporter and Report options.
Report formats and timing semantics
Use the Rust CLI below, or see the illustrated desktop guide.
Run source commands from the repository root. With a prebuilt CLI, replace
cargo run --locked --bin pptx-reporter -- with pptx-reporter (or
pptx-reporter.exe on Windows). The Python reporter has been retired.
Extract videos and create Markdown and Ontime timing reports:
cargo run --locked --bin pptx-reporter -- presentation.pptx
Generate one or more report formats without keeping newly extracted videos:
cargo run --locked --bin pptx-reporter -- presentation.pptx --timings-only --report html,pdf
cargo run --locked --bin pptx-reporter -- presentation.pptx --report all
--report accepts comma-separated formats and can be repeated. Markdown and
Ontime are included by default; an explicit --report replaces this selection.
Use --report all for every format, including both built-in PDF layouts
and Ontime.
The output root is <presentation-stem>_videos, or the directory supplied with
-o. Extracted media goes in videos/; all reports and Typst sources go in
reports/:
presentation_videos/
├── videos/
│ └── media1.mp4
└── reports/
├── timings.md
└── timings.ontime.json
Markdown and HTML links point to ../videos/; JSON extracted_file paths are
relative to the report directory too. --timings-only reuses media in videos/
when available, otherwise probes temporary copies without creating that folder.
--extract-only creates no report folder.
PDF uses the embedded Typst engine and retains timings.typ
for editing. HTML and Typst/PDF include colored summary cards and pills;
Markdown and TXT use aligned tables. JSON includes numeric durations in seconds,
sizes in bytes, and slide references.
For a compact portrait PDF with slide numbers, media names, and duration pills:
cargo run --locked --bin pptx-reporter -- presentation.pptx --timings-only --report pdf-dense
This creates timings-dense.pdf and its editable timings-dense.typ source.
It has a discreet title containing the presentation name and no summary cards.
Slide numbers and media names are plain text; durations and loop markers use pills.
Trimmed videos show a discreet line under the media name with the amounts removed
from the start and end. Looping videos carry an amber Looping pill next to
their name and a dash instead of a finite duration.
Use --report pdf,pdf-dense to produce both layouts.
Timings require ffprobe (from FFmpeg); PDF generation needs no external CLI. Use --extract-only to extract without a report. Presentations with no
embedded videos produce no output.
Playback durations and trimming
Reports list each video occurrence separately, in slide order. Reusing a media file on another slide, or in two shapes on one slide, can produce different durations. Media size and embedded-video counts still count each file once.
Duration is the single-play duration after PowerPoint’s start and end trims.
The full reports also show Original duration and Playback status.
HTML and both PDF layouts show start/end trim details below the media name and
an amber Looping pill for repeated playback. Markdown and TXT include the
trim details in the Playback column.
pdf-dense retains its three columns; its duration pill shows a status when
there is no usable duration.
- PowerPoint’s end trim is the amount removed from the end, not an end timestamp: a 10-second clip with 1 second trimmed from the start and 2 from the end plays for 7 seconds.
- Repeats show Looping. Custom speed, reverse playback, conditional endings, finite animation duration caps, and playback across slides show Custom timing. These are not simulated and have no effective duration.
- Invalid trim values show Invalid trim. Unknown source durations remain Unknown. No duration is invented.
- The duration total adds known effective playback durations, once per occurrence. Loops and unsupported/invalid timing contribute nothing.
- This is playback length once started, not total time spent on a slide. Click-to-start waits, slide transitions, and interactive animation sequences are not evaluated. Extracted media files are unchanged.
JSON retains file-level metadata under videos, with per-occurrence settings,
trim offsets, original/effective durations, status, and diagnostic notes under
playbacks. total_duration_seconds totals effective occurrences;
total_media_duration_seconds retains the original once-per-file total.
Implementation references: Microsoft’s media trim definition, time-offset units, and animation timing properties.
Ontime import
cargo run --locked --bin pptx-reporter -- presentation.pptx --timings-only --report ontime
This writes timings.ontime.json, a native Ontime 4 project. It is separate
from timings.json, which remains the general metadata report.
Import it through Editor → Project → Manage projects. To bring the rundown
into an existing project, import the file and use Partial Load.
See Ontime’s import instructions.
- Each supported video occurrence becomes an event, sorted by slide. Reused media and multiple video shapes on the same slide get distinct events.
- Event cues contain the slide number, titles contain filenames, and notes identify the presentation and archive media path.
- Durations apply PowerPoint trims and retain milliseconds. Starts are linked, beginning at midnight; change the first playable event’s start to your show time after import.
- Loops, unsupported playback timing, and invalid trims are completely omitted. Unknown source durations use zero and are marked skipped with a review note. Unreferenced videos appear last and are also skipped. Durations exceeding Ontime’s 23:59:59 limit require manual review.
- No automatic playback or external-media downloads are configured. Slides without embedded videos are not included. Add speaking time manually.
The export was checked against Ontime 4’s native project-section parsers; Ontime 3 is not supported by this export schema.
Progress output
Interactive terminals show a single animated progress line with completed video
count, elapsed time, and the current extraction/probing/report step. It clears
when finished, leaving report paths, the final summary, and warnings/errors.
Long operations keep animating. Redirecting either output stream uses ordinary
line logs instead. NO_COLOR disables colors; TERM=dumb also disables animation.
Batch and folder inputs
Multiple PPTX files, folders of videos, and folders containing PPTX files or video subfolders use the same timing and report rules. Batches produce one combined export with named Ontime groups, ordered by filename. See batch examples and folder rules.
Cross builds and portable releases
Run commands from the repository root. The primary release workflow is the
rust_realease named bundle described below. The standalone packager remains
available for manual/offline packaging until native acceptance tests are complete. Cross needs Docker or Podman;
Cross.toml selects Windows GNU x64 and Linux GNU x64 images. Jenkins does not
run release builds or publish releases.
cross build --locked -p pptx-reporter --release --target x86_64-pc-windows-gnu
cross build --locked -p pptx-reporter --release --target x86_64-unknown-linux-gnu
python3 scripts/package-portable.py --target x86_64-pc-windows-gnu --fetch-ffprobe
python3 scripts/package-portable.py --target x86_64-unknown-linux-gnu --fetch-ffprobe
The packager reads target/<target>/release/ and produces a Windows ZIP or Linux
.tar.gz in dist/, plus a SHA-256 checksum. Each includes GUI and CLI binaries,
FFprobe, licenses/provenance and quick-start instructions. Existing archives
are protected; use --output DIR for a new test build.
FFprobe
scripts/fetch_ffprobe.py downloads FFmpeg-Builds 9.0 release-branch, non-shared
LGPL builds. It verifies GitHub’s archive SHA-256, executable format and x86-64
architecture, then tests ffprobe -version on a matching host. Foreign binaries
are inspected without execution. Verified binaries/notices are cached in
ignored downloads/ffprobe/; no FFprobe binary is committed.
The default upstream latest tag moves. Pin repeatable builds with
--ffprobe-release TAG --ffprobe-sha256 HASH. Provenance records release/asset
IDs, download URL and digest. Cached files are checked on reuse, but online
metadata verification still requires GitHub access.
For offline packaging or another provider:
python3 scripts/package-portable.py --target x86_64-pc-windows-gnu \
--ffprobe /path/to/ffprobe.exe --ffprobe-licenses /path/to/notices
Review upstream platform requirements and distribution notices for the selected build. Test Windows launch, drag/drop, file dialogs, scaling, Unicode paths and opening reports on a Windows machine; cross-compilation alone cannot verify them.
Release automation
Root Cargo.toml → workspace.package.version is authoritative. The reporter
inherits it; its manifest contains cargo-binstall metadata. rust-release.toml
configures targets and named bundles for
rust_realease:
rust_realease . --package pptx-reporter --dry-run
rust_realease . --package pptx-reporter --compile-only
Publication needs a clean checkout and a matching explicitly created/pushed
version tag. The existing local v0.1.0 marks the original trial, not subsequent
changes; do not move it implicitly.
The portable named bundle adds Windows/macOS ZIPs and a Linux .tgz, containing both
Cargo binaries, adjacent FFprobe, quick-start instructions and licenses. Canonical
cargo-binstall .tgz archives remain unchanged and require external FFprobe.
Python 3.11+ is required on the build host only.
The protocol-1 hook scripts/prepare-release.py uses the publisher’s output and
cache directories, copies FFprobe/notices and emits a hashed file manifest. It
never guesses Cargo output paths or creates archives. The publisher handles
archive validation, checksums and upload. See the upstream
named-bundle contract.
crates/pptx-reporter/ffprobe-pins.json pins a dated FFmpeg-Builds release, exact non-shared
LGPL 9.0 asset name and published SHA-256 digest per Windows/Linux target. Dated assets have
versioned names, unlike the downloader’s default latest assets. To update,
review the provider release and its notices, then update all three fields together.
These dated releases are not marked immutable by GitHub; digest verification
fails closed if an asset changes. Pinned cached binaries and notices are rechecked locally before any network access;
unpinned downloads still refresh upstream metadata.
rust_realease . --package pptx-reporter --target x86_64-unknown-linux-gnu --compile-only
Dry-run validates static configuration without downloads. Compile-only prepares
and packages bundles without a token, tag creation, push or publication. After a
successful invocation, read dist/latest-artifacts.json; resolve its manifest
and checksums paths relative to dist/. Resolve assets relative to the resulting
artifact-manifest.json directory and verify SHA256SUMS. Do not guess build paths.
Before publication, extract both portable trees. On Linux, generate a report using adjacent FFprobe without relying on PATH. On Windows, launch the GUI and generate a report without separately installed FFmpeg or Python. Cross compilation and fixture tests do not replace native acceptance tests. Keep the standalone packager until those checks are complete. Jenkins remains checks/coverage/badges only.
macOS
Release builds include aarch64-apple-darwin (Apple Silicon) and
x86_64-apple-darwin (Intel), with macOS 13.0 as the minimum. Choose the
portable ZIP for your Mac. It contains pptx-reporter, pptx-reporter-gui,
FFprobe, notices and a quick-start guide. Extract the entire archive, then run
./pptx-reporter-gui in Terminal, or:
./pptx-reporter presentation.pptx --report all
Keep FFprobe beside the applications. No separate FFmpeg, Python, PowerPoint or PDF compiler is needed. The smaller canonical cargo-binstall TGZs contain only the reporter applications and still require external FFprobe.
These are separate architecture-specific executables, not universal binaries
or Finder .app bundles. They are not Developer ID signed or notarized.
If macOS blocks a trusted release, open Terminal in the extracted folder:
xattr -d com.apple.quarantine pptx-reporter pptx-reporter-gui ffprobe
chmod +x pptx-reporter pptx-reporter-gui ffprobe
./pptx-reporter-gui
An attribute-not-found message means that file is already unquarantined. Native startup, file dialogs, drag/drop, report generation and Gatekeeper behavior still require testing on compatible Macs.
Bundled macOS FFprobe
scripts/build_macos_ffprobe.py builds FFprobe from the exact official source
archive and SHA-256 pinned per Mac target in ffprobe-pins.json. It uses the
same digest-pinned cargo-zigbuild image as the reporter, enables local file
probing, and disables network input and external codec-library autodetection.
It does not enable GPL or nonfree components. The dependency is a separate
LGPL executable with statically linked FFmpeg libraries and only macOS system
libraries loaded dynamically.
The source build needs Linux, Python 3.11+, and Podman or Docker (selected via
CROSS_CONTAINER_ENGINE, or Podman if available). The image must be available
to the engine. Compilation runs with container networking disabled; downloading
the pinned source occurs first on the host. First preparation can take several
minutes. The cache identity covers the source pin, target, image and recipe;
reused payloads have their hashes and Mach-O compatibility checked. A warm
cache needs no dependency download.
Each Mac portable ZIP includes the complete FFmpeg source archive, LGPL license,
reproduction scripts and BUILDING.txt under LICENSES/ffmpeg/. The dependency
validator checks the CPU, macOS minimum and system-only library paths without
running foreign binaries. The publisher must include Mach-O support for named
bundle executables, in addition to its existing macOS build support.
On the Linux release host, the same publisher routes Apple targets through the
digest-pinned cargo-zigbuild image in [build.apple]; Cross remains responsible
for Windows/Linux. No host Xcode or Darwin Cross image is used.
The image pin, SDK path and deployment minimum are explicit in
rust-release.toml. See the upstream
automated macOS workflow.
# Validate the complete four-target release configuration.
rust_realease . --package pptx-reporter --dry-run
# Build/package just the two macOS architectures, without publication.
rust_realease . --package pptx-reporter \
--target aarch64-apple-darwin --target x86_64-apple-darwin --compile-only
# Build/package the complete release, including Windows/Linux portable bundles.
rust_realease . --package pptx-reporter --compile-only
Review SHA256SUMS and archive executable modes, including the bundled FFprobe. The publisher checks Mach-O
architecture, the exact macOS deployment minimum and system-only dynamic
dependencies. Foreign cargo-binstall checks install files without executing
them; macOS runtime validation is explicitly skipped on Linux.
Publish the complete configured matrix together so its checksum manifest covers
all platforms.
The release configuration uploads that matrix to both Gitea and GitHub. Provide
GITEA_TOKEN and GITHUB_TOKEN, or use --token-file with an untracked JSON
object whose gitea and github keys contain the corresponding tokens.
Application artwork
PPTX Reporter embeds its PNG window icon and Windows ICO resource, including CLI-only Windows builds. Linux/FreeBSD X11 uses the window icon; Wayland desktops match the app ID to its desktop entry. macOS uses the ICNS resource in an app bundle. A bare Unix executable has no Finder/application-menu icon.
The crate keeps app-icon-source.png, app-icon.png, app-icon.ico and
app-icon.icns under crates/pptx-reporter/assets/.
Builds consume committed derivatives and need no image tools. To regenerate the
256px PNG, seven-size ICO (16–256px), and ICNS (128–1024px), install ImageMagick 7
and run python3 scripts/build-icons.py from the repository root.
Desktop launchers
After building or extracting a release, create a launcher pointing to the binary at its permanent location. The helper refuses existing launchers/icons. Linux/BSD launchers reference the original executable and stop working if it moves. macOS bundles copy the binary and adjacent LICENSES directory. Reporter bundles also copy an adjacent FFprobe (requiring its LICENSES directory); otherwise FFprobe must be on PATH. Recreate macOS bundles after updating binaries.
# Linux / FreeBSD: install into your desktop's user application directory.
python3 scripts/create-desktop-launcher.py pptx-reporter \
--binary "$PWD/target/release/pptx-reporter-gui" --output "$HOME/.local/share"
# macOS: create a Finder/Dock launcher (run on the Mac).
python3 scripts/create-desktop-launcher.py pptx-reporter --platform macos \
--binary "$PWD/target/release/pptx-reporter-gui" --output "$HOME/Applications"
Portable archives include the helper, its supporting module, and the icon
formats, so these commands also work from an extracted archive. Respect
XDG_DATA_HOME instead of ~/.local/share when
customized. Desktop menus may need a refresh. Windows executables have embedded
icons; shortcuts inherit those icons.
Launcher output is described in the desktop launcher contract. Automated checks validate icon containers and launcher output on Linux. Finder, Dock, Windows Explorer/taskbar and individual Wayland desktop behavior still need native visual checks. The macOS launchers are not signed or notarized.
Development
PPTX Reporter is a Rust workspace with one application crate. The crate exposes
the shared reporting core plus pptx-reporter and pptx-reporter-gui binaries.
Install a current Rust toolchain and run from the repository root:
cargo fmt --all --check
cargo clippy --locked --workspace --all-targets --all-features -- -D warnings
cargo test --locked --workspace --all-features
RUSTDOCFLAGS="-D warnings" cargo doc --locked --workspace --all-features --no-deps
python3 -m unittest discover -s tests -v
cargo build --locked -p pptx-reporter --no-default-features builds the CLI
without desktop or PDF features. Ordinary builds include both. FFprobe is a
runtime dependency for reading media metadata; packaging scripts download only
checksum-pinned builds and keep them outside Git.
See CI and coverage and cross builds and releases for the automated validation and portable packaging workflows.
PPTX Reporter changelog
v0.7.0 — 2026-11-21
-
Publish the first standalone Idle release with portable desktop packages for Windows, Linux, Apple Silicon macOS and Intel macOS.
-
Make the GUI the primary download and README workflow while retaining the CLI inside each portable package for optional automation.
-
Refresh the pinned Windows and Linux FFprobe archives and accept the provider’s current GitHub organisation URL after its repository move.
-
Publish future release assets to both Gitea and GitHub from one build, with separate named credentials for each service.
-
Move PPTX Reporter from the Beffroi tools workspace into its own Idle-owned repository with standalone build, packaging, documentation and CI support.
-
Store new desktop preferences under the Idle application namespace while reading the former Beffroi settings location as a compatibility fallback.
-
Preserve the application icon generation prompt with the standalone project.
-
Rewrite the project README as an illustrated, task-oriented quick start for desktop users, with installation, output selection, results and troubleshooting.
-
Update the shared Rust application version to 0.7.0; see the release notes.
-
Add direct links to the published mdBook manual from the project README, tool guide and documentation indexes.
-
Add an mdBook manual built from the existing guides, with local assets and downloads. Jenkins publishes successful main builds under
/mnt/books/manuals/; staging, link validation and scoped publication have regression coverage. -
Use absolute Gitea main-branch URLs for repository file links in the root README; verify linked files exist.
v0.6.0 — 2026-11-14
-
Synchronize the shared Cargo package version with the v0.6.0 milestone tag; see the release notes.
-
Group the guide and supporting documentation in this tool’s folder; update portal, cross-document and packaging links for the new paths.
-
Add ImageGen application artwork in PNG, Windows ICO and macOS ICNS formats. Embed native icons and support Linux/BSD desktop entries and macOS app launchers; native Windows/macOS visual checks remain required.
2026-11-03
b1ddf39: Compact GUI with tabs and a fixed action bar.