| Hannes Magnusson 2007-10-04, 10:00 pm |
| On 10/3/07, Philip Olson <philip@roshambo.org> wrote:
>
> On Oct 1, 2007, at 9:27 AM, Hannes Magnusson wrote:
>
>
> It goes without saying that this is awesome and a great step for the
> PHP manual. The dream and reality of allowing an extension specific
> faq, tutorial, and the like, by using set/book is most excellent.
>
> Regarding basic extension navigation, like from here:
>
> http://livedocs.phpdoc.info/manual/en/funcref.php
>
> It's sometimes difficult to find an extension. Right now this uses
> information (status, membership, and state) that is currently defined
> in each reference.xml and displayed here:
>
> http://php.net/extensions
>
> This is good but because it's difficult to categories all of these,
> and because one day we will have over 1000 extensions (god bless
> PECL!), we'll need to offer an alternative means or three for finding
> these extensions. One route (current, non-dev) is to offer users a
> view of them alphabetically. Another is to focus on our search
> functionality. Basically we need to brain storm on this because I'm
> afraid it's too difficult to find an extension and the problem will
> only get worse. Perhaps use the categorized approach as current, and
> offer (link to) an alphabetized version in the appendix. But maybe
> someone will come up with something more innovative... :)
As soon as we create nested groups the user will not be able to find
the extension he is looking for on the funcref page, he will have to
first click a category and then he has to find a sub-category and then
the extension..
I don't feel that is acceptable, which is why I removed it. (An
exception to this is of course PDO which is a "container" for the rest
of the drivers plus the general PDO docs)
I don't mind the funcref page listing 500 extensions. When I click an
extension my left-hand-navigation will only show me extensions in the
same category so there won't be more than 20-30 extensions there.
The current grouping could be better though, but I am definitely
against sub-categories.
> And on a sidenote, ref.http is missing from manual.xml.in (it should
I know. I was having problems with it and removed it temporarily to
fix the build.
-Hannes
|