Skip to content

FileIO

Purpose

Owns low-level file output helpers used by Snap Studio Pro export and capture workflows.

This territory handles file saving, image encoding, folder creation, and export path construction without owning export orchestration.

Owns

  • Binary file saving
  • Image encoding helpers
  • Export folder creation
  • Export file path construction
  • File-output service contracts

Does NOT Own

  • Export workflow orchestration
  • Capture execution
  • Rendering implementation
  • Preview lifecycle ownership
  • Panel UI
  • Asset import/slicing workflows

Allowed Dependencies

FileIO may depend on:

  • Unity texture APIs
  • Diagnostics
  • Lightweight capture/export abstractions
  • .NET file IO APIs

FileIO should avoid depending on:

  • Preview systems
  • Feature orchestration systems
  • Panel UI systems
  • Window lifecycle systems

Notes

FileIO is infrastructure, not export workflow ownership.

Export decides: - what should be exported - where the workflow is going - when output should be written

FileIO decides: - how bytes are encoded - how files are written - how folders/paths are prepared

Future Candidates

  • Keep FileIO focused on output mechanics.
  • Avoid adding export workflow decisions to FileIO.
  • Maintain clear separation between file writing and asset import/post-processing.