Is PHPList codebase solid for future features?
Jaime Gómez Obregón <jaime <at> iteisa.com>
2009-08-14 16:42:15 GMT
I've started to use PHPList some weeks ago and now I've started to have
a look at the source in order to try to improve the look and feel and
the usability of the UI.
But the way PHPList is constructed makes it very difficult to do any of
such improvements: there is no independent presentation layer, the i18n
implementation is confusing (getText has probed to be far more robust),
lots of embedded styles and scripts, no database abstraction layer,
hardcoded HTML, no semantic markup... amongst many other things I'd like
There are also a couple of things I don't like, as sharing the Webber
libraries, files ending in ".inc", abuse of global and superglobal
variables, the /?page=action dispatcher, mixing web and command line
logic, files over ~1,000 lines... not to mention http://tinyurl.com/otd3s2
IMHO integrating all of those improvements and making PHPList ready for
further development would imply almost a complete rewrite of the actual
Please, don't take me wrong: I really appreciate PHPList, I use it, I
know it's given out for free and I made my little contribution on the
issue tracker. The point is that I'd like to add things but don't see
the actual codebase solid enough.
I'd like to ask: is there any plan for a major rewrite?
In the case of somebody starting such a heavy work, the changes are
likely to be not easily merged back into the trunk. Would the dev team
be supporting it? Have there been any attempts to address the goals I
Jaime GÓMEZ OBREGÓN
jaime <at> iteisa.com
Phplist-developers mailing list
Phplist-developers <at> tincan.co.uk