[REMINDER] Tools and Utilities::PDS

Hey, PDS stands for PHP Documented Source. You can see the original posts on this here: http://marc.theaimsgroup.com/?l=pear-dev&m=105318684503136&w=2 Latest source should be available from my HDD here: http://davey.is-a-geek.com/PDS/pds.pre.pds - if you have problems accessing I'll move it to my server. I have done some more work on this lately (not much, but have it working properly now) and think its ready to be marked as Alpha and released in a PEAR Package. The two things that needed to be fixed and that have been are: * Allowing for multiple params * Killing the script in the auto_prepend_file so that the code isn't run in a buffer and silenced (thats how it worked before but I hated it, now I set error_reporting(0) and trigger an E_USER_ERROR which kills it before it tries to parse the file) Things that need doing are: * Allowing for parsing of *all* apidoc @foo properly * Source/Doc cross referencing * Making the source a <ul> list so that the numbers are no selected if you want to highlight and copy the code * Make each line (an <li>) highlight when clicked (a la Zend Studio) * link to included/required files .pds files if they are found I'm going to check out PHP_Parser a little later to see if that can be used instead of reproducing its code in this. Also I've spoken to Greg about what sort of role phpDocumentor's code will play in this, and I think we've concluded that its not practical to use code from the phpDcoument 1.x codebase, but we've talked about how phpDocumentor 2.0 can be written to make it easier to hook into the apidoc parser. Voting currently stands at: 0 There was a lot of talk about this and feedback, which I've acted on, but mostly it was talk about using phpDocumentor code within it and then it kind of dejenerated into a phpDocumentor discussion. I look forward to response. - Davey