The repo files would be injected into the page in a certain order (using a tree traversal algo; files first, then [sub]folders files) , syntax highlighted, line numbered, with the possibility to add user bookmarks. The tool would also automatically save the current reading point per repo, like e-book readers.

I guess the use case would be to speed read a project's source code, as opposed to following the specific logic (class/function call stacks, etc).

The issue is that i haven't been able to decided on a proper implementation, particularly how/what to stream to the browser and memory management.

Obviously outputting the full repo's source to the browser in a single page is memory intensive, so it would have to pre-request a few files ahead. But rendering a certain number of files is not a guarantee that they would fill the device's screen (for example requesting 5 files with one or two lines each). So, something i've considered was for the client to request (to the tool's own api) a certain number of lines, depending on the client's device (smartphone/tablet...) / screen resolution.

There is also an issue in that source files that have been rendered on the webpage and were already scrolled over, should be removed from the page due to memory consumption, but should probably be cached locally in case the user scrolls back, ideally to avoid re-requesting the files, for a faster seamless experience. For local caching, cookies do not seem a solution, so probably html5 local storage?

Would appreciate any suggestions people would like to share,

thanks!