TeamAmaze / TeamAmaze/AmazeFileManager
Trying to load gigantic directories *before* accessing them
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Take for instance a directory of 1500 files (could happen) or more, MainFragment will simply find every file in it, and then show the directory, in my Moto E2 4G that takes time. I propose loading dynamically and telling the user that the directory isn't fully loaded; take also into account that the user won't look at each (1500) file/directory inside, probably they will just search.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading MainFragment and tracing how it enumerates directory contents before displaying them. Define an incremental loading approach that keeps large directories responsive and tells users when results are incomplete; completion should avoid loading every entry before showing the directory and support the stated search-oriented use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100