in reply to building an HTML based tree UI

Well... for handling the state of the tree, you can name your tree limbs 000 001 002 003 etc in order, which is basically your key into an array or something, so when it is clicked you can either expand it, collapse it or view its contents. Then a child of 002 is 002000 002001 etc, which makes it easy to maintain hierarchy. Then just maintain your state in either hidden fields or a cookie, or in a file or DB on the server. It's not terribly hard to maintain if you do it right, but I might be misinterpreting your question.
                - Ant

Replies are listed 'Best First'.
(jptxs)Re: building an HTML based tree UI
by jptxs (Curate) on Apr 18, 2001 at 17:49 UTC
    that's been the thoughts I've had thus far as well, but the problem is that elements will be variable at all times. meaning when i collapse and expand the different parts of the tree, at one point or another what comes out could be different. The real problem I see with that is that I'll be regenerating what could be a big hash every time. I may have to just live with that, but I'm thinking _someone_ must have done this already =)
    "A man's maturity -- consists in having found again the seriousness one had as a child, at play." --Nietzsche
      Well... I suppose you could give every item you have a unique identifier in advance, something like a 3 char string. That way you could do the same thing, but you would have a more stable way of identifying what you have.
                      - Ant