Would you agree this is the definition of a PHP framework?

[s_molinari]

@tony_marston404

My description of a Transaction Pattern is nowhere near the same as Martin Fowler’s description of a Transaction Script. Read the two links and you will see the difference.

You keep linking to component script. Why?

@tony_marston404

What he is clearly saying there is that you should separate out all GUI logic, Business logic and Data Access logic which is precisely what I have done by virtue of the fact that my framework is based on a combination of the 3-Tier Architecture and the MVC design pattern.

Again, you are confusing SoC with SRP or rather using SoC to support your usage of a monster class, which is totally off.

@tony_marston404

The fact that it does more than is absolutely necessary does not stop it from being a framework.

The fact you call your framework a framework isn’t being debated. The fact you call your framework a framework and all other frameworks libraries is.

@tony_marston404

Anything which does not provide all four of those characteristics does not deserve to call itself a framework.

The frameworks you call libraries do fulfill the 4 characteristics.

@tony_marston404

I know when to apply a pattern and when not to. I now when to separate a monolithic piece of code into cohesive modules and when to stop separating so that I don’t end up with a bunch of tiny fragments where all cohesion and unity is lost.

I would have to disagree with you here.

@tony_marston404

Yet when I have the audacity to question some of the things that YOU believe in all you can do is brand me a heretic for not following your interpretation of “best practices”. That sounds like hypocrisy to me.

It isn’t what I believe, but practically all good PHP developers.

Scott