Files
x ad31cfbafa Vendor flare-ui v0.2.9 and prove the schema-driven UI in an image
Spike, not the final UI: it answers whether flare-ui can drive Alkane OS's
on-box pages, and what it costs.

What works:

- schema/alkane-bb.json authors the sidebar as data (3 sections, 14 tabs);
- src/bin/ui-spike.rs renders it through flare_ui::nav + flare_ui::shell, so
  the unified sidebar, ordering and surface filtering come from the schema
  rather than from hand-written HTML;
- the render uses the shared bf- design tokens, the same ones the rest of the
  suite uses.

Size, measured rather than assumed (armv7, release, stripped):

  ui-baseline   323 KiB   (maud + serde_json, no flare-ui)
  ui-spike      771 KiB   (flare-ui + wschema + sha2)
  marginal      448 KiB

Vendoring: third-party/flare-ui is the full v0.2.9 tree pinned in
flare-ui/flare-ui.lock (a partial archive does not compile, since the crate
include_str!s assets from dash-editor/). vendor/ is re-generated as a cargo
directory source with the new registry dependencies (maud, sha2, typenum,
digest, generic-array, block-buffer, crypto-common, cfg-if, etc.) so the build
still works offline. third-party/README.md records how to re-pin.
2026-11-04 14:06:25 -06:00

1.3 KiB

Third-party sources

Code we consume that is not on crates.io. Both entries are pinned, and both are vendored rather than fetched so an image build works with no network.

flare-ui

flare-ui/ is a full checkout of the flare-ui tag recorded in flare-ui/flare-ui.lock (repo, tag, commit). It is used as path dependencies:

flare-ui = { path = "third-party/flare-ui/crates/flare-ui" }
wschema  = { path = "third-party/flare-ui/crates/wschema" }

The whole tree is vendored, not just crates/, because the crate embeds assets from dash-editor/ with include_str! and will not compile from a partial archive.

Updating the pin:

git archive <new-tag> | tar -x -C third-party/flare-ui   # from a flare-ui checkout
cargo vendor vendor                                       # refresh registry deps

vendor/ is a cargo directory source (see .cargo/config.toml), so every registry dependency flare-ui needs - maud, sha2, typenum, digest and the rest - must be re-vendored or the build fails offline.

Size

ci/check-ui-size.sh builds two binaries for armv7 with the same profile: one renders through flare-ui, one renders the same shape with maud alone. The difference is the marginal cost. Measured 2026-11-03, release, stripped:

ui-baseline   323 KiB
ui-spike      771 KiB
marginal      448 KiB