General Support: Plogger PHP5/OOP Rewrite?

First of all: neat piece of software, especially as to the easiness of setup and administration. I instantly fell in love with the great look + feel and the simplicity.

However when I took a look at the source code to adjust a few things to my needs (I needed German language in the frontend and another zip method for the downloads) I was a bit disappointed finding it to be just a bundle of functions with lot of repetitive code. Honestly I had expected a bit more from a "complete rewrite".

Anyway I'm not here to complain so I want to ask: has anyone ever tried to port plogger to clean PHP5 OOP (or would anyone like to join in such a project)? I think some clean code we can make plogger even better :)

Thanks and regards
Chris

Chris33:

I agree it is some very messy code and is in desperate need of rewrite. When things were starting off over two years ago, PHP5 was not yet mainstream. Now, most hosts support PHP5 out of the box. With that being the case, I would like to refactor most of the code and make it much more OO as well as take advantage of some PHP5 features. There was not necessarilly a "complete rewrite"; it was a bit more of a reorganization of the file structure and naming conventions. Rewrite of the codebase is next.

My question is: Why port when you can contribute here and help clean the project up?

There are two links on the Trac Wiki for developer information. One links to the (still under development) Codex regarding reporting and patching bugs. The other links to some Plogger developer standards. You're more than welcome to contribute patches (You can open a ticket to refactor the codebase if you like) and we can test and apply those patches. If you contribute enough quality code, we might even give you commit access. We encourage people join the development and make Plogger even better.