Expand description
Browser build of indicatrix: open a faceting design (a self-contained
.isdd file (or a legacy .indicatrix), .asc, .gem,
.gcs), keep it in the shared indicatrix_editor::EditorSession, and save it
back as a browser download. See README.md for what works today and what the
later phases add.
§Modules
-
app: the oneapp::state::WebApp(in anRc<RefCell<..>>), the entry point, callback wiring, thepush_*UI refresh, persistence tosessionStorage, the solve (tiny designs on the page, the rest in the solve Worker), diagnostics. -
io: file input (picker + drag-and-drop), per-kind loaders, the HDR cap, and file output (Blobdownloads). -
render: the CPU-worker live render loop, its settings panel, the PNG export and the viewport-size tracking. -
workers: the one lazily created Worker pool (render Workers + solve Worker, and the analysis Worker on first use). -
metrics: the Render tab’s gemological-metrics HUD and the Tilt Performance dialog, both computed in the analysis Worker. -
views: the Solid and Diagram tabs. -
editor: the CAD panels of the Design dock – the tier table, its command bar and editing actions, and the unsaved-changes dialog.
§Why everything is #[cfg(target_arch = "wasm32")]
This crate exists for one target: it drives a Slint UI through wasm-bindgen
and reads files through the DOM. A native build compiles to nothing, so
cargo check --workspace on a native host costs the desktop apps nothing.
Pure logic that deserves native tests lives in the shared crates instead
(indicatrix-editor’s files module, for one).