Re: HTML_Menu nodes properties mapping in templates

Great ! I don't think I'll be able to code it, but if I try, I'll warn you. Another great feature would be the possibility to decide if a level must be collapsed or expanded (see the same feature in dhtml_treeMenu). I think we could be greatly inspired by Dhtml_TreeMenu package : input from Tree class (createFromSql or createFromXml methods if I remember well), options by node, collapsed/expanded option (+ saved in cookie), etc... But I don't know very well what is under the hood in this package. Regards, Didier ----- Original Message ----- From: "Alexey Borzov" <borz_off@cs.msu.su> To: "Didier Galland" <galland@appli-box.com> Cc: <pear-general@lists.php.net> Sent: Saturday, September 13, 2003 9:42 AM Subject: Re: [PEAR] HTML_Menu nodes properties mapping in templates > Hi! > > Didier Galland wrote: > > First, Alexey, thanks for your great work on this package. I've been used > > this class for a while, found it very powerful and useful, and didn't > > understood why It was forgotten by pear gurus ;-) > > > > I wish to know if you think it will be possible to add other dynamic > > elements to the templates (with no limits), not limiting them to the three > > elements {url} {title} {indent}. It would be great if each node can have as > > many replacement tags we want. > > Hey, you are fast. I commited the renderer stuff only a week ago and didn't > release it yet. :] > > I thought about having more tags and allowing an unlimited number of custom > atrributes in menu nodes, but must admit that you have a more complete idea for > this than I ever did. > > Right now I want to add a renderer that will output menu to an array, add the > documentation for HTML_Menu to peardoc and release 2.0. As soon as it is done, > I'll work on integrating your proposal. Or if you'd like to code this yourself, > you can send me the patches against current CVS, I don't expect changes to the > already commited code before 2.0.