Window Framework for UI Toolkit v2.0.x
GWG.WindowFramework.Theming Namespace Reference

Prepared and portable player-theme data, validation and appearance application. Contains configured snapshots, catalog/runtime selection, bounded folder import/export, validation reports, reversible bindings and compiled extension contracts. Player data does not execute loose USS, UXML or code. Borrowed project resources and decoded folder-owned images have distinct lifetimes. See wfw_prepared_theme_workflow, wfw_portable_import_export and wfw_portable_bindings. More...

Namespaces

namespace  Json
 Framework-owned bounded JSON parser, writer and data nodes. Describes WindowFramework's own implementation, not Unity's internal JSON API or a new network service. Strict parsing and deep-copy access support portable manifests and opaque extension sections without an external serializer dependency. See wfw_extension_data_api.

Data Structures

class  DeveloperThemeBinding
 Applies trusted prepared developer rules inside one explicitly owned UI scope.
class  DeveloperThemeDefinition
 Build-prepared developer settings derived from the configured USS graph. More...
class  DeveloperThemeSelector
 Supported selector matching for application-owned prepared developer mappings. More...
interface  IPlayerThemeAssetExtension
 Optional raster-asset capability for compiled purchaser theme extensions. More...
interface  IPlayerThemeExtension
 Compiled purchaser-defined handler for one namespaced portable theme section. More...
interface  IPlayerThemeRecoveryExtension
 Compiled purchaser-defined handler for one namespaced portable theme section. More...
class  MappedPlayerThemeExtension
 Generic metadata adapter created by the runtime, not a developer's control bootstrap.
class  PlayerThemeButtonBinding
 Applies resolved player button tokens to one explicitly owned UI Toolkit button. More...
class  PlayerThemeCatalog
 Owns a bounded discovery snapshot of valid player theme folders. More...
class  PlayerThemeContextMenuBinding
 Owns theme application for one core context-menu surface or item.
class  PlayerThemeExporter
 Creates a new independently editable player theme from resolved framework values. More...
class  PlayerThemeExtensionRegistry
 Application-owned registry of compiled portable theme extension handlers. More...
class  PlayerThemeFolder
 Owns a completely validated manifest and decoded raster assets from one player folder. More...
class  PlayerThemeManifest
 Validated data-only portable manifest with preserved purchaser extension sections. More...
class  PlayerThemeNaming
 Portable Windows-safe theme folder naming shared by UI and direct export callers. More...
class  PlayerThemeReport
 Creates bounded player-facing diagnostics without exposing exception payloads or filesystem paths. More...
class  PlayerThemeRuntime
 Owns a runtime player catalog and selection leases for explicit UI scopes. More...
class  PlayerThemeScopeBinding
 Owns reversible player-theme mappings for a bounded framework visual subtree. More...
class  PlayerThemeSelection
 Resolves stable identity without silently falling back to index zero or a palette. More...
class  PlayerThemeSlideToggleBinding
 Maps the canonical slide-toggle contract onto one existing control.
class  PlayerThemeStateBinding
 Applies state-specific surface colours to framework tabs and context-menu rows. More...
class  PlayerThemeSurfaceBinding
 Maps resolved semantic tokens onto one explicitly scoped framework surface. More...
class  PlayerThemeTokenCatalog
 Canonical friendly-key mapping for portable framework theme data. More...
class  PlayerThemeValues
 Holds resolved player theme values keyed by canonical framework semantic token. More...
class  PreparedThemeSnapshot
 Build-prepared supported values embedded in the existing theme configuration. More...
class  SplitViewCursorBinding
 Centers theme cursors on native split-divider hit areas without changing native dragging.

Detailed Description

Prepared and portable player-theme data, validation and appearance application. Contains configured snapshots, catalog/runtime selection, bounded folder import/export, validation reports, reversible bindings and compiled extension contracts. Player data does not execute loose USS, UXML or code. Borrowed project resources and decoded folder-owned images have distinct lifetimes. See wfw_prepared_theme_workflow, wfw_portable_import_export and wfw_portable_bindings.