Re: Package Proposal: MVCnPHP
| From: | Xavier Noguer | Date: | Mon, 07 Apr 2003 14:58:17 +0000 |
| Subject: | Re: Package Proposal: MVCnPHP | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-14982@lists.php.net to get a copy of this message | ||
El Lun 07 Abr 2003 06:23, Martin Jansen escribió:
..
> Stig's email from last year summarizes my thoughts about this topic
> pretty well. I suppose this is the way to go:
>
>
> http://marc.theaimsgroup.com/?l=pear-dev&m=102431151907287&w=2
<quote>
If they can be broken up in smaller components, they fit well in PEAR.
The problem (but also advantage of course) with application frameworks
is that they are monolithic, following you (whether you like it or not)
all the way from your database to the browser. If someone wants to use
some forms package, he should not have to install the whole circus.
</quote>
I don't see Tony's framework as monolithic, it just changes the way your
application is coded by introducing actions and views.
<quote>
Instead PEAR provides many smaller packages, that interoperate. In
practice this gives you a kinda of framework when you select given
packages, but it's not monolithic, you have options.
</quote>
I didn't notice the architecture of Tony's framework impedes in any way
interoperating with other packages.
If I'm correct, Stig's idea was not to accept packages/frameworks that don't
get along well with other packages. Am I correct in this?
Xavier