Hi!
> Right (unfortunately :). Since splitting up only to
> the main-parts doesn't seem to be a solution for long
> (most files are from the funcref which is the most
> growing part), and the TOC for the Funcref doesn't
> provide also a great overview anymore:
> What do you think about inserting a new chapter-level
> into the function-feference, e.g.
> core-functions (array, filesystem, etc.),
> database-functions (msql, etc.),
> payment-functions (ccvs, cybercash, ),
We have discussed many times this subject, and came
to the point [at least as I can remember] that it
needs to be done, just we don't exactly now how
to do this. But the alfavetical listing is not all
right anymore....
>> Also we can decide if we want to produce "short" type of
>> manuals, as people do at Nexen. This way we can pack a small
>> compressed file with the most important functions and extensions,
>> and left off the less used ones. It would be popular IMHO.
> Right, and since I don't know the Nexen-structure:
> What's the relation between the No. of downloads?
> I could imagine that most people think "I want it all".
If you use the manual daily, you can easily find things,
if you need not look at things like migrating, exotical
database extensions, etc. that are only space consuming
for you. A small manual is easier to search in, and find
the things you want.
I think the smaller manual should be an alternative, maybe
somehow producable from the current XML files (broken links
are the biggest problem), and this should not be the
replacement of the current one.
Goba
