In order to start drawing the general structure of the Model-View-Controller schema (from this point onward, I'll reference it as MVC) that I plan to build, I'll provide you with a basic hands-on example, which can be appropriately understood with only minor complications.

In short, my example will be structured as follows: I'll build an object-based system, which will be capable of displaying simple messages in different ways, that is in lowercase, uppercase and reverse respectively. Although certainly this system won't have an immediate application in the real world, it will serve as a good introduction to how to construct a MVC relationship with PHP.

Having defined the basic structure of my MVC-based example, I'll begin defining the first element of this schema, in this case the controller itself. This component will be directly represented by a PHP class, which will be responsible for instructing the model (more on this in a moment, thus be patient please) on what types of views, that is lowercase, uppercase and reversed, will be properly generated.

The definition of the example looks really simple, therefore here is how the controller class, which I called "MessageController" will look:

// define 'MessageController' class (controller)
class MessageController{
    private $viewRanges=array('uppercased','lowercased','reversed');
    private $view;
    // constructor
    public function __construct($view='lowercased'){
        if(!in_array($view,$this->viewRanges)){
            throw new Exception('Invalid type of view!');
        }
        $this->view=$view;
    }
    // return type of view
    public function getView(){
        return $this->view;
    }
}

If you examine the signature of the above class, then you'll quickly realize what it does. Basically, this class accepts a type of view to be applied to the future model (as you know, in this example the model will be made up of simple message strings), and stores the inputted view as a new class property.

Aside from the corresponding checking code, pointed out to verify the validity of the view passed in as an argument, the class exposes the "getView()" method, which comes in handy for returning precisely the type of selected view to the calling code. Nothing unexpected, right?

As you'll probably agree, the panorama looks really simple when it comes to creating a controller class with PHP. Now, let's move on and see how a model class can be included as part of the MVC schema.

Based on the practical example that I'm currently developing, the model should be another PHP class, which would accept as an incoming parameter the controller object that you saw before, in order to display messages either in lowercase, uppercase or reversed. Now, do you see the logic followed by the MVC relationship? Great! Therefore, to see how the model class will be created, please click on the link shown below and continue reading.