> > Every configure and ini options should be configured in
> > a "reference" section, if there is a reference section
> > for that topic. If there is no, then we need to put that
> > remainder option (probably core one) to a common place
> > (probably to that appendix, where the autogenerated index
> > of all the ini and configure options will reside).
>
> I can remember a discussion about ini.xml in every /referenc/ext
> with all ini-related settings for that extension (like constants.xml)
> Am I right and should this be done?
/reference/someextension/
reference.xml [intro]
constants.xml [predefined constants]
classes.xml [predefined classes]
ini.xml [ini settings]
configure.xml [configure options]
aliases.xml [function aliases - deprecated or still working]
resources.xml [resource types, and functions using/creating/destorying
them]
faq.xml [extension specific FAQ]
functions.xml [entity list of funcitons]
As discussed before, *everything* into extension docs. This let us
move all the stuff to PECL doc for example, or move an extension to
here from PECL. It also make finding particular extension related
docs easier, and we can also generate an index of all stuff including
aliases, resource types, functions, faq, etc... This is kind of a big
reorganization, but it worth the effort IMHO.
But please just start from one point (the first one was predefined
constants), and move then on forward. If we have these files in
some of the extensions in separate stages, then we make our work
really harder. Go step by step...
Goba
