HTML_TreeMenu and Tree

[simonneaves]

Can anybody give me some general advice about HTML_TreeMenu.
there seems to be quite a lot of possibly out of date packages and tutorials, and I’m getting confused about what is currently the best solution.

I have had a go with the kriesing Tree package, and have successfully hooked it up to a sql nested set database structure, but I can't integrate the Kreiesing Tree object with the heyes HTML_TreeMenu without getting an error. The error is because the kreising Tree package works with the field `name`, and the HTML_TreeMenu needs a field called `text`.

I have had a go at working with the latest Heyes Tree package (http://www.phpguru.org/static/tree.html) too, but there doesn't seem to be any documentation on creating Tree objects from a nested set sql structure.

Any thoughts?

[Eran]

http://www.google.com/search?q=recursion+tree+php
it simple to do it in recursion.
this is looking nice - http://www.sitepoint.com/article/hie...-data-database

i don't read it all but i saw the picture and the table and this is all what you need although i think you can find a better script code than they wrote there

[simonneaves]

Thanks for this Eran. I was hoping to avoid recursion (the adjacency list model) because potentially my tree might have many thousands of nodes (hense I was intending to go with the nested set model (http://dev.mysql.com/tech-resources/...ical-data.html). Having said that, the article you found is a good one, and covers the nested set model nicely.

I wanted to take advantage of all of the javascript that has already been written in HTML_TreeMenu to dislpay these trees as expandable and colapsable interactive menus though. There is documentation that says that both the Kreising tree and the Heyes tree should work with the HTML_TreeMenu Pear component, but as I say, I can't find definitive documentation to show me exactly how to do it. I was hoping to aviod having to hack into the classes that kreising and heyes have written, or indeed write my own. Perhaps I'm being lazy, but these PEAR classes seemed like a good way of shortcutting a lot of work.