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

[tony_marston404]

@TomB

THEIR opinion is much more valuable to me than yours, so you might as well keep your opinion to yourself.

Then stop coming here and trying to convince people your framework is “good”.

Some people like my framework, some people don’t.
Some people like the Zend framework, some people don’t.
Some people like the Laravel framework, some people don’t.
Some people like the Symfony framework, some people don’t.
Some people like the CodeIgniter framework, some people don’t.
Some people like the Yii framework, some people don’t.
Some people like the framework, some people don’t.

What does this prove? To each his own. This is a free country, and people are free to determine for themselves what they like and what they dislike.

@TomB

tony_marston404:
Each script therefore specifies a unique combination of Model, View and Controller, therefore there is no violation of DRY.

You do realise it would take longer to navigate into a GUI, move between form fields and type into text boxes than it would to just type out the code in the first place?

But that is not all that my transaction generation process does. For example, the most common transaction pattern in all the applications which I have built is the LIST1. This is part of a family which also includes the ADD1, ENQUIRE1, UPDATE1, DELETE1 and SEARCH1 patterns. When you create a LIST1 task it performs the following:

1. Generates the transaction script for the LIST1 task.
2. Adds the LIST1 task to the TASK table in the MENU database.
3. Adds the LIST1 task to the MENU table in the MENU database.
4. Generates the transaction scripts for the associated ADD1, ENQUIRE1, UPDATE1, DELETE1 and SEARCH1 tasks.
5. Adds ALL these task to the TASK table in the MENU database.
6. Adds ALL these task to the NAVIGATION table in the MENU database.

This means that the LIST1 task will be instantly available on that subsystem’s menu bar, and all the associated tasks will be available on the LIST1 task’s navigation bar. All these tasks will be runnable with default behaviour but without having to write a single line of code - no PHP, no HTML no SQL. Can YOUR framework do that?