Library folder/container - use human readable structure / naming.

[sammcj]

Is your feature request related to a problem? Please describe.

At present when you add files to Depot it moves them to another location and renames them with UUIDs, I can see how this makes sense for the application - but for the end user who often has to browse the filesystem to access / change models etc... it's not very accessible.

Additionally because the directory structure is completely flat - it's very hard to find what you're looking for.

This makes using files stored in Depot very difficult to find when you're importing them to slicers, modelling software or uploading to your printer etc...

With using the container / application specific data folder it's actually become a little more messy for me than just managing folders and subfolders.

e.g.

Currently Depots directory structure looks like:

And there's no way to open the directory inside the container from the library view:

Describe the solution you'd like

• The option to use a standard directory path rather than an application container (hidden folder / whatever you call them) would be great.
• The option to use meaningful directory and file naming rather than UUID (alone).
• The use of subdirectories, perhaps per-category.

Additional context

For example, here is what my non-Depot directory/file structure looks like:

[destari]

[destari]

In the resources section, you can right click on any file and show in finder, or export the file (basically extracting it from the Depot library). Is this not enough or not in the correct place for it?

[sammcj]

Ohh yeah I guess that works - I'd probably expect it to be on the main model folder but that's fine for that problem.