On 15 May 2007, at 17:46, David Dashifen Kees wrote: > I'd suggest using a structure rather than hierarchical divs; I've made > tree menus mostly out of unordered lists. The children of any node > in a > list are then contained within an internal <ul> within the <li> of the > node. Then, when a list item is clicked, you can open or close it's > internal <ul> with toggling or, as I usually do it, changing the class > name of the list item that you click. That way the class name can not > only control the display of any internal <ul> but it can also alter > the > image that appears to the left of the <li> which indicates whether the > list is expanded or collapsed.
This solution is just one case scenario, ajax-enabled trees are sometimes a better solution (very large trees, a lot of concurrent users working in the same structure, ). Most open source tree classes support both. Best regards Peter De Berdt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
