Skip to main content

bdinfo_rs_gui/
lib.rs

1//! bdinfo-rs desktop GUI — the library half.
2//!
3//! Holds the pure logic — the argv surface and attended-session evidence
4//! ([`args`]), the playlist view-model ([`model`]), the
5//! master-detail pane view-models ([`panes`]), the selection model (`selection`),
6//! the live-progress model ([`progress`]), the mid-scan measured cells
7//! ([`live`]), the flow state machine ([`flow`]),
8//! the copy-path helpers ([`paths`]), the clipboard sanitizer ([`clipboard`]),
9//! the column-weight math ([`columns`]), the persistent configuration
10//! ([`settings`]), the best-effort diagnostics log ([`diagnostics`]), the
11//! visual identity ([`theme`]),
12//! window-icon rendering ([`icon`]) with its Windows `.res` packer
13//! ([`winres`], shared with `build.rs`), and the scan seam ([`scan`]) — so the
14//! golden-tie + unit
15//! tests link them directly, and the `bdinfo-rs-gui` binary is the thin iced
16//! shell over this surface: it translates messages to calls here and
17//! results to widgets, holding no business logic of its own. The one impure thing
18//! the shell does is spawn the measured-scan worker thread and forward its
19//! progress over a channel.
20//!
21//! This crate is an INDEPENDENT workspace (see `Cargo.toml`) — the large
22//! iced/wgpu/winit tree stays out of the root gate — but it STAYS inside
23//! `forbid(unsafe_code)`: a native iced app needs no `unsafe` in our own code.
24#![forbid(unsafe_code)]
25
26pub mod args;
27pub mod clipboard;
28pub mod columns;
29pub mod diagnostics;
30pub mod flow;
31pub mod icon;
32pub mod live;
33pub mod model;
34pub mod panes;
35pub mod paths;
36pub mod progress;
37pub mod scan;
38pub mod settings;
39pub mod theme;
40pub mod winres;
41// Private: the binary drives selection only through `flow`, never this module
42// directly (so public-API docs reference it as a plain code span, not a link).
43mod selection;