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
- Improved UI Experience: The application can show only the history relevant to the active pipeline instead of mixing everything together.
- Better Organization: Users can easily browse specific types of generations directly through their file explorer.
- Performance: Prevents a single folder from containing thousands of files, which slows down file managers.
Description
Currently, all generated assets are saved into a single, flat
Historydirectory. 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
Historydirectory 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:
Benefits