egui Weave
Accessible components, modern layout ergonomics, and UI-system tooling for egui applications using Taffy.
egui Weave is an immediate-mode integration layer. It keeps widgets, interaction, painting, focus, and responses in egui; keeps intrinsic measurement and the Taffy lifecycle in egui_taffy; and keeps Block, Flexbox, and Grid algorithms in Taffy.
The crate owns a smaller missing contract:
- ergonomic Box, Row, Column, and Grid composition;
- semantic component recipes and themes;
- keyboard and accessibility behavior;
- deterministic container breakpoints;
- layout/pass inspection and regression tests.
It does not provide a DOM, CSS parser, retained widget tree, renderer, state framework, or replacement layout engine.
use ;
Compatibility
The initial implementation intentionally pins the compatible dependency line:
| egui Weave | egui | egui_taffy |
Taffy | Rust | Verified hosts |
|---|---|---|---|---|---|
| 0.1.x | 0.35.x | 0.13.x | 0.9.x | 1.92+ | eframe 0.35, headless egui_kittest 0.35, any host supplying a normal egui::Ui |
The dependency contract remains the exact egui 0.35.0 / egui_taffy 0.13.0 pair.
An isolated package upgrade to egui 0.36.1 / egui_taffy 0.14.0 passes the core tests;
it requires Rust 1.95 and is an upgrade exercise, not a second supported dependency line.
Run the proof
cargo run --example settings_gallery
cargo run -p weave-data-browser -- applications/data-browser/data/sample.csv
bash scripts/check.sh
python3 scripts/check-performance.py
python3 scripts/check-upgrade.py
The gallery can switch the same demanding settings surface between direct egui_taffy and the
Weave facade. It also exposes every component, semantic variant, theme, density, breakpoint, zoom,
font scale, representative edge states, and the read-only layout inspector.
Status
The core and tooling are implemented, with two Codebase settings migrations on an integration
branch and a functional, separately themed CSV application. Application-owned component geometry,
live AccessKit inspection, evidence-linked coverage checks, and executable performance budgets are
present. This is a pre-1.0 candidate, not a claim of production adoption or stability. See
docs/milestone-status.md for the evidence and blockers,
docs/usage.md for integration boundaries, and
docs/customization.md for application styling.
The source checkout also contains the original design in notes/spec.md and the second app in
applications/data-browser; these are not part of the registry library package.