Re: large ref pages

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 M. Sokolewicz wrote: > Now, it might be just me, but I think we should think about what the > ref-page is actually for. Is it there (as I believe it should be) to > show a summary of what that extension IS and provide links to other > (sub)sections which explain it in detail if a user wished to do so. Or > is it there to dump all documentation that does not fit anywhere else > (like it seems to be used now) ? Part of the reason the constants are included in the ref page is because the skeleton generator includes them in there by default. I would suppose in the olden days, it made a lot of sense to stuff them in the same page, since there weren't very many constants, but now with huge constant lists, this default behavior may not be the smartest. A good example of an extension that moved the constants list off the front page is http <http://php.net/manual/en/ref.http.php>, but the execution is a little clunky. I am fully in favor of moving constants off the ref page, but we first need the proper tools in place to do this. - -- Edward Z. Yang GnuPG: 0x869C48DA HTML Purifier <htmlpurifier.org> Anti-XSS HTML Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGagwcqTO+fYacSNoRAlThAJ4lN0x7fCYcgKyP+3dwXB6JaTYVXQCcCc7z Co8E0HaImwBjD5X4a/hFUxs= =luWB -----END PGP SIGNATURE-----