Re: Feature Request: deeper TOC for pear.php.net manual

Have to say I find it kind of annoying that I have to click twice to find the package docs I'm after - and expecially as some packages do not have docs.. - eg. press on Images looking for Image_Transform. It gives the impression that perhaps there isnt much in the manual, whereas the opposite is true. It would be better to list all packages under their categories, on the main page - however my pathetic efforts at playing with dssl ended up concluding it was just too difficult.. - and it would be quicker to write the XML_Transformer manual generator... so many todo's and so little time... Regards Alan Alexander Merz wrote:

Greg Beaver wrote:

In addition, do the template engines in PEAR really require HTML to work? Why not put them into a category called "Templates" or "Template Engines?" Math/Numbers should be combined into one category, or differentiated more.

It would no problem to write, but this is the best way to confuse users. Also you lost a big advantage: an automatic link (not in sense of a hyperlink only) between package doc and the package itself. Will thinking about peardoc2, i played with flatter and deeper TOCs, the current way is IMO the best compromiss.