Re: phpDocumentor Bugs... ?
| From: | Davey | Date: | Tue, 14 Oct 2003 15:15:45 +0000 |
| Subject: | Re: phpDocumentor Bugs... ? | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22686@lists.php.net to get a copy of this message | ||
Greg,
yes, I am using tabs. Silly me. Forgot to convert to spaces for PEAR compliance like normal.
I will file the class bug now.
- Davey
Greg Beaver wrote:
Hi Davey, Could you open bugs for especially the class list, but also the / as they probably can be fixed easily. It is probably adding a test if ($link{0} != '/') in the HTMLSmartyConverter As for source highlighting whitespace, do you use any tabs? the highlighter doesn't do well with them, as it tries to convert them to spaces. There will be large changes to the way source highlighting is implemented in version 2.0 - basically, unless there is a showstopper bug in 1.x, I'm halting development, because otherwise 2.0 will never be released :). I consider the class bug to be a showstopper. Greg Davey wrote:Hey, I've been creating a new package for PEAR (not one of those mentioned in my large RFC) called XML_Annotea. Whilst using phpDocumentor for the first time I've come across some possible bugs... Going through the docs seems to add extraneous /'s to the url, go to http://davey.is-a-geek.com/php-cvs/pear/XML_Annotea/docs/ And then click: Annotea_Client.php Now, look at the link to the source code, notice extra / after /docs? Go back to the Annotea_Client.php and look at the link again, we have another extra / there. I'm sure this is a small fix. Now, my second problem is that whilst phpDocumentor is picking up each file, the files phpdoc and also is documenting the class, on the pages http://davey.is-a-geek.com/php-cvs/pear/XML_Annotea/docs/XML_Annotea/_Annotea_Annotea_Client_php.html and http://davey.is-a-geek.com/php-cvs/pear/XML_Annotea/docs/XML_Annotea/_Annotea_Annotea_Server_php.html it does not list the classes in the files... why? Last... the highlighted source has some slight whitespace problems still, Would you like some help in implementing the highlighting? Are you using a tokenizing system now? or highlight_*? Can I suggest making the code an <ol> and placing each line in a <li> - this gives automatic line numbers AND when copied and pasted the numbers should not be copied. I've done work with both butchering highlight_* (http://hashphp.org/ see one of the pastes here for an example, it has an anchor for each line, each line will highlight if you click it, it uses the <ol> like I said) and also using the tokenizing approaching via PDS which you have seen. - Davey