Bigger boxes for bigger files

[sanoodles]

Please provide an option to make files that weight more KB look bigger in the diagram.

Perhaps with a logarithmic relationship between file weight and box size so that a few very big files don't take too much screen space.

If bigger boxes is technically challenging, try just bigger font sizes (which hopefully will stretch the box along) or greater background/foreground contrast. With logarithmic relationships as well.

[PabloLION]

Two features to add

1. get file size (core)
2. change node/&font size in graphviz.
   • Research how to map package size to node size. (package size can differ 1,000 times easily, yet node size should be relatively consistent, maybe use log or logistic function)
   • In case of the package size is cannot be known, what node size should we use? (for dynamic import Is it possible to exclude dynamically imported modules? #344 (comment))

[PabloLION]

Also, should we use a different style (including size, if cannot resolve the size of the dynamically imported package)
if so, what style / size should we use?
This is also for #344 (comment)?

[sanoodles]

I'm not sure if you are asking me, but I assume yes.

I think that how to depict dynamic imports is a different topic on which I have no strong opinion.

I only know that the type of an import could not imply a different box style because other consumers might import it in different ways (eg. static, or for the side effects (yuk))

So if anything, I would paint the arrow differently. But mind:

• Dashed arrows already symbolize something else in UML. I would overlap as little as possible with UML to minimize confusion.
• Maybe use a lower contrast color arrow
• Maybe and if easy enough, add a label with the word "dynamic" next to the middle of the arrow

[PabloLION]

Thanks for the ideas @sanoodles . It seems to me that the current graph is not using same symbols as the UML system. I just checked that the UML uses dashed line with open arrow for Dependency relationships.
I'll edit my posts before and try to work on it later.