There are various tools that count the lines of code in a project, such as cloc or tokei. I'll use tools like this to get a very rough idea of the scope and complexity of a project. Where I've found these tools to fall short is when I want to get a deeper understanding of the shape of a codebase and answer questions such as which subsystems have the most code, or which languages are more prevelant in which areas. LocTree provides an interactive tree view of a codebase, allowing you to easily see line of code counts for every subdirectory of a project and filter it by language.
About LocTree
Filters
Recent Activity
&loctree Got a basic web UI up, with an interactive collapsible tree view and filtering by language. So far it's all a completely statically built page, with javascript taking the raw LOC data and rendering the tree from scratch on every filter. This ran reasonably on the orca codebase, but on chromium I'm getting absolutely destroyed. Going to see how much performance I can get out of the static rendering, if that'll work or if I'll have to set up a local server to stream the data and/or do some server-side html generation.
&loctree day 2ish - I'm creating some data visualization for lines-of-code-count data - I've often found myself wanting to drill down into lines of code for subdirectories of a project instead of just a whole-project summary. A tool called tokei exposes raw data per file, and you can use it as a library, but so far the only visualization I've seen is a somewhat inflexible pie chart. So I'm hoping to use that to export a static, interactive html page, maybe something like windirstat. Admittedly less x-ray-ish than some of the project I've seen so far, but I figured better to participate and try to scratch an itch than not.
Yesterday and this morning was getting data into a format I can use and starting to generate HTML. I've got some rust code that uses the tokei library to export the data, then using python to transform it since I'm too dumb to write tree building logic and fight the rust compiler at the same time, but I hope to have it all in native code either by the end of the jam or shortly after.