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

[tony_marston404]

@mAAdhaTTah

tony_marston404:
This tells me that the framework is in control, not the developer, that the framework should provide default behaviour, and the developer should only need to write code when this default behaviour needs to be changed. How else can this be accomplished?

The framework is in control. Writing:

$app = new Application();
$app->boot();

puts the framework in control. The default behavior is to run your application.

You mean you have to write your own code to get your application going? How quaint! How so-o-o-o last century! All 2,500 user transactions in my application are started from a script such as this:

<?php
$table_id = "person";                      // identify the Model
$screen   = 'person.detail.screen.inc';    // identify the View
require 'std.enquire1.inc';                // activate the Controller
?>

And guess what? Each of these scripts is generated by the framework from a GUI screen. The Controller scripts are part of the framework, and each Model class is generated by the framework from another GUI screen. The $screen script specifies which XSL stylesheet will be used by the standard View component. This is how I can generate the code for a user transaction, and run it immediately from an online menu, without having to write a single line of code - no PHP, no HTML, no SQL. This transaction will automatically include all default behaviour, and the developer only has to write code when he wants to alter this behaviour.