Cheers,
This is a long standing TODO item. Zeev finally found the time to think about it a bit, and agreed that the Zend API documentation is going to be moved to phpdoc. Here is the relevant excerpt from his mail:
| We're willing to reassign the copyright to the PHP Doc team with | just one condition - we'd like there to be an attribution to | Zend, mentioning that the docs are based on an initial | contribution by Zend Technologies. | | I hope this was worth the wait :)
I propose moving the Zend API docs to phpdoc/en/zendapi, but we need to make up a good folder structure. We need the XML files, but not simpler then Extending_Zend_....xml, and we also need the figures and source examples in some sensible folder structure. I also don't know whether it would be better to move on the CVS server (retaining history), or just copy-add-commit-remove_on_old_file...
Continuing on this long on-hold thread, it would be nice to come up with a structure to move the files into. phpdoc/en/zendapi might not be a good idea after all, since this is supposed to be a start of a developers manual (which will hopefully get updated eventually :). So the streams docs should also go in here.
What about:
phpdoc/en/internals/zendapi
and
phpdoc/en/internals/streams
for now :) And still bundling the ZendAPI docs and the Streams docs with the manual, but in the same <part> (until something better comes around). The ZendAPI XML files, figures and the streams XML files should be easy to relocate. Systems people hinted that we should just do "cvs remove" and "cvs add" since these files have nearly no practical history. But the hanging question remains. What to do with the code examples in ZendAPI? I mean:
http://cvs.php.net/ZendAPI/source/
Any ideas? After these are handled, the remaing files (DTD, build system) in ZendAPI are just old crap, so if we have the content in phpdoc, the ZendAPI module can be removed entirely.
Goba
