Marco V. wrote:
I've committed some core classes to create the php5 port of log4php.
Nice :)
The next steps (comments are welcome):
- Convert all the classes using the new php5 oo model.
- Create test cases using PEAR::PhpUnit2
I can help out with this if you create can give me a subversion account.
- Make some modifications to address new log4j features
- Mark the log4php (the php4 trunk) as stable and release the 1.0 version.
- Discuss a new class namespace (log4php_XYZ, more PEAR compliant).
Personally I think we should leave class names as it is. I don't think
we need to introduce a log4php_* prefix since the current classes is
mostly named Logger*. Have anyone experienced naming conflicts with
log4php? I think it's also important to stick to the names that is
already being used in a number of applications and make the transition
easier to the PHP 5 version.
Since we use PHPUnit2 for testing now it would be nice to use the unit
test and code coverage reporting tools in Phing to drive the development
process of log4php for PHP 5. Here's an example of how I'm using it with
PRADO:
1) Unit Test Report: http://www.urdalen.com/prado/qa/report/
2) Code Coverage Report: http://www.urdalen.com/prado/qa/coverage/
I can set this up if you want. Even nicer we could set up a nightly
build or running these tests on svn commits so that we know that we
don't break code in the subversion tree. What do you think?
Best regards,
Knut Urdalen
