You're right in your argumentation. Thus I think that I'm +1 for your
proposal. Apart from that we should take that we don't clutter the
source tree with other MVC packages, like it has happened with HTML
Templates, e.g., but that MVCnPHP should become the "standard" for PEAR.
I thing that thats a bit hopefull. (the one and only framework!) - frameworks are probably more contentious than template engines.
As I said before, raising the barrier on components that are likely to be more common (and implementation strategies could be considerably different) - like templates/frameworks.. to add the doc requirement will mean that we get a few good, well documented frameworks, and let end users decide from a range of quality (as aposed to picking from the trash:)
Regards
Alan
- Martin
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com