Php.MVC InfoStretch Solutions Pvt. Ltd Prepared By Niranjan Limbachiya Nimesh Chauhan

InfoStretch Solutions Pvt. Ltd

Prepared By

Overview Introduction The Benefits The MVC pattern Concepts The Web-server Directory structure Core components of Php.MVC Library XML Application Configuration System Controller The Action Form & Action Security View Resources

Introduction

The Benefits

The MVC pattern Concepts

The Web-server Directory structure

Core components of Php.MVC Library

XML Application Configuration System

Controller

The Action Form & Action

Security

View

Resources

Introduction php.MVC is a M odel V iew C ontroller (MVC) framework for PHP Web applications The use of this design philosophy makes it easier for designers and programmers to focus on their respective areas of expertise This design model allows Web pages or other contents (Views) to be separated from the applications business logic, or code (Model) php.MVC is a PHP port of the Jakarta Struts project.

php.MVC is a M odel V iew C ontroller (MVC) framework for PHP Web applications

The use of this design philosophy makes it easier for designers and programmers to focus on their respective areas of expertise

This design model allows Web pages or other contents (Views) to be separated from the applications business logic, or code (Model)

php.MVC is a PHP port of the Jakarta Struts project.

Introduction

The Benefits php.MVC is a PHP port of the Jakarta Struts project Enforces modularity and application partitioning Increases developer/designer role separation Increases code manageability Increase code extensibility (Ability to adapt to change)

php.MVC is a PHP port of the Jakarta Struts project

Enforces modularity and application partitioning

Increases developer/designer role separation

Increases code manageability

Increase code extensibility (Ability to adapt to change)

The MVC Pattern Concepts We can see the how a typical HTTP request from a Web client (Web browser) would interact with the core framework classes and our application classes, to produce a HTTP response (Web content) to return to the Web client.

We can see the how a typical HTTP request from a Web client (Web browser) would interact with the core framework classes and our application classes, to produce a HTTP response (Web content) to return to the Web client.

Contd.. To start the process, a client would send our php.MVC application a request perhaps a request to view a particular company sales report http://www.myhost.com/mycompany/Main.php?do=salesReport

To start the process, a client would send our php.MVC application a request

perhaps a request to view a particular company sales report

http://www.myhost.com/mycompany/Main.php?do=salesReport

Web server Directory Structure

MVC Libraries .htaccess control who can access this directory art directory Is used to hold the application graphics, and will be accessible to the Web style directory is used to hold the application style sheets and will also be accessible to the Web /WEB-INF directory This is where we locate the application classes and resources.

.htaccess

control who can access this directory

art directory

Is used to hold the application graphics, and will be accessible to the Web

style directory

is used to hold the application style sheets and will also be accessible to the Web

/WEB-INF directory

This is where we locate the application classes and resources.

Contd.. The tpl directory holds the applications View resources, such as page ModulePaths.php file Is used to define the application specific paths to our classes and resources phpmvc-config.xml file Is the central component of the php.MVC application. phpmvc-config_1_1.dtd file Contains the Document Type Definitions (DTD) for the phpmvc-config.xml file prepend.php file is used to include application files Main.php file is the single entry point for an application, and is located in the application root directory

The tpl directory

holds the applications View resources, such as page

ModulePaths.php file

Is used to define the application specific paths to our classes and resources

phpmvc-config.xml file

Is the central component of the php.MVC application.

phpmvc-config_1_1.dtd file

Contains the Document Type Definitions (DTD) for the phpmvc-config.xml file

prepend.php file is used to include application files

Main.php file

is the single entry point for an application, and is located in the application root directory

Core component of MVC The XML configuration file is the "switchboard" of a php.MVC application. This is how we bind the various components to a HTTP request path The Controller consists of the php.MVC framework classes that are responsible for routing HTTP requests to the correct Form and Action classes and View resources, as defined in the application phpmvc-config.xml file. The Action Form classes can be used to handle Web form checks and validation The Action classes are used to access our business classes. We can direct the application flow to resources based on run-time conditions The Action Dispatcher class handles the resource (template) processing

The XML configuration file is the "switchboard" of a php.MVC application. This is how we bind the various components to a HTTP request path

The Controller consists of the php.MVC framework classes that are responsible for routing

HTTP requests to the correct Form and Action classes and View resources, as defined in the application phpmvc-config.xml file.

The Action Form classes can be used to handle Web form checks and validation

The Action classes are used to access our business classes. We can direct the application flow to resources based on run-time conditions

The Action Dispatcher class handles the resource (template) processing

XML Application configuration system

Example

Controller The Controller component of the php.MVC framework consists of classes that handle a users request according to predefined configuration options A typical user request may look something Like: http://www.myhost.com/mycompany/Main.php?do=salesReport The php.MVC Controller consists of two distinct sections: The Front Controller The Controller proper

The Controller component of the php.MVC framework consists of classes that handle a users request according to predefined configuration options

A typical user request may look something

Like: http://www.myhost.com/mycompany/Main.php?do=salesReport

The php.MVC Controller consists of two distinct sections:

The Front Controller

The Controller proper

Front Controller

The controller

Action Form An ActionForm is represented in the XML Application Configuration like this: The use of an ActionForm for a particular request path is optional, and can be activated in the XML Application Configuration System using the validate attribute of the action mapping node like this

An ActionForm is represented in the XML Application Configuration like this:

The use of an ActionForm for a particular request path is optional, and can be activated in the XML Application Configuration System using the validate attribute of the action mapping node like this

Action An Action class is represented in the XML Application Configuration like this:

An Action class is represented in the XML Application Configuration like this:

Security regular expression (RE) such as "^[a-z0-9]{8}$"

regular expression (RE) such as "^[a-z0-9]{8}$"

View Tpl comes into view Action dispatcher

Tpl comes into view

Action dispatcher

Resources www.phpmvc.net php.MVC on SourceForge

www.phpmvc.net

php.MVC on SourceForge