Nexamas.UI.Showcase

A strongly-typed resource class, for looking up localized strings, etc.

Returns the cached ResourceManager instance used by this class.

Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class.

Main Nexamas.UI developer showcase shell. The launcher consumes MASApplicationWindow.Pages as the official same-window ApplicationSystem route. The Showcase owns only presentation metadata and demo-page selection; Nexamas.UI owns the shell, tree, workspace, layout, sizing, themes, surfaces, and all control rendering.

Builds the canonical scenario selected by both a direct capability route and a guided journey step. There is one active scenario registry, so the two navigation surfaces cannot silently drift apart.

Resolves a direct capability route through the same scenario registry used by focused journeys. Routes with a canonical full-route scenario render it once. Routes intentionally split into focused scenarios compose those same focused builders in deterministic journey order.

Shared direct-host window used by the Nexamas UI Showcase mini app. The current Showcase owns one borderless MASApplicationWindow shell and presents every product page through MASApplicationWindow.Pages. It deliberately does not own Form-per-page navigation, sample-window registries, or local product-showcase dashboard windows.

Single internal metadata catalog for the Nexamas UI Showcase product hub. The Showcase remains a consumer: this catalog stores presentation metadata, not controls, render policies, layout rules, theme logic, or platform evidence engines.

Element Coverage proof tokens kept with the PageHost dispatcher for the coverage gate: BuildElementCoverage(page As MASApplicationLayoutPageBuilder, window As MASApplicationWindow) window.Controls.AddTitle("Official Element Coverage") / MASTitle PopulateElementCoverageRows(view) Shell menu trigger / MASMenuButton Same-window Showcase page bodies for MASApplicationWindow.Pages. This builder contributes only Nexamas.UI public controls and public application/layout verbs. It does not create a second navigation host or decide Nexamas.UI-owned evidence internally. The dedicated Multi-window / Lifetime scenario may create a plain WinForms owner solely to exercise MASApplication.CreateWindow(owner); Nexamas.UI still owns the child window surface. The launcher supplies the official MASApplicationWindow.Pages route.

Consumer-owned host sizing contract for the current Nexamas UI Showcase. The active Showcase uses one PageHost window and no Form-per-page sample routes; all page body layout, control sizing, and surface rhythm are consumed from Nexamas.UI.

Internal LocalAppData-backed persistence for the external Nexamas UI Showcase theme preference. This is a showcase-app preference only; the Nexamas.UI runtime remains the owner of actual theme application.

Records fatal Showcase boundary failures outside the Nexamas.UI visual tree. This is host diagnostics only; it does not imitate a Nexamas.UI service.