storytold main 83cb1133dd (291 commits) into the integration head bab1a99b85; 47 conflicted files.
- Domain test files (metafile, prepress, pdf plates, settings store, heif, media-testkit, atomic): tests next cut stay cut; tests new on main are kept, as trials where the crate's test target runs trials.
- atomic: main's group-bits test and Faulty::set_group go to src/tests.rs. audio: main's GSM and SBC oracles join tests/main.rs. cms constructors, pdf knockout_backdrop and testing_pdf join their crates' one test binary; timeline's preflight tests become src/preflight_tests.rs trials.
- update: main's changes to detect, install (linux, macos) and the tests land in next's split modules. The app's own offer is inspected on a thread of its own, picked up by tick's polling; settle_for_tests settles offers too. Later on a ready update drops the close it asked for. updater_pin_tests.rs stays deleted; its new pin test is in tests/it/update.rs.
- craft-color: main added a different crate at crates/color (the colour tags of compositor and display frames); it is next's craft-color module `tags`, re-exported at the root.
- Old crates/ui (combo, docking, testing, README) and keymap's ui/view.rs stay deleted; main's new crates/ui/src/testing files are dropped with them.
- New crates in the craft facade: ai, control, dds, frame, ipc, media-source, palette, press-print, score, ssip. testkit and xtask are listed outside it.
- Cargo.lock: the union of both locks, resolved by cargo metadata. Workflow: main's nextest Windows leg, with next's --keep-going clippy.
craft
The craft libraries in one dependency. An app pins one revision of this crate and turns on features; everything is imported as craft::<crate>.
[workspace.dependencies]
craft = { git = "https://github.com/storytold/craft-libs", rev = "…" }
# crates/ui-egui/Cargo.toml
craft = { workspace = true, features = ["ui", "color", "draw", "imaging", "keymap", "platform-appearance"] }
Always on
craft::theme, craft::i18n, craft::host.
Features
- One feature per crate, named after the crate without
craft-:colorturns oncraft-colorand re-exports it ascraft::color. uiturns oncraft-ui(craft::ui), re-exportsegui(craft::egui, the egui the library is built with) and forwardsuito every enabled crate.screen-testingimpliesuiand forwards to every enabled crate.- Each crate feature is forwarded as
<crate>-<feature>(platform-appearance,text-hyphen,ui-window-frame). - A crate whose
uineeds another family'suiturns that family's feature on (drawturns oncolor).
The [features] table in Cargo.toml is written by tests/features.rs from the member crates' manifests. After changing a member's features or adding a crate, run UPDATE_FACADE=1 cargo test -p craft -- integration::features and commit the result. A comment on a feature line marks a crate that does not build for wasm32-unknown-unknown.
Reached through other crates, not named in the facade: the six library crates (craft-ui-contract to craft-ui-shell), craft-ui-macros and craft-behavior through craft-ui, and craft-win32 through craft-window.
Not in the facade, because they are tools or test harnesses: craft-ui-gallery, story-render, feature-root (the features local builds resolve with), craft-ui-bench, craft-ui-test-kit, craft-fonts-build (a build-script helper), craft-design-lint, craft-plate-test, craft-media-testkit, craft-render-parity.
Family dependencies
tests/families.rs fails when one family crate's ui depends on another family crate's ui. craft-color is the base family that any family may use.
egui fork
craft::egui_fork::{GIT, REV} name the egui fork the library is built with, and check_lockfile(lock) checks that an app's Cargo.lock takes every egui package from it. An app's xtask calls it in its ci and check commands. The app's workspace must also patch egui to this fork, since [patch] applies only at the workspace root.