ui Directory Reference

Directories
	testing

Files
	agent.hpp
	alignment.hpp
	morph::ui::Align and morph::ui::Justify: where a container places its children across its axis and along it. The view tree, the authoring API and the backends share them. Specified in docs/spec/ui/backend_contract.md, "The cross axis".
	author.hpp
	Server-side authoring of UI documents (spec 5 §11): typed builders that write a screen's JSON, and the registration that validates it once — loadDocument with the builders' catalog facts, then the accessibility rules.
	author_forms.hpp
	backend.hpp
	The backend contract: the retained widgets a mount drives, and the factory that makes them.
	bundle.hpp
	What the UI service's client and server share (spec 5 §12): content hashes, the bundle's manifest, and the bodies of the ui-hello, ui-catalog and ui-fetch envelopes, with their bounds and their parsers.
	button_emphasis.hpp
	morph::ui::ButtonEmphasis: how much a button stands out. The view tree, the authoring API and the backends share it. Specified in docs/spec/ui/backend_contract.md.
	button_style.hpp
	morph::ui::ButtonStyle: whether a button is drawn as a push button or as an entry of a list. The view tree, the authoring API and the backends share it. Specified in docs/spec/ui/backend_contract.md.
	catalogue.hpp
	Message catalogues (spec 6 §19): a bundle's messages files read into a TranslationProvider that t resolves through, and the search that matches a title in every locale the bundle has.
	dev_reload.hpp
	Development reload (spec 5 §12): which documents a changed bundle changed, and remounting the mounted screens that show them, keeping their state.
	dev_tools.hpp
	morph::ui::DevelopmentTools: whether a client runs in development mode (spec 6 §21). The tools are in every build; this decides at run time whether they are on. Specified in docs/spec/ui/inspector.md.
	document.hpp
	The UI document (spec 5 §3): its model — declarations, commands, view nodes, components and customization points — and loadDocument, which parses a document and runs its load-time validation.
	explorer.hpp
	The app explorer: what a morph application is made of — its screens, the models they use with every action, and for one action its facts, its fields, the places that use it and the widget the framework builds for it, mounted live.
	expression.hpp
	The expr/1 expression language of the UI document: parsing a JSON expression into an Expr tree, checking it against the names a document declares, and evaluating it.
	file_store.hpp
	The file side channel's store (files/1, spec 6 §18): uploads in chunks, and files a principal may read by a capability reference.
	frontend.hpp
	The frontend seam: main picks a frontend at runtime, and the frontend runs whatever an AppSource opens.
	host.hpp
	The host contract (spec 6 §4): how a host mounts UI documents and closes them, whether it owns its own shell or is the framework's workspace shell, and DocumentScreenHost, the framework's host over documents.
	host_vocabulary.hpp
	HostVocabulary: the commands and values only the client application has (host/1, spec 6 §14), registered with their types and versions, run with checked arguments behind a trust gate, and declared to the server in ui-hello.
	inspector.hpp
	morph::ui::Inspector: the development inspector's read-only view of a mounted screen (spec 6 §21).
	interpreter.hpp
	The UI document interpreter: Interpreter::mount turns a loaded Document into reactive state and a view tree, mounts it through Mounted on any IViewBackend, and runs its queries, mutations, relations and commands. Model calls go through a Dispatcher (the bridge's model-free seams in an application, a scripted fake in a test); what only the application can do goes through an InterpreterHost; what screens share — the query cache, the principal's permissions, the formatting facts — is a Session.
	message.hpp
	The MessageFormat 2 subset ui/1 accepts for t(key, fallback, args), and the CLDR plural rules its .match on a :number selects by.
	mount.hpp
	morph::ui::Mounted: builds a view tree's widgets through a backend once, and keeps them current through reactive bindings.
	navigator.hpp
	The workspace's navigator and pins (spec 6 §7): the catalog listed by module and group, searched by title, with the person's pinned shortcuts.
	preference_sync.hpp
	PreferenceSync: the client side of the preferences model. It loads a mounted screen's stored choices into Screen::setPreference, and writes what InterpreterHost::preferenceChanged and resetPrefs report.
	preferences.hpp
	Per-person storage of customization choices (spec 5 §12b, spec 6 §8): the IPreferencesStore seam, the framework's in-memory store, and the server's preferences model, which keys every entry by the person the verified session names.
	queueing_dispatcher.hpp
	route.hpp
	Routes (spec 6 §20): the string form of a screen instance, <screen id>?<param>=<value>&…, written from a screen's declared params and read back against them.
	route_history.hpp
	Route history (spec 3 §10, spec 6 §20): the route of the screen a shell shows, kept in a history the user moves through with back and forward, such as a browser's.
	service.hpp
	The server side of the UI service (spec 5 §12, §12b, §13): UiRegistry collects an application's screens and files and builds a ServedBundle; UiService answers ui-hello, ui-catalog and ui-fetch from it as a RemoteServer envelope service.
	service_client.hpp
	The client side of the UI service (spec 5 §12, "Content addressing"): UiClient runs ui-hello, ui-catalog and ui-fetch over a transport the caller supplies, verifies every file against the manifest and the manifest against the ui-hello digest, and keeps what it verified in a VerifiedCache.
	shell_frame.hpp
	morph::ui::ShellFrame: the frame a client shows its screens in — a sidebar with the navigator, a top bar, and the page the workspace's tabs sit on. Built from backend widgets, so every frontend shows it.
	theme.hpp
	Theme tokens (ui-theme/1, spec 6 §6): DTCG 2025.10 token files read and checked, layered into a variant, their aliases resolved, and the closed ui-theme/1 set filled from them with its defaults. No toolkit: the Qt Quick renderer applies the result (qt_quick::applyTheme).
	value.hpp
	The UI document's typed values (ui::Value), its types (ui::Type), their JSON form, and ui::Refusal, the error every load-time check of the document layer returns.
	view.hpp
	The toolkit-agnostic view tree: props, node kinds and their builders.
	workspace.hpp
	The workspace shell (spec 6 §7, §15): tabs over screens, mounted through a DocumentScreenHost.
	workspace_model.hpp
	The workspace's tab logic with no widgets (spec 6 §7, §15): what an application's own tab strip binds to, and what ui::Workspace draws as a tab bar.