Rendering¶
Purpose¶
Owns preview-facing rendering coordination for the live preview system.
This territory is responsible for coordinating preview rendering flow, preview texture lifecycle management, styled preview application, and preview render scheduling while delegating low-level rendering implementation to Rendering and pipeline systems.
Owns¶
- Preview render coordination
- Preview render scheduling
- Preview texture cache lifecycle
- Styled preview application flow
- Preview render request orchestration
- Async preview render coordination
- Preview render result handling
Does NOT Own¶
- Low-level rendering implementation
- Shader implementation
- Background generation
- Pipeline-specific render implementation
- Export workflow ownership
- Panel UI drawing
Allowed Dependencies¶
Rendering may depend on:
- Preview.Scene
- Preview.Prefs
- Styling systems
- Rendering abstractions
- Pipeline routing systems
- Texture lifecycle utilities
Rendering should avoid: - editor panel orchestration - export workflow ownership - feature-level business logic
Notes¶
This folder exists to separate preview-facing render orchestration from lower-level rendering implementation details.
Preview.Rendering decides: - when previews render - how preview textures are coordinated - how styled preview results flow through the system
Rendering and Pipelines decide: - how actual rendering occurs - how pipeline-specific rendering behaves
This distinction is important.
Preview.Rendering is orchestration territory. Rendering is implementation territory.
Texture ownership and cleanup are intentionally centralized here to reduce preview memory leaks and render lifecycle bugs.
Future Candidates¶
- Continue protecting the separation between orchestration and rendering implementation.
- Avoid allowing export rendering workflows to merge into preview rendering.
- Maintain strict ownership of preview texture cleanup and replacement behaviour.