Checklist
Description
In most filesystems, folders are meant to be used as organizational units for objects. But there are many instances where users treat them as a whole object, one that just so happens to be made of several disparate files.
Solution
I'd love a feature that lets you either:
- group several individual files into a single "file"
- import a folder as a "file" rather than importing its contents
The resulting entity would be treated as a single indexed and taggable entity. Opening it would reveal either a folder, or some kind of gallery view.
Use-cases I can think of include:
- Comics. They're often made up of multiple images. Currently, TagStudio treats them all as individual images, even though they're technically a single object separated into multiple pages.
- Projects (such as video projects). Each project gets its own folder, so the project is the "object", and the files within should remain untagged.
- Applications. macOS handles each app like it's an individual file, even though it's just a folder with
.app appended to the end of the name. It'd be neat if we could use TagStudio as an "app launcher" of sorts, one that respects the folder hierarchy within.
Alternatives
I'm aware that you can use archive file formats like .zip (and .cbz for comics specifically), but these options won't work if the files are intended to be kept separate for editability, archival, or a need to reference individual files (usually by apps).
Checklist
Description
In most filesystems, folders are meant to be used as organizational units for objects. But there are many instances where users treat them as a whole object, one that just so happens to be made of several disparate files.
Solution
I'd love a feature that lets you either:
The resulting entity would be treated as a single indexed and taggable entity. Opening it would reveal either a folder, or some kind of gallery view.
Use-cases I can think of include:
.appappended to the end of the name. It'd be neat if we could use TagStudio as an "app launcher" of sorts, one that respects the folder hierarchy within.Alternatives
I'm aware that you can use archive file formats like
.zip(and.cbzfor comics specifically), but these options won't work if the files are intended to be kept separate for editability, archival, or a need to reference individual files (usually by apps).