Re: [Fwd: Re: [PEAR-DEV] MVC revisted]

Lukas Smith wrote:

Its 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.

I am sure people will have a look and maybe some people will join you in your efforts. Help is always encouraged and it is needed to the extent I can get it. However, just getting more eyes on it and some input would be a starting point

Thanks, --Tony