Skip to content

[Discussion] Organize History outputs into subfolders by Pipeline type #28

@massadm

Description

@massadm

Description

Currently, all generated assets are saved into a single, flat History directory. As the number of generations grows, this folder becomes cluttered. Furthermore, the application UI displays the entire generation history globally, regardless of the currently active pipeline.

Proposal

Organize the History directory by separating outputs into subfolders named after their respective pipeline types. Consequently, adapt the UI to filter and display history contextual to the selected pipeline.

Suggested folder structure:

  • History\AceStepPipeline\
  • History\ChromaPipeline\
  • History\ZImagePipeline\
  • History\etc.

Benefits

  1. Improved UI Experience: The application can show only the history relevant to the active pipeline instead of mixing everything together.
  2. Better Organization: Users can easily browse specific types of generations directly through their file explorer.
  3. Performance: Prevents a single folder from containing thousands of files, which slows down file managers.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions