PHP_CodeBrowser is a tool that creates good looking web pages from your code and annotates them with problems found by checkstyle, pmd and others.
We have covered the release of PHP_CodeBroser version 0.1.0-alpha some months ago, see this post. Now, we’re proud to announce version 0.9.0-beta.
It features a neat interface that let you find errors even quicker, a clear commandline interface and much better performance, it’s almost seven times faster than the 0.1.x release.
You can get it via pear, just do
pear channel-discover pear.phpunit.de
pear config-set preferred_state beta
pear install phpunit/PHP_CodeBrowser
or you can check out the from github, just visit http://github.com/mayflowergmbh/PHP_CodeBrowser or just try
git clone git://github.com/mayflowergmbh/PHP_CodeBrowser.git
Here are some pictures to give you an impression of what it looks like
This is the overview page
And this is how the real code browser looks like.
When the stable release should be ready?
Regards!
Hi Jonathan,
the stable release is planned for the end of september 2010. We already have plans for version 2.0
Cheers
Thorsten
Nicht vergessen die PEAR Config wieder auf den alten state zurück zu stellen.
pear config-set preferred_state stable
Oder gleich
> pear install phpunit/php_codebrowser-
beta
– ohne irgendwas umzustellen.
under php 5.3.3 in windows i get report whitout any errors no mather what code i use (and there are errors ofcourse).
Tried to install it and got:
sudo pear install phpunit/PHP_CodeBrowser
No releases available for package „pear.phpunit.de/PHP_CodeBrowser“
Cannot initialize ‚channel://pear.phpunit.de/PHP_CodeBrowser‘, invalid or missing package file
Package „channel://pear.phpunit.de/PHP_CodeBrowser“ is not valid
install failed
Previous commands finished successfully
sudo pear channel-discover pear.phpunit.de
Channel „pear.phpunit.de“ is already initialized
sudo pear config-set preferred_state beta
config-set succeeded
Is this stable already? If not why is it taking so long? I hope this is free as it should be since we are waiting so long and you are already working on 2.0