Skip to content
Project referenceDevelopmentEngine ccf7d03f
Authored
  • Explicit UI backend identities, providers and deterministic product composition.

This host-layer project lets a product select an available retained UI implementation by identity. It does not own a global backend singleton, scan arbitrary directories, or choose a fallback implementation.

UiBackendCatalog receives composition-owned providers and validates their identities before exposing a frozen selection. Null providers and duplicate identities are rejected. Selecting an unavailable backend throws NotSupportedException; a provider returning null is an invalid implementation.

UiBackendProvider.CreateBackend returns a caller-owned backend. Transfer that responsibility to the runtime that will dispose it, or dispose it at the composing boundary if construction cannot continue. The catalog itself does not dispose providers supplied by its caller.

Identity describes implementation selection; it is not a document handle or a renderer choice. A product must still arrange source-language compatibility, Native deployment and a consumer for render frames.

Read UI lifetimes and RmlUi backend requirements. Ordinary scripts use the selected UI service, not this composition API.

Browse types and exact member contracts.

Project: Inno.Adapter.UI
Source: src/adapters/ui/Inno.Adapter.UI/Inno.Adapter.UI.csproj

Type API Description
IUiBackendFactory engine Creates isolated UI backends without exposing implementation assemblies to composition code.
UiBackendCatalog engine Resolves UI providers from one immutable composition-owned registration snapshot.
UiBackendId engine Identifies a UI implementation independently from its document language.
UiBackendProvider engine Creates one concrete UI backend registered by a composition root.