Skip to content

Capture

Purpose

Owns capture execution workflows used by Snap Studio Pro export and production systems.

This territory is responsible for routing capture requests, executing static and animation capture operations, and coordinating capture-facing preview context access without owning higher-level export workflows.

Capture executes.

Export orchestrates.

Owns

  • Capture request execution
  • Capture routing
  • Static capture execution
  • Animation capture execution routing
  • Capture-facing preview context contracts
  • Capture size helpers
  • Capture texture preparation workflows

Does NOT Own

  • Export workflow orchestration
  • Batch export planning
  • Panel UI
  • Preview scene lifecycle ownership
  • Low-level rendering implementation
  • File path workflow ownership

Allowed Dependencies

Capture may depend on:

  • Rendering abstractions
  • Preview capture contracts
  • Models
  • Enums
  • Infrastructure file/encoding services
  • Styling and overlay systems where capture output requires them

Capture should avoid depending on:

  • Panels
  • Window lifecycle systems
  • High-level export workflow coordinators

Notes

Capture is the execution layer for producing images from the current preview context.

It owns: - how a capture request is executed - how capture executors route work - how capture output is prepared

Export owns: - why captures happen - which captures happen - how many captures happen - where export workflows go next

Rendering owns: - how pixels are rendered/generated at the lower level

This separation keeps capture execution reusable across quick export, batch export, animation export, static sprite export, and future feature workflows.

Future Candidates

  • Continue protecting the Capture/Export boundary.
  • Keep request execution focused and predictable.
  • Avoid moving export planning into Capture.
  • Maintain strict temporary texture cleanup ownership.