Skip to content

Controllers

Purpose

Owns workflow orchestration and export coordination for Static Sprite Animation features.

Controllers coordinate user actions, preview state, capture workflows, and export services while delegating implementation details to specialized systems.

Controllers act as the application layer for Static Sprite Animation workflows.

Owns

  • Export workflow orchestration
  • Capture sequencing
  • Frame generation coordination
  • Sprite sheet assembly coordination
  • Preview state integration
  • Export pipeline routing
  • User action execution

Does NOT Own

  • UI rendering
  • Editor panel drawing
  • Capture engine implementation
  • Sprite encoding implementation
  • Preview scene ownership
  • Camera implementation
  • File system abstraction ownership
  • Sprite sheet implementation details

Allowed Dependencies

Controllers may depend on:

  • Preview systems
  • Capture systems
  • Export systems
  • Sprite capture utilities
  • Sprite sheet services
  • Shared workflow helpers

Controllers should avoid depending directly on:

  • UI layout systems
  • Editor styling systems
  • Rendering implementation systems
  • Thumbnail generation systems
  • Environment export systems

Notes

Controllers are responsible for coordinating workflow steps but should not perform rendering, encoding, or export implementation directly.

Typical controller responsibilities include:

  • validating export requests
  • coordinating capture operations
  • managing export execution flow
  • restoring preview state after export
  • routing work to capture and export services

This separation keeps workflow orchestration independent from UI and implementation details.

Future Candidates

  • Additional export workflow coordinators
  • Export job batching
  • Progress reporting enhancements
  • Export cancellation workflows
  • Advanced sequencing behaviours