Obviously, this isn't a complete detail of everything that's going on, but it gives you an insight into the overall process.
Starting the script
In simple situations, creating an auto-loading script is a simple matter of setting window.onload to a function. But what if there's more than one script? To this end, we created an appendLoader() function that will execute multiple loader functions, including a previously defined loader function
Finding the tree content
Rather than write a piece of script to define where your tree is, we've tried to make the script as automatic as possible - it finds all ULs with a class name containing "tree".
Augmenting the HTML
Unfortunately, an LI containing an A isn't sufficient for doing all of the necessary tree styling. Rather than force people to put non-semantic HTML into their file, the script generates extra <span> tags.
So, the following HTML:
<li>
<a href="#">My item</a>
</li>
Is turned into the more ungainly, and yet more easily styled:
<li>
<span class="a"><span class="b"><span class="c">
<a href="#">My item</a>
</span></span></span>
</li>
Additionally, some helper classes are applied to the <li> and <span class="a"> elements:
Styling it up
Why the heck do we need 5 styling elements? Basically, because there are 5 background-images to apply:
Opening / closing nodes
Having come this far, the "dynamic" aspect of the tree control is very trivial. We set a "closed" class on the <li> and <span class="a"> elements, and our CSS takes care of hiding the children, changing the - to a + and changing the folder icon.