a cache is not simple... you have to account for lots of things
- storage management (thumbnails are not cheap)
- if the users doesn't stay in the file browser long enough, do you pause the cache and resume later? if resume the app needs to keep track
- what if the files was changed (added, deleted, removed, renamed, modified) outside? what thumbnails do I keep or discard? does the app scan in the background? what if the folder is never touched again or deleted? what happens to the thumbnails?
- the above problems propagates the more files in the folder
so it's not as easy as a problem as you think. That's why I said maintenance overhead is huge and if we were to implement this properly it'd take a long time, and it'd be only useful for people who keep large amounts of files in a single folder, and usually they are content with list mode (see other thread). If more people in the future request something like this then we'll add it.
- storage management (thumbnails are not cheap)
- if the users doesn't stay in the file browser long enough, do you pause the cache and resume later? if resume the app needs to keep track
- what if the files was changed (added, deleted, removed, renamed, modified) outside? what thumbnails do I keep or discard? does the app scan in the background? what if the folder is never touched again or deleted? what happens to the thumbnails?
- the above problems propagates the more files in the folder
so it's not as easy as a problem as you think. That's why I said maintenance overhead is huge and if we were to implement this properly it'd take a long time, and it'd be only useful for people who keep large amounts of files in a single folder, and usually they are content with list mode (see other thread). If more people in the future request something like this then we'll add it.