large system defaults - Githubissues

git-truck / git-truck

Git repository visualizations, contribution statistics and more. Run npx -y git-truck to use Git Truck today!

https://twitter.com/git_truck

MIT License

235 stars 9 forks source link

large system defaults #579

Open mircealungu opened 2 years ago

mircealungu commented 2 years ago

[ ] #638
[ ] If I open GT on a very large system it would be nice to start with the treemap by default

e.g. when opening on TypeScript (and probably similarly sized projects) the bubble chart looks artistic; but does not do much more than that :) see:

alternatively, if we aggregated at the folder level the current metric, then this view might still be interesting; e.g. in it, the compiler should be the very active folder because it contains the checker -- which is the most changed file in the project :)

joglr commented 2 years ago

It would be interesting to experiment with some sort of coalescing / aggregation in the case of these large projects.

mircealungu commented 2 years ago

In fact, we already do a bit of this when not showing the labels when we have too many entities right? We could build on top of that maybe?

Some things to consider would be:

how to summarize the highlighted metrics? or do not summarize them at all, but instead simply show the gray circles making it clear that there's more to be seen in that part of the system that can be displayed
would this be solved if we introduced a "real zooming" - as suggested by Johan - a real zooming that would complement the "semantic zooming" that we do now?

joglr commented 2 years ago

We need to set some thresholds of these large system defaults. I also think we should notify the user that they have opened a large project, so we've activated some optimizations.

mircealungu commented 2 years ago

Very good point. I like the idea of notifying the user that "we've detected a large project" and adjusting the truck :)