TM.Util contains useful JSON Tree manipulation methods.
TM.Squarified creates Squarified TreeMap tilings.
TM.Strip creates Strip like tilings.
TM.SliceAndDice creates Slice and Dice TreeMap tilings.
Each tiling algorithm has its pros and cons. The main criteria for determining if a tiling algorithm is good is to check for the aspect ratio of nodes, check if the result is ordered or not and check for stability (i.e whether the nodes maintain their relative positions when the TreeMap is being navigated).
Here's a picture describing these points for the Strip, Squarified and SliceAndDice tiling algorithms:
As you may have noticed, DOMTreeMap is a standalone version of the JIT TreeMap component.
So why do this, then?
Well, I decided that for the next version of the library TreeMaps are going to be Canvas based. I'm already adapting the TreeMap tiling algorithms to render on Canvas and also plugging the rest of the TreeMap visualizations to an abstract Graph class that is also used by all other visualizations so I can use a lot of library code related to Tree Operations, Tree Animations, etc.
Also, not all TreeMap visualizations render nodes as rectangles. Some TreeMap implementations are based on Voronoi Tessellations for example:
So in order to maintain a more "abstract" notion of TreeMaps I think that having Canvas based TreeMaps would be a good idea. Anyway, now I'm working on adapting the code to be able to render TreeMaps on canvas, I must say that performance-wise things are looking promising: