> > Builds: > > Will all or just bundled PECL docs be in phpdoc manual builds? > > Meaning, will a separate PECL manual ever exist? As PECL grows > > the manual will grow and like we discussed having a separate > > developers manual this is a *similar* issue. PECL is going to > > be huge one day and contain many specialized extensions. > > The decision was to now build all PECL docs with php docs, as > > - users will not be aware of where the extension comes from anyway > (lot of people use shared hosting) > - php.net and mirror sites provide good ways to search and > shortcut the manual > - this will promote PECL extensions better, they will not be > burried deep > > Since livedocs will be the future presentation system, we can do all > kinds of special marks on PECL extension pages.
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
