Re: [Fwd: Re: [PEAR-DEV] MVC revisted]
| From: | Lukas Smith | Date: | Tue, 11 May 2004 15:58:22 +0000 |
| Subject: | Re: [Fwd: Re: [PEAR-DEV] MVC revisted] | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-29093@lists.php.net to get a copy of this message | ||
Tony Bibbs wrote:
Lukas Smith wrote:Well I will see if I have time to checkout your work. However I dont quite see how your MVC can be build without expecting a particular interface and logic inside the packages which may be used along with it. Otherwise it would just be a very abstract implementation which doesnt offer much then any article on MVC in PHP would also provide. regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07Its a framework for reuseable components. Not a place for frameworks. See the difference?Understood.if your system really becomes as flexible as you hope it needs to define alot of standards and/or abstraction layers. if it is not as flexible it will result in confusion (why does this package work but this doesnt)Well, not sure what you mean here. Out of the box my MVC implementation needs no other PEAR classes to function. It works as is, but when combined with some of the PEAR packages it gets quite powerful quickly. To that end, you can't really define a 'standard' as the standard would need to be set at the application level. I have no problem adding other abstract layers but the fewer the better. Again, this isn't aimed at being like struts and adding too many layers go against the intention. The good thing, however, is that those implementing that package can still add those layers themselves.