phpDocumentor development, end of Feb.

phpDocumentor development has been moving towards stability. We're about to do a feature freeze and release phpDocumentor 1.2.0rc1 within the next month, or slightly later depending on a few variables. In the past week or so, there have been many bugs cleared up in the HighlightParser, and it has reached stability. There are some remaining bugs with {@internal}} to be worked out, but otherwise it is now safe to use the new --sourcecode command line call to generate highlighted cross-referenced (phpxref-style) source code. The highlighting is customizable to the token. This means that the templates have total control over how highlighting will appear. All templates that ship with phpDocumentor have the same highlighting due to the common programmer attribute known as laziness: I don't have the energy to customize it for every template. Anyone with interest can take a look at cvs (instructions for anonymous cvs are at http://www.phpdoc.org) and request a developer account from Josh if you want to help make a template kick butt. We are no longer bound to the 5 allowed colors in php.ini for highlight_string, and in fact don't even have to use <font> tags. Anything is allowed. Source code highlighting has also been expanded to both in-code <code></code> tags like: /** * * <code> * class test * { * } * </code> */ to {@source} tags, and to <programlisting role="php"> sections in a tutorial/extended documentation for examples, see the phpDocumentor manual at http://www.phpdoc.org/docs We also added in Harald Fielker's alpha-level CSVdia2codeConverter, which can be used in conjunction with dia2code to generate UML diagrams and then convert them back into code. I have no idea how it works, so when I learn, I'll add that to the documentation :) Otherwise, many bugs have been fixed in the core, and documentation added to all the core classes or revised to be up to date. Greg -- phpDocumentor http://www.phpdoc.org