Files
solvecraft/docs/architecture.md
jyviko 312454f899 Look: SolidCraft's icons, glyphs, UI fonts and themes as the shared crate solidcraft-look (follows #14251) (#14578)
* UI kit: an icon set can extend another host's masters with a host's own

IconSet::extended(data, extension) draws another host's IconData (the same
static tables, not a copy) with an IconExtension of the host's own masters,
aliases and default accents, in the data's colour roles and accents. For a
name both have the extension's master, alias or default accent wins.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtL5M2MmcDrkcWhQeHS2K8

* Look: SolidCraft's icons, glyphs, UI fonts and built-in themes are the shared crate solidcraft-look

The icon masters and their build step, the code-drawn glyph painters, the UI fonts and the
built-in themes move into crates/look with history. SolidCraft's app installs its look from
the crate, as another app can. The workspace tab table stays the app's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtL5M2MmcDrkcWhQeHS2K8

* Look: the end-cap icons' attribution rows and the style guide's path follow the move

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtL5M2MmcDrkcWhQeHS2K8

* Licence: SolidCraft's brand and interface are under LICENSE-BRAND

The UI kit, the look (interface icons, glyphs, built-in themes), the theme's tokens and palettes,
and the SolidCraft name, logo, app icon and brand kit are SolidCraft's brand. They may be used,
changed and contributed to as part of SolidCraft; using them in another program or product needs
the maintainers' written permission. Geometry and the rest of the code stay MIT OR Apache-2.0,
and third-party fonts keep their own licences.

The three crates declare the licence with `license-file`, which `xtask shared` now accepts when
the file sits inside the crate; the generated licence list names it; ATTRIBUTION rows for the
look's artwork and the branding name it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DtL5M2MmcDrkcWhQeHS2K8

---------

Co-authored-by: jyviko <2501648+jyviko@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-10 09:06:00 -05:00

2.3 KiB

Architecture

Layer Crates Role
L0 geom vectors, planes, profiles, meshes and their measures
L1 sketch, kernel, render, dynamics constraint solver and profiles; the B-rep kernel boundary (the vendored solidcore); product rendering (render jobs and their backends) on the shared viewport renderer; multibody dynamics (rigid bodies, joints, forces, time integration)
L2 doc parameters, expressions, the feature timeline and its incremental evaluation
L3 io design files, STL/OBJ/STEP/3MF export, STEP and 3MF/STL/OBJ/glTF import features
L4 engine the session and the command registry (everything is a command)
L5 gpu, ui-egui, mcp the GPU path tracer and SolidCraft's GPU environment over the shared viewport renderer; the swappable desktop front end; SolidCraft's MCP tools (headless or bridged to the app) over the shared mcp-server
shared color, ui-registry, ui-text, theme, ui-kit, look, mcp-server, control, control-egui, viewport, viewport-gpu, viewport-egui crates other front ends use: they depend only on other shared crates, solidcore and external crates (UI toolkits included), any crate may use them, and cargo xtask shared builds and tests each one on its own. The viewport renderer is three: viewport (camera, pictures, CPU rasterizer, shading), viewport-gpu (its wgpu pipelines and plan evaluation) and viewport-egui (the viewport in an egui window). The UI kit (ui-kit) holds the tokenised controls and the components built from them (ribbon, app bar, history and navigation bars, view compass, preferences window, start page, window chrome, theme files), drawn from data the host installs or passes. SolidCraft's look (look: its icon masters and colour roles, code-drawn glyphs, IBM Plex faces and built-in themes) is a shared crate too, so SolidCraft and other hosts install the one copy. A crate below L5 reaches no UI toolkit or wgpu through them, or any other way: cargo xtask layers follows workspace dependencies to check it
apps solidcraft, solidcraft-cli desktop app, headless CLI

How the layers, the shared crates and the solidcore seam fit together, with what enforces each rule: layers.md.