Hi there,
if you want to make one section with all the developer-info in it, I'm
fully with you, and would go one step further, to structure like
- developing PHP
- Building PHP from source (from Win-install-section, it's just
confusing newbies which just downloaded the bin-distri)
- extending PHP 3
- extending PHP 4
more to come (e.g. Zendapi 2)?
But PLEASE consider and agree on it completely before you make the the
changes to prevent the current chaos we have now.
We are still in the "consolidation-phase" of all the last changes in the
past e.g. the install split still isn't solved, this all makes confusion
to the writers/translators (which slows them down or even prevents them
from working) on one hand, slows down builds, and makes the files for
the build-process hard to read.
I don't consider links as a problem, it's just one point to be planned
before the change.
Other questions that occur for me concerning this:
Are there licencing-issues for the Zend-API-docs? Would be nice to have
them in the phpdoc-tree, and to make it more actual (e.g. there is still
a comment about a "CD enclosed to the book", etc.).
Bringing it into the phpdoc-tree would bring a much more clear
file-structure (e.g. in relation to the other chapters in the
"Dev"-section, a common "figures"-dir where also other figures could be
placed into, and finally a more clear build-process), and it would need
only one cvs-checkout to get - and work on - the whole maunal.
Just my 2 Cents,
Thomas
Philip Olson wrote:
>>splitting up the docs is a good thing, i'm for it anyhow.
>
>
> +1, good luck ;)
>
>
>>i think we can rename this appendix extending php 3, not
>>phpdevel because I don't think it's overly clear.
>
>
> This sounds reasonable although am always afraid such
> changes will break outside links. But oh well, this
> should be okay.
>
> On a related note, the section on "Reporting Errors"
> that lives in phpdevel (phpdevel-errors) is linked in
> many places in the manual, these docs should be moved
> elsewhere too. Maybe make features.error-handling
> the official page for these error type descriptions?
> The table there could hold this information nicely.
> For example, php.net/error_reporting links to them.
>
> Regards,
> Philip Olson
>
