93aeb26027
The first pass only proved the Tauri capture pipeline against the
default landing view ("About"). All 24 real sidebar sections are wired
up now (every id in lib/sidebar.ts has a real component in
lib/views/registry.ts — no Placeholder fallbacks to skip).
Since there's no URL/route per section (activePage is plain Svelte
$state, switched by the sidebar's own click handler), the frontend now
also listens for a screenshot-set-view Tauri event in +page.svelte's
onMount and sets activePage from its payload — the same effect a real
sidebar click has, just driven from the Rust side. screenshot.rs emits
that event after the initial page-load settle delay, then waits a
second settle delay for the newly-active view's own Tauri-command data
fetch to land before capturing (each section fetches its own state on
mount, same as the About page's system-info fetch needed 2s in the
first pass).
|
||
|---|---|---|
| .forgejo/workflows | ||
| frontend | ||
| packaging | ||
| src | ||
| .gitignore | ||
| bakery.toml | ||
| LICENSE | ||
| README.md | ||
bos-settings
System settings app for BOS (Bread Operating System) — GTK4, configures every bread* app's config plus core system settings (network, sound, power, users, firewall, snapshots, packages, AUR, firmware, Hyprland display/appearance/autostart) non-destructively.
Split out of the bos repo into its own repo so a bos-settings release doesn't require a BOS ISO release, and vice versa. Distributed via bakery — see bread-ecosystem's CONTRIBUTING.md for the dev/beta/stable track workflow shared across the bread ecosystem.
Building
cargo build --release
Packaging / releasing
Bump Cargo.toml's version, tag vX.Y.Z, push the tag to both remotes — .forgejo/workflows/release.yml builds and publishes to dl.breadway.dev (bakery) automatically. Pushes to dev/beta publish a dev/beta-track build the same way, no tag needed.