Quality Assurance on PHP projects - PHPDocumentor feedback

First of all, thank you all for the enormous feedback I got on my latest article on documentation of code. I got a lot of comments on the usage of PHPDocumentor for the following reasons:
  • the project seems to be no longer maintained
  • it's not ready for php 5.3
  • it uses too much resources when using it on big projects
I have to agree that these reasons are valid enough to step away from PHPDocumentor as a tool for documentation purposes and look for a better alternative. So I've investigated one tool most people have commented on or tweet-ed/facebook-ed/g+-ed on: DocBlox.

Before I start a flamewar, I'm all for investigating more tools as time permits me, but these are my first impressions on the tool that had the most buzz in my personal social zone. If your tool of preference is not listed here, write an article on it and put the link here in the comments (or ping back to this article in your own post).

DocBlox seems to be the youngest project of all the various projects suggested to me, but gets a lot of support from major players in the field of PHP and is supported by my favorite build tool Phing (a tool I'll describe in detail in another article).

You can simply use PEAR to install DocBlox.

user@server $: pear channel-discover
user@server $: pear channel-discover

Select a package you need, in this case docblox/DocBlox-0.12.1 as the project is still in beta (when writing this article) and version DocBlox-0.12.2 has some issues

user@server $: pear install -a docblox/DocBlox-0.12.1

DocBlox is pretty simple in it's usage and works indeed better than PHPDocumentor, although I had to contact the project lead Mike van Riel (@mvriel) regarding a dependency error on Zend Framework, but it should be fixed now or any time soon.

My dear friend Matthew Weier O'Phinney (@weierophinney) had taken up my challenge to write an article about the usage of DocBlox and I have to say, it's a very good introduction that allowed me to use it immediately.

As a result, I was able to test-run both PHPDocumentor and DocBlox using Phing resulting in a small win for DocBlox. I haven't made a true benchmark test including memory consumption, cpu usage but I think that someone with more sysadmin background knowledge can easily set it up to give a more in-depth detail on which tool performs the best.


  1. Has anyone had this working with Mac OSX Lion? I've installed it as per the instructions above (except with 0.13.0 rather than 0.12.1) and get the following error:
    PHP Warning: require_once(markdown.php): failed to open stream: No such file or directory in /usr/lib/php/DocBlox/src/DocBlox/Core/Application.php on line 35

    Any help would be massively appreciated.

  2. @Gavin, if you're using the PHP version bundled with OS X, you may need to add PEAR's directory to your include path in /etc/php.ini. This is what mine looks like - I was having a similar error just trying to get phing to work.

    include_path = ".:/usr/lib/php:/usr/local/share/pear/PEAR";

  3. I have spoken to Gavin via Twitter; problem was indeed a missing include path.

  4. The dependency was fixed in version 0.13.0


    Nice work, though.