Namespaces

One page for each documented namespace: what it holds, and a link to each class in it.

  • BaseTranscode: Number base conversion with arbitrary alphabets
  • ChatTables: Tables of a chat message: whole words in each cell, and a table wider than its bubble that scrolls sideways (trove-navigation TNX-41)
  • ChatTranscript: Forms of a whole chat conversation: HTML for the PDF, Markdown for the clipboard, and the paths of its pictures
  • Mustache: A renderer for Mustache templates
  • TimeGridRuler: Tiered wall-clock vertical time rulers for time-series plots (§CG-T)
  • agent: —
  • agent::client: Widgets that show an agent node to a remote or a hub
  • audio: 16-bit PCM conversions and the audio effects of libaudio
  • audio::effects: Audio effects that implement IAudioProcessor, such as reverb
  • bahn: —
  • bahn::settings: —
  • banter: Banter: data transfer between nodes over sound, through speakers and microphones
  • banter_bench: Options of the subcommands of the banter-bench tool
  • batch: Batch jobs: the queue, the workers that run the jobs, and the dispatcher between them
  • batchtasks: OPAL tasks of the batch queue, and what they may reach
  • catalog: Catalog: the registry of every addressable widget and scene, and the screenshots taken of them
  • catalog::capture: Wait for a model in a screenshot scene that renders through the real viewport producer
  • clockwork: Stored schedules, their time rules, and the engine that turns them into batch jobs (clockwork §CW-D)
  • clockworkopal: `clockwork.*` OPAL tasks: list, read, preview and change the node's stored schedules (clockwork §CW-D-13)
  • clockworkui: Page of the stored schedules in the Hub (clockwork §CW-D-14)
  • config: Settings engine: declarations, levels, stores and the resolver
  • config::testing: Fixtures for the tests of the settings engine and the settings window
  • config::ui: Settings page: the item model, the views, the page, the framed window and the config.* tasks
  • construct: Construct, the 3D CAD editor: the scene model, the renderer and the editor
  • construct::aa: Anti-aliasing strategies of the scene viewport
  • construct::asset: Assets of a scene: imported files, meshes and their field data
  • construct::bench: Scenes, options and jobs of the construct benchmarks
  • construct::camera: Where the camera and new reference images go in a construct scene
  • construct::cpupreview: Isolated CPU preview of a scene's field: a progressive point cloud in the parts' material colors, and a leg timer of its milestones (cpu-sdf-preview §CSP-A). Construct does not use it yet
  • construct::denoise: Denoisers of a path-traced picture: the à-trous filter and the Open Image Denoise network in our own compute shaders (rendering-revamp §RVR-7)
  • construct::diag: Diagnostics of the construct worker, such as its signal audit
  • construct::document: Open documents of construct, their change feed and their GUI-thread work
  • construct::engine: Tuning, cost model and probes of the SDF engine (construct-scene-evaluator)
  • construct::eval: Evaluators of the scene field: CPU, native and mesh, and the probes that check them
  • construct::lifecycle: Transitions of a construct scene: teardown, then load
  • construct::mesh: Triangle sources and sinks, and the filters, of mesh export from a construct scene
  • construct::model: Scene model of construct: the items, their views and editors, and their fields
  • construct::model::derived: Keys of an item's typeData that a run writes, and a person never edits (simulation-ux §SXD-1, §SXD-5)
  • construct::model::presentation: Presenters of an item: what it shows of its fields (field-presentation §FVE-1 to §FVE-5)
  • construct::native: Native code for the running process: in-process compilation with the vendored LLVM, loading, and cancellation
  • construct::opal: OPAL tasks that read and edit a construct scene
  • construct::ops: Operations on a construct document and their undo batches
  • construct::pathtrace: Path tracer of the construct viewport: the engine, its snapshot of the scene and its sample budget
  • construct::region: Regions of a construct scene, their fields, and what they select (construct-project-space)
  • construct::registry: Definitions of construct: the registry of the built-in, library and scene items, their sources and the user's library
  • construct::render: Renders of a scene to files: the render jobs and their settings, the scene renderer, the encoders and the file names
  • construct::rendering: Render pipeline of the construct viewport: environments, shading modes and the worker viewport
  • construct::selection: Caches of the selection and hover highlights of the viewport
  • construct::settings: Construct schema, its levels and its stores
  • construct::shader: Build of the SDF shaders: the forge, its recipes, its worker and its report
  • construct::studyseam: What a study reads of a construct scene: its geometry, its mesh and its regions
  • construct::ui: Widgets, windows and panels of the Construct editor
  • construct::viewer: Load of a scene into the construct viewer
  • construct::xport: Mesh export: the scene field baked to a mesh, post-processed and written to a file
  • construct::xport::results: Input keys of derived results, and the cache that follows the inputs (simulation-ux §SXD-2, §SXD-5)
  • contentview: How content is shown: viewers with one zoom model, shared by the lightbox, the file manager and the chat (lightbox spec §LBX-6)
  • cpppolicy: Allowlist of the cpp-policy check of lint
  • crosssweep: Runners of a cross sweep: on this machine, or in a Windows virtual machine
  • definitionpages: Reference pages of the Construct definitions in an export
  • dragmotor: Headless drag-to-value engine that DragBox and DragNumber share
  • dragnumberformat: Lays out one DragNumber value on a fixed column grid
  • eval: Expression system: GLSL expressions declared, compiled and evaluated
  • eval::gpu: Headless GPU compute of the evaluator: its configuration and its programs
  • eval::internal: Parts of libeval that the compile lanes share: values, slot layout, GLSL assembly and SPIR-V compilation
  • expredit: Shared expression editor and the expression compiler under it
  • face: Editor: a graph of nodes, connections and triangles, a spreadsheet of formulas, and their OPAL tasks
  • femjob: Load cases and the checks of a finite element solve job (construct-fea-solve §FEJ)
  • field: Field kernels, their catalog and engine, and the kept field sets of earlier solves (field-presentation)
  • field::gpu: GPU half of the field kernels and its probe
  • field::reduce: Reductions over a whole field, and their cache (field-presentation §FVK-6)
  • fixo: Fixo, the static firmware controller: presets compiled to firmware with LLVM, the runtime that drives it, and the activities that use it
  • fleet: Rented machines: providers, instance types, the fleet that owns them, and the hosts that run work on them (fleet)
  • fleet::gate: Gates of the fleet: each buys a machine, runs a check there, and puts everything back
  • fleetui: Fleet page of the Hub and its OPAL tasks
  • help: Browser, its pages and the help.* tasks
  • inventory: What a node knows of its hardware: its devices, its load and its health (work-placement §WPN-9)
  • inventory::probe: Probes that measure a node's hardware, such as the throughput of its cores
  • kiln: Build system of the tree: its plans, its broker protocol, its runs and its tests (kiln)
  • kiln::kit: Writer of the kiln kit
  • kiln::opal: OPAL tasks of kiln: build progress, the queue, storage and the announcements
  • kiln::qtconf: Configuration of a Qt build that kiln makes from the machine it runs on
  • kiln::remote: Announcement board of remote kiln builds (§KA-R)
  • kilnui: Kiln activity: the broker's queue, cache, checks and storage, drawn with the monitor's charts
  • kilnui::testing: Scripted broker snapshots, so that a test can drive the kiln activity with no broker
  • launch: Node-free start of an application (app-composition W8)
  • libname: Name generation for the identities of nodes
  • lightbox: Modal lightbox: the overlay, the input it blocks, show() and open() (lightbox spec §LBX-5)
  • lint: Checks of the lint tool, and the runner that gives each check its files (script-ports §SCP-D-2)
  • llm_opal: —
  • llvmglue: Project's own code inside libllvm: what every in-process LLVM user shares
  • markdown: —
  • media: Framework that audio and video share: devices, processing graphs, encoders and the audio engine
  • media::devices: Multimedia device enumeration, caching and matching
  • media::encoder: Video codecs that this platform can encode, found by a live test and cached
  • media::graph: A generic processing graph: nodes, connections, buffers, jobs and the schedule that runs them
  • mesh: Meshes: their fields, their processing, spatial search and topology
  • mesh::field: Solution fields of a mesh, their axes, units and extremes (field-presentation §FVD)
  • mesh::process: Processing of meshes: feature detection, parallel loops and the improvement of tet volumes
  • mesh::spatial: Spatial search in meshes: box trees and point locators (field-presentation §FVS)
  • mesh::topology: Of triangle meshes, such as vertex fans
  • monitor: Resource monitor: the processes and threads of this machine, sampled, grouped and watched for runaways
  • monitor::testing: Scripted samples, so that a test can drive the monitor with no real process table
  • nodekit: A composable node: the kit, its features, and the scope each feature installs in (work-placement §WPK-2)
  • nodesettings: Node schema and its host: the settings of Hub, Agent and Remote
  • numex: Numex serial protocol, shared by the host and the firmware
  • oc_crypt: Thin C++ wrappers around the crypto primitives: hashes, ciphers, key derivation, random numbers, RSA and EC keys, and Ed25519
  • octomy: Root namespace of the newer libraries
  • octomy::activity: Framework: one screen of an application, its context and its markers
  • octomy::apidocs: Units of the apidocs host tool: what QDoc may read, derived from the tree
  • octomy::crypt: Cryptographic concepts and seals of the applications
  • octomy::header: Plain navigation header of a window, with no node (§ACW-7.1)
  • octomy::hive: Swarm status chip of the window header and the state it shows
  • octomy::hub: Settings schemas of the Hub's apps
  • octomy::llm: LLM providers of the app: the drivers, the sessions and the wire formats of the online providers
  • octomy::llm::wire: Formats of the online LLM providers, as pure functions (llm-openai-compatible §OCP-W2)
  • octomy::llm::wire::anthropic: Anthropic's Messages API, as pure functions (llm-openai-compatible §OCP-W1, §OCP-W2)
  • octomy::llm::wire::openai: OpenAI Chat Completions form, as pure functions (llm-openai-compatible §OCP-W2)
  • octomy::llmsession: Runs LLM sessions and records them: the session store, the Claude Code stream transport, the runner and the transcript import
  • octomy::llmsession::opal: Session.* OPAL tasks over the session store and the runner
  • octomy::localdoor: One door per user per host: its address, its file, its server and its client
  • octomy::lockstep: Engine: the turns, the commands of the players and the simulation it drives
  • octomy::log: Color of the terminal copy of a log line
  • octomy::opal: Newer parts of the OPAL task system: task families and the chat host
  • octomy::opal::ui: OPAL chat surface of a window
  • octomy::opalnet: OPAL calls and batch control between nodes, carried over comms
  • octomy::pair: Bridges that carry the pairing state of a node through an activity context
  • octomy::rts: Deterministic real-time strategy game: its simulation, content, computer opponent, networked matches and screens
  • octomy::splash: Screens of the windows
  • octomy::standalone: Host glue that runs an app with no node: harness, window, context and its facilities
  • octomy::swarmui: Swarm screens of a node, and the swarm schema
  • octomy::trove: Trove: specs as a database, with its settings schema
  • octomy::trove::door: Host of the trove: the one door of a user and host, its sessions and its tasks
  • octomy::trove::driver: Claude Code side of a session: the files in its working folder and the models it can use
  • octomy::trove::fleet: Trove side of the fleet: node capabilities and fleet tasks
  • octomy::trove::git: Named worktrees of one git checkout, and the lease of each one to one holder
  • octomy::trove::lane: Lanes of a trove project: the lane manager, and the notifier that tells each view when a lane or a job changes
  • octomy::trove::opal: OPAL tasks of the trove
  • octomy::trove::recurring: Recurring specs: their probes, the engine of their runs, and the host and lander of the HUB (trove-recurring)
  • octomy::trove::specdb: Spec database of the trove
  • octomy::trove::ui: Widgets of the trove board: the project and lane cards, and the views of a session
  • octomy::trove::workspace: Tabs of the trove board: the spec workspace, the files workspace and the trove chat
  • octomy::window: Window-features that any QMainWindow composes: the stack, the header, the prompts, the geometry, the raise, the shutdown and the watermark (app-composition §ACW-7, §ACW-8)
  • opal: OPAL task system: tasks, plans, the runtime, and the call that runs a function on the GUI thread
  • opal::attachment: Material that a session grants to OPAL, and the registry of the grants
  • opal::filekind: Kinds of file that task families can show to the model, matched by suffix
  • opal::vision: Surfaces OPAL can look at, and the tasks that capture them (opal-vision)
  • opal::web: Web.fetch task of OPAL, its limits and its downloads (opal-web-reference)
  • opal_bench: Options of the subcommands of the opal-bench tool
  • paint: Spectral paint engine: paint documents of layers and frames, brushes, and the file format
  • paint::settings: Paint schema, and the one resolver that reads and writes it
  • plan: —
  • plan::editor: Plan editor widget
  • platform: Wrappers for what differs per system and Qt does not cover, and the pure parsers they are built on
  • platform::associations: File associations of the desktop
  • platform::crash: Sentinel and its link to an application (diagnostic-reports §DGK-4)
  • platform::diagnostics: Diagnostics of a running process, such as the stack of another thread
  • platform::filesystem: File stamps and folder watches, as the platform reports them
  • platform::hardware: Of the machine: processors, caches, memory, drives and the network link
  • platform::shell: Other programs that open a file: the system's list, a start of one of them, and the system's own chooser (construct-viewer §VWO-2)
  • platform::spawn: Start of child processes and the job trees that hold them
  • platform::system: What the system says of this machine and process: processor, control group memory and thread times
  • platform::terminal: Of the standard error stream, and the color conventions of the environment
  • polyhedra: Polyhedra and their published data, such as the Johnson solids
  • qhttp: An HTTP server and client on Qt sockets, built on http_parser
  • qhttp::client: HTTP client: the connection, the request it sends and the response it reads
  • qhttp::server: HTTP server: the listener, its connections, and their requests and responses
  • qmapcontrol: Map widget: tile providers, map layers and the geometries drawn on them
  • raybench: Ray-marching benchmark: its composer, its field probe and its records
  • referencework: A fixed piece of work, and a speed budget that holds under any load
  • resourcecheck: Check that each Qt resource path in the source is declared in a .qrc file, and that each static library registers its .qrc files
  • rhi: Project's layer over Qt RHI: device selection, device loss, pipelines and render budgets
  • shader: Runtime shader compilation: baking GLSL, the on-disk artifact cache, DXIL for Direct3D, and SPIR-V linking
  • sing: Singularity, the singing game: its sessions, scores, audio and settings
  • sing::settings: Of singularity, and the store that keeps them
  • spir: SPIR-V loader, its type model and the reference interpreter
  • study: Studies: the evaluation of a model graph at design points, and where the points run (construct-project-space)
  • study::opal: OPAL tasks of studies
  • study::ui: Study composer: its graph editor and graph host
  • style: Colors and colormaps of the user interface
  • syntax: One tokenizer per language, for the terminal and for the widgets
  • system_load: —
  • system_tasks: —
  • test: Shared helpers of the test suites
  • test::image: Comparison of images in tests, and reference images kept as fixtures
  • test::scale: Timing helpers for the scale tests of the tree
  • test::source: Scans of the source tree that tests make
  • toast: Notifications: transient toasts, inline notice cards and window confirmations
  • toolchain: Builds and caches the compiler components that native and firmware builds compile against
  • utility: Small helpers that every library can use: strings, files, time, graphics, IDs, processes and more
  • utility::color: Color utilities, such as the quality check of a colormap
  • utility::concurrent: Concurrency utilities, such as the count of the jobs an object has in flight
  • utility::graphics: 2D image, palette, and pixel-manipulation utilities
  • utility::process: Environment and the arguments of child processes
  • utility::random: Reproducible random sequences
  • utility::time: Time, duration, and rate utilities
  • utility::ui: Labels tied to points in 3D, and their layout (field-presentation §FVL)
  • video: Video capture, frame conversion, video processing and camera roles
  • watermark: Embedding and detecting a keyed watermark in a triangle mesh
  • widgets: Reusable widgets of the user interface
  • widgets::graph: Shared interaction of node-graph editors: the canvas, its style and its host
In this section