Module application
Expand description
Checked application construction shared by hosts, independent of any runner.
Modules§
- registry
- The applications a multi-app host can mount, registered once per process.
Structs§
- AppComponent
- Real app content and its lifetime; hosts cannot extract an unbound root.
- Application
Catalog - Application
Definition - Application
Host - Capture
- What a host prepares an instance for when it renders a screenshot
(
--shots,--shots-dir,--responsive-matrix) rather than a window someone uses: the app shows a deterministic scene from fixtures and starts nothing that reaches outside the process. - Component
Behaviour - How the window hosting a component treats its tree. Part of the component, so every host that runs it applies the same behaviour.
- Component
Close Report - Component
Replacement - A component an app built to show another record in the place of the one
it shows now, and the launch that names that record (the path a person
chose to open). The host closes the current component and mounts this
one in the same window (
AppComponent::take_replacement), then answers the request (Self::into_parts). - Component
Runner Inputs - Presentation owned by a runner. Authority comes only from the component context.
- Host
Context - Explicit identity, authority and storage. Apps receive no ambient profile resolver.
- Host
Context Inputs - Host-supplied storage, identity and authority for one instance, checked by
HostContext::preparebefore any factory runs. - Launch
Option - One of an app’s own command-line options a launch named:
--purpose numbercarries a value, a switch such as--debug-hit-areasnone. - Native
Process Host - The host inputs a normal application process receives from the trusted launcher. Storage and presentation identity are resolved once, before an application factory is allowed to open a record.
- Native
Profile - One app’s launcher-owned profile in one room, opened by the trusted
host from outside the app’s sandbox: the same store, device identity and
storage workspace
NativeProcessHostresolves inside it. The shell uses it to carry a window’s record and presentation to another room (crate::record::transfer); it grants nothing the app itself lacks. - Open
File - One file to open: its name, media type and bytes.
- Open
File Receipt - What the host keeps of an
OpenFileit handed over: which resource the component opened it as, once the component says so. - Playback
Handoff - Where playback stood on the device or app that handed the launch’s media over: the launch continues it from there. The media itself is what the launch names (its argument or file); this is the transport and the name it played under.
- Prepared
Component Inputs - Explicit host preparation completed before invoking the application factory.
- Reopener
- What a component needs to open another record of its app in its own
window: the same store, identity, authority and services as the record
it shows, for another record. Taken from the
HostContextbefore the factory consumes it (HostContext::reopener). - Replacement
Outcome - What became of a request to show another record in a window: nothing yet, shown, or refused with the reason. The host answers before it closes the asking component and polls the operation that asked, so that operation can be answered from it; a refusal leaves the component open to tell the person on its next frame.
Enums§
- Launch
Target - Restore
Input - Window
Role - What a component’s window is to the session.
Constants§
- ANY_
MEDIA_ TYPE - The entry of
ApplicationDefinition::opensthat opens files of every type. - MAX_
OPEN_ FILE_ BYTES - The largest file a host may hand a component (128 MiB).