Styling¶

Purpose¶

Owns preview-facing visual style state and style coordination for the live preview system.

This territory is responsible for managing preview style effect state and exposing simplified access surfaces for preview styling workflows while delegating actual image processing implementation elsewhere.

Owns¶

Preview style state
Preview style effect coordination
Style-facing facades
Style reset behaviour
Preview-facing style configuration

Does NOT Own¶

Low-level image processing implementation
Rendering implementation
Export workflows
Panel UI
Shader implementation
Texture generation
Scene lifecycle management

Allowed Dependencies¶

Styling may depend on:

Styling abstractions/contracts
Preview-facing systems
Lightweight rendering coordination surfaces

Styling should avoid: - export orchestration dependencies - panel/UI ownership - rendering pipeline implementation dependencies

Notes¶

This folder exists to isolate preview style state and coordination from rendering implementation and editor UI systems.

Preview.Styling owns: - which style effects are active - style-related preview state - simplified style access surfaces

Rendering/processing systems own: - how pixels are actually modified

The goal is to keep style workflows predictable and centralized without collapsing rendering logic into preview orchestration layers.

Facade classes are acceptable here when they simplify style interaction without exposing lower-level implementation details.

Future Candidates¶

Continue separating style state from image processing implementation.
Avoid allowing export-specific styling workflows to drift into Preview.Styling.
Maintain lightweight ownership boundaries around preview style configuration.