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

[s_molinari]

@tony_marston404

But how much code do you have to write to use this ACL feature?

Not much.

@tony_marston404

But does it have an pre-built AUDIT database and a set of screens instantly available in the framework to view the contents of the AUDIT database?

Now you are talking about being more at an application level and not a framework level. Of course, there is no premade screens for accessing the stored logs. That is up to the client developer.

@tony_marston404

But does it allow you to define separate tables for different translations of particular database tables, and does the framework automatically switch to those tables when you specify that you want the output in a different language?

The language in Symfony is stored in different language files and transpiled to PHP a single time, so the code is ready at run time. No database calls. And yes, if you change the locale, the retrieved language is changed too.

@tony_marston404

But you have to write code in order to incorporate those optional extensions.

As a software framework, the base behavior is supposed to be extensible through code (too). That is one of the main reasons to use a framework. You force your solution on your customer. Some might like that, others might not. It doesn’t make your framework any better.

@tony_marston404

So you don’t now what Transaction Patterns are?

I know what a transaction script is. I have no idea what you are explaining on the page you linked to. You do explain what a transaction pattern is here: http://www.tonymarston.net/php-mysql/infrastructure.html#controller.script

And if you read this gem about “anemic models”, if fits to what you are doing like a tee.

Anemic domain model

@tony_marston404

This is about ROW level security, not FIELD level security.

Field level security is a higher resolution for security. I am sure row level security can also be accomplished fairly easily.

@tony_marston404

I do have support for web services, but that has to be customised for each user’s requirements.

I do not have templating for free style page creation as it has never been a user requirement.

I do not have composer support as it is not a user requirement.

I do not have unit testing as it would be far too expensive to retro-fit into an existing and huge application. Besides, it has never been a user requirement, and no user would be willing to fund an exercise that would take longer than the original product development and produce no visible benefits.

So, in other words, because Symfony does have these things or at least can be very easily added, Symfony is way ahead of your framework. It might not be your customers asked for these things, but if they use Symfony, they can.

Scott