Re: API Documentation Generation
| From: | Daniel O'Connor | Date: | Sat, 30 Jul 2011 17:14:44 +0000 |
| Subject: | Re: API Documentation Generation | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-54418@lists.php.net to get a copy of this message | ||
>
> > > > What's required to set it up on test.pear.php.net?
> > >
> > >
> >
>
> http://svn.php.net/viewvc/pear/pearweb/trunk/cron/apidoc-queue.php?view=markup
>
> Thank you for providing that link.
> I have taken a look and notice that DocBlox currently does not (yet ;))
> support 3 of the command line arguments:
>
> 1.
dn, DocBlox currently does not provide the possibility to
> specify
> the name of the default package; it is always Default
> 2. p, PEAR mode is quite specific to phpDocumentor and is
> currently
> not implemented
> 3. s, There is no implementation at the moment for this option.
>
> Unfortunately; I can't seem to get it to work; nor understand how the
pieces fit together with even the existing phpdocumentor on the
test.pear.php.net site - help wanted!
I haven't applied your patch yet; and won't until I've got a good handle on
how it actually all works under the hood.
Is Helgi or anyone else able to take a quick look and explain to me in 25
words or less how pearweb's apidocs generate; where they are stored; etc?
Reviewing the code around the crontab and having to do tricky things on the
test site make me have low trust in this code.