Re: PEAR::PHPDoc --> DocBook (was Re: [PHP-DOC] developersmanual and users manual)
| From: | Joshua Eichorn | Date: | Thu, 22 Aug 2002 16:11:29 +0000 |
| Subject: | Re: PEAR::PHPDoc --> DocBook (was Re: [PHP-DOC] developersmanual and users manual) | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-8581@lists.php.net to get a copy of this message | ||
Bertrand Mansion wrote:
<cox@idecnet.com> wrote :We should be able to do another release soon after with docbook output. After that i'll start working on the integration stuff it doesn't look that hard but will need to decided what to do about dependencies, since currently they have to be documented at the same time for links to be created between them. Thanks for all the feedback and support. -joshJoshua Eichorn wrote:Same opinion here. Go for it. Bertrand Mansion Mamasam Sounds good, were about to release phpDocumentor 1.1.0 i'll try to release it to PEAR as well as in tarball form.Were willing to work with PEAR and add any features you guys need. Were already setup for multiple outputs so adding a converter for docbook wouldn't be that hard. Currently there are 5 active phpDocumentor developers and a couple others who have been sending in some small patches, we got slowed down a bit by the summer but im sure will be back on an agressive release schedule soon. -joshua eichorn Lead Developer phpDocumentor http://phpdoc.orgThat's the kind of things we need in PEAR. Take all my support on this. For me a good plan could be to commit PHPDocu, integrate things that people miss from PHPDoc, test the package and so, and then leave only one. Then we could finally add a "pear genphpdoc package" (currently we can't as it's not possible to generate the API doc from many packages because of the one-class per file PHPDoc limitation).