[AlliumCepa]

When I want to "View Shared Files" of a user, and they "sent list of shared files for directory" - results return as a list of files, without their folder tree. It is difficult to distinguish group of files for downloading, for example music album, TV series or Chapters of a book. Can we have the list organized just like our own shared folders which we can browse, collapse and expand? Thanks.

[fox88]

File data is sent without directory tree structure information.
Once upon a time it was attempted to have a separate tab for each subdirectory; and it was a mess when directories were numerous.
Hence the data is treated as a flat list, and there is no simple way to change this.

[AlliumCepa]

Thank you for the fast reply, fox88.

fox88, on 07 February 2024 - 03:54 AM, said:

File data is sent without directory tree structure information.

Incorrect. Depending on the client you're using, you may want to check [Servers] -> [Log] for example:

2024-02-07 10:01:48: Requesting shared files from 'kha1949'
2024-02-07 10:02:46: User kha1949 (10335028) shares directory 'Collections'
2024-02-07 10:02:46: User kha1949 (10335028) shares directory 'Downloads'
2024-02-07 10:02:46: User kha1949 (10335028) shares directory 'Torrents'
2024-02-07 10:03:01: User kha1949 (10335028) sent list of shared files for directory 'Collections'
2024-02-07 10:03:05: User kha1949 (10335028) sent list of shared files for directory 'Downloads'
2024-02-07 10:03:05: User kha1949 (10335028) sent list of shared files for directory 'Torrents'
2024-02-07 10:03:05: User kha1949 (10335028) finished sending lists of shared files

fox88, on 07 February 2024 - 03:54 AM, said:

Once upon a time it was attempted to have a separate tab for each subdirectory; and it was a mess when directories were numerous.
Hence the data is treated as a flat list, and there is no simple way to change this.

Great! So it can be done, but there is no simple way. I can understand this and I am willing to help simplify a possible solution, by breaking the mess down to less messy chunks.
Since there was an attempt already, can we adjust it (or rebuild it) so there wouldn't be a mess when listing numerous directories? What was learned as a result? That a large amount of data can be difficult to manage? How much was too much? Did it slow down performance or made visualisation ugly? Both?

For example:

• Auto-pause retrieving (and/or displaying) list of shared files every XXX lines. Resume (retrieve next XXX) with a button [Load More]. Number XXX can be automatically approximated according to each client's hardware capabilities. My understanding is that XXX < 1 million.
  
• As the above, but auto-pause every YYY tabs.
  
• Load list of shared directories first, but queue their content upon user expanding only that branch of the tree.
  
• Groups of tabs.
  
• Combination.

If the above ideas could work, is it simple enough?