This repo contains libraries used by the various Craft Apps. It's a Rust monorepo workspace, and the libraries can be included by any Craft Apps that need them.

In the future this may grow to include non-Rust library code.

If any libraries grow beyond Craft App usage, eg. RAW format support, they may be promoted out and into their own libraries for the broader ecosystem to take advantage of.

Layout

A Cargo workspace (edition 2024, resolver 3). Each library is a crate under crates/<name>, named craft-<name>, with version, edition, license and repository inherited from the workspace (license.workspace = true, and so on) and [lints] workspace = true. Register each crate in [workspace.dependencies] in the root Cargo.toml.

Use a released version

The first coordinated release is v0.1.0. It gives consumers a fixed baseline while development continues on main. All five crates share this version. They require Rust 1.95 or later; the UI integrations use egui 0.36.

Add only the crates you need, using the same tag for every craft-libs dependency:

[dependencies]
craft-ui = { git = "https://github.com/storytold/craft-libs", tag = "v0.1.0" }
craft-settings = { git = "https://github.com/storytold/craft-libs", tag = "v0.1.0" }
# Optional, for egui close handling and the macOS application menu:
craft-quit = { git = "https://github.com/storytold/craft-libs", tag = "v0.1.0", features = ["menu"] }

craft-atomic and craft-print use the same dependency syntax. Enable craft-ui's serde feature if you need to serialize its docking layout. These are Git releases; crates.io publication is deferred.

Release tags are never moved or reused. For a commit pin, resolve the tag with git ls-remote https://github.com/storytold/craft-libs 'refs/tags/v0.1.0^{}' and replace tag = "v0.1.0" with rev = "<full commit SHA>" on every craft-libs dependency. Use either tag or rev, not both. An existing commit pin keeps working; switching to this release may require adapting to changes since that commit.

Commit your application's Cargo.lock and build with cargo build --locked for reproducible Rust dependency resolution. A Git pin fixes craft-libs source, not every transitive dependency. A library's own lockfile does not constrain its downstream consumers. Upgrade deliberately: read the release notes, update all craft-libs pins together, refresh the lockfile with cargo check, and run your application's tests and affected workflows before committing.

See the release notes for included functionality and known limits, and the versioning policy for compatibility guarantees and release checks.

Libraries

craft-atomic: Crash-safe atomic file writing and replacement with same-directory staging, directory fsync, Apple F_FULLFSYNC fallback, transient lock backoff, and fault injection for the Craft suite.
craft-print: PDF submission to CUPS and Windows, printer discovery, duplex/copies/colour and driver preferences. PDF generation stays in each app.
craft-quit: native macOS quit, egui close handling and an optional app menu. Unsaved-document decisions and save prompts stay in each app.
craft-settings: config.toml settings storage for every app: platform folders, portable mode and overrides, atomic saves while running, backup, damaged-file recovery and schema migrations. Policy in docs/settings-storage.md.
craft-ui: SVG catalogs, icon buttons, tabs, pane controls, transactional docking, print settings and theme helpers for egui frontends; assets, themes, localization and command handling stay in each app. Requires Rust 1.95 or later.
Shared UI component audit: source inventory, extraction priorities and compatibility boundaries across the Craft suite.
Theme infrastructure: eight-app comparison and the small shared widget-state styling boundary.
Panel docking: validated panel moves, floating groups, workspace adapters and an optional egui docking surface.

License and credits

Bundled fonts, icons, images and other assets keep their own open licenses; each one is listed with its author, source and license in ATTRIBUTION.md.