It is pretty slow for 700 nodes and 4096x4096. It can be much faster. Some algorithms do too much loops and copies.

It seems like Inkscape does not support rgba(...) colors. (see https://gitlab.com/inkscape/inbox/-/issues/1195).
This causes Inkscape to render all boxes and borders in black.

Would it be an option to use rgb(...), and handle the alpha component via opacity (should probably be a / 255.0)?

Happy to make a PR for this minor change, if this workaround is acceptable.

Slashes and commas are reserved as path and column delimiters, respectively. This prevents their use in names (path parts). Or rather, it leads to unexpected results.

My particular use case is in dirstat again, where I would like to use a trailing slash to denote directories.

I see two options to solve this:

• Configurable column and path delimiters
• Using HTLM entities, like / for these characters
  • Comes with some problems:
    • Would not work well with string length calculations for box titles
      • Could use regex or a dedicated XML/HTML encoding/decoding library to fix this
    • & is currently replaced by & to form valid XML/SVG
      • Would require to take care of HTML entities in & replacement

Are there any plans to make this zoomable?

• find . | tree
• find . -d | tree
• nginx logs?
• URLs?
• open API?
• some REST endpoints somewhere?
• K8S resources?

• Text would be challenging to scale.
• Box margins would be challenging to make nice looking.

Currently, the default heat coloring ranges from red to blue for low to high heat values.

Given the term "heat", I would expect the opposite.

Here is an example from dirstat, which uses log(#files) for coloring:

Some characters that are illegal in XML strings break SVG rendering. These characters should be escaped.

Encountered the issue in my little Go learning project dirstat, which uses treemap to visualize disk usage. File and directory names may contain such characters.

Looks like the relevant characters are only those:

• " "
• ' '
• < &lt;
• > >
• & &

Would you accept a PR to do a CI build of native binaries in order to distribute it to those who don't have or want the go toolchain?

( Super cool tool ! )