There is very limited documentation for PECL extensions currently as far
as I see. So I am not that much worried. We need to implement the
extension categorization system (phpdoc/RFC/manual.xml) either with that
markup or a different one, so the extensions will be easier to locate in
the manual. The manual will not be 100MB if we include all the PECL
extension docs (currently available in the PEAR manual).
Goba
What will the functions reference look like? Or quickref? Is the
index going to simply be a package search form? Like this:
http://pecl.php.net/packages.php
And what about the downloadable manuals, what will their indexes
look like? And what size will they be, 100MB or more? There are
already 314 PECL extensions and this number increases almost daily.
I'm a little worried but maybe I'm [likely] missing something here.
Downloads should be smaller somehow like only include bundled
extensions. Not sure how to package the other ones but maybe
they can be in their own downloadable manual. Ideally someone
could simply "update" their downloaded manual like add the
extensions they need but that doesn't sound like a simple task
especially for the printable one-page manual or CHM. And just
think how much more size all the user comments will add!
My main point of worry here is dl size and what the indexes will
look like, what's online or not isn't really a concern. People
need downloads for various things like IDE integration, printing,
going on a trip, etc.
Regards,
Philip
