Skip to content

BatchEdit

Purpose

Owns editor UI panels and controllers for multi-prefab batch export workflows in Snap Studio Pro.

This territory coordinates user-facing batch export configuration, multi-angle setup, batch progress reporting, and filtered prefab export workflows while delegating capture execution to feature services and capture systems.

Owns

  • Batch export panel UI
  • Batch export workflow coordination
  • Multi-angle batch configuration UI
  • Batch request construction
  • Batch progress routing
  • Batch export controller orchestration
  • Batch export user settings
  • Filtered prefab export workflows

Does NOT Own

  • Capture execution internals
  • Rendering implementation
  • Preview scene lifecycle ownership
  • Export encoding implementation
  • Thumbnail generation implementation
  • Rendering pipeline implementation

Allowed Dependencies

BatchEdit may depend on:

  • Capture/export feature systems
  • Prefab repositories
  • Thumbnail grid systems
  • Preview facades
  • Shared panel helpers
  • Batch runner infrastructure
  • Models/settings/request objects

BatchEdit should avoid depending directly on:

  • rendering implementation systems
  • low-level texture encoding systems
  • pipeline-specific rendering internals

Notes

BatchEdit is intentionally orchestration-heavy because batch export workflows naturally combine: - prefab selection - transform settings - camera settings - export settings - angle distribution - progress reporting - capture coordination

This complexity belongs in editor workflow territory rather than being hidden inside rendering or export implementation systems.

BatchEditPanel owns: - user-facing workflow coordination - request collection - UI state

BatchEditPanelController owns: - operational orchestration - runner coordination - progress lifecycle handling

Capture and export implementation remain delegated to feature systems.

Future Candidates

  • Continue separating UI orchestration from capture implementation.
  • Maintain explicit request construction for batch workflows.
  • Keep batch lifecycle cleanup and runner unsubscription safe and obvious.
  • Avoid embedding rendering implementation inside batch export UI systems.