Skip to content

Prefs

Purpose

Owns preview-domain editor preferences related to live preview behaviour.

This territory stores lightweight editor preference state for preview rendering and interaction systems without owning preview orchestration or rendering implementation.

Owns

  • Live preview editor preferences
  • Preview optimization toggles
  • Preview FPS overlay preferences
  • Preview anti-aliasing preference storage
  • Preview-related EditorPrefs keys

Does NOT Own

  • Preview rendering implementation
  • Preview scene orchestration
  • UI drawing
  • Export settings
  • Rendering pipeline logic
  • Feature workflow ownership

Allowed Dependencies

Prefs may depend on:

  • Unity Editor preference APIs
  • Lightweight shared models/utilities where required

Prefs should avoid: - rendering implementation dependencies - panel orchestration dependencies - preview scene lifecycle dependencies

Notes

This folder exists to isolate persistent preview-related editor settings from preview orchestration systems.

Preference systems should remain: - lightweight - domain-focused - storage-oriented

They should not absorb: - workflow logic - rendering coordination - feature orchestration

The goal is predictable ownership of preview-related editor preference state.

Future Candidates

  • Continue keeping preview preference ownership isolated from rendering and UI systems.
  • Avoid turning preference systems into general preview service layers.
  • Maintain simple domain ownership boundaries for EditorPrefs storage.