#44689 [WFx->Asn]: old table of contents in documentation

ID: 44689 Updated by: bjori@php.net Reported By: routinet at hotmail dot com -Status: Wont fix +Status: Assigned -Bug Type: Documentation problem +Bug Type: Doc Build problem Operating System: no matter PHP Version: Irrelevant -Assigned To: +Assigned To: bjori New Comment: > Still, the original index.php was quick. One click vs. > two clicks, I suppose. Why not use both? I don't think we can, for technical reasons. I'll look into it though. > I certainly agree. It offers an excellent level of detail. > I find the alphabetical list of extensions easier to use than the > categorized version, however, and the latter could benefit > from some sorting as well. Same idea: why not both? Alternative extension categorization is available from http://php.net/extensions, I suppose we can add alphabetical categorization there. Alphabetical listing from the left-and TOC will however not get back in, it was completely uncontrollable. The left hand TOC only lists "related" (same category) extensions. -Hannes Previous Comments: ------------------------------------------------------------------------ [2008-04-11 08:53:07] routinet at hotmail dot com Maybe I'm just resistant to change. > These are still there, and even more detailed listing and > description for each chapter and subsection, from the TOC > on the left. I compared to Aug2007 from archive.org, and I have to say it is a great improvement. Still, the original index.php was quick. One click vs. two clicks, I suppose. Why not use both? > The left hand navigation is much more detailed now and contains > all its parent chapter and a detailed subsection listing with > (hopefully) better description for each subchapter I certainly agree. It offers an excellent level of detail. I find the alphabetical list of extensions easier to use than the categorized version, however, and the latter could benefit from some sorting as well. Same idea: why not both? ------------------------------------------------------------------------ [2008-04-11 08:16:41] bjori@php.net > For example, under "Language Reference", > there was a list of direct links to "Basic Syntax", "Types", These are still there, and even more detailed listing and description for each chapter and subsection, from the TOC on the left. > I very much miss the left nav as well. The chapter-level TOC > is fine for the most part (providing the detailed TOC is still > available *somewhere*). The left hand navigation is much more detailed now and contains all its parent chapter and a detailed subsection listing with (hopefully) better description for each subchapter ------------------------------------------------------------------------ [2008-04-11 07:21:00] derick@php.net I agree, the navigation now is much worse than before. ------------------------------------------------------------------------ [2008-04-11 06:44:56] routinet at hotmail dot com Yes, that too. :) I have bookmarked http://www.php.net/manual/en/. Until recently, that page displayed a very detailed table of contents which included the major subsections within each chapter. For example, under "Language Reference", there was a list of direct links to "Basic Syntax", "Types", "Variables", etc. (the first-level bullet points found at http://www.php.net/manual/en/langref.php) I very much miss the left nav as well. The chapter-level TOC is fine for the most part (providing the detailed TOC is still available *somewhere*). I would like to see the chapter currently being viewed expanded there. For example, the alphabetical extension listing would only show up if I were looking at the "Function Reference" chapter. Perhaps create an expandable tree view there, such that the user could drill down into details as they wished? ------------------------------------------------------------------------ [2008-04-11 04:00:04] philip@php.net Please be more specific with what you mean. Do you mean you miss having every extension listed alphabetically in the left sidebar? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44689 -- Edit this bug report at http://bugs.php.net/?id=44689&edit=1