|
Ciekawe strony |
sambar indyjski zlote globy kopalnia wegla pasawa telefon ochrona wod 1941 brooklyn dodgers season Prawa człowieka Świat JavaScript RSS Tworzenie stron |
| 2.2. The MVC Pattern | ||
|---|---|---|
| Prev | Chapter 2. Basic Concepts | Next |
|
Ciekawe strony |
sambar indyjski zlote globy kopalnia wegla pasawa telefon ochrona wod 1941 brooklyn dodgers season Prawa człowieka Świat JavaScript RSS Tworzenie stron |
| 2.2. The MVC Pattern | ||
|---|---|---|
| Prev | Chapter 2. Basic Concepts | Next |
Model-View-Controller is a software design pattern that helps you logically separate your code, make it more reusable, maintainable, and generally better. Model View Controller was first described by the author group Gang of Four. Dean Helman wrote (an extract from Objective Toolkit Pro white paper):
"The MVC paradigm is a way of breaking an application, or even just a piece of an application's interface, into three parts: the model, the view, and the controller. MVC was originally developed to map the traditional input, processing, output roles into the GUI realm.
Input -> Processing -> Output
Controller -> Model -> View
"The user input, the modeling of the external world, and the visual feedback to the user are separated and handled by model, view port and controller objects. The controller interprets mouse and keyboard inputs from the user and maps these user actions into commands that are sent to the model and/or view port to effect the appropriate change. The model manages one or more data elements, responds to queries about its state, and responds to instructions to change state. The view port manages a rectangular area of the display and is responsible for presenting data to the user through a combination of graphics and text."
In Cake terms, the Model represents a particular database table/record, and it's relationships to other tables and records. Models also contain data validation rules, which are applied when model data is inserted or updated. The View represents Cake's view files, which are regular HTML files embedded with PHP code. Cake's Controller handles requests from the server. It takes user input (URL and POST data), applies business logic, uses Models to read and write data to and from databases and other sources, and lastly, sends output data to the appropriate view file.
To make it as easy as possible to organize your application, Cake uses this pattern not only to manage how objects interact within your application, but also how files are stored, which is detailed next.