Cakephp /development

CakePHP Development Email : [email_address] Phone: 800-414-4172

What is CakePHP? In simple words CakePHP development is an open source web application framework for producing web related applications. It is written in PHP, modeled after the concepts of Ruby on Rails, and distributed under the MIT License. The only goal is to enable work in a structured and rapid manner–without loss of flexibility.

Like Rails, CakePHP makes application easier for the user to interface with the database with the active record pattern. It also encourages use of the model-view-controller architectural pattern, also it has the following features
Active, friendly community
Compatible with versions 4 and 5 of PHP
Integrated CRUD for database interaction
Application scaffolding
Code generation
MVC architecture
Request dispatcher with clean, custom URLs and routes
Built-in validation
Fast and flexible templating (PHP syntax, with helpers)
Cookie, Security, Session, and Request Handling Components
Why CakePHP?

MVC
Model–View–Controller (MVC) is an architectural pattern used in software engineering. The pattern isolates "domain logic" (the application logic for the user) from input and presentation (GUI), permitting independent development, testing and maintenance of each.
1. The Model represents the application data
2. The View renders a presentation of model data
3. The Controller handles and routes requests made by the client

Basic Principles of CakePHP The CakePHP framework provides a robust base for your application. It can handle every aspect, from the user’s initial request all the way to the final rendering of a web page. And since the framework follows the principles of MVC, it allows easily customize and extend most aspects of application. The framework also provides a basic organizational structure, from file names to database table names, keeping entire application consistent and logical. This concept is simple but powerful.

Components Controller Extensions A Component is a class that aids in controller logic. If you have some logic you want to share between controllers (or applications), a component is usually a good fit. As an example, the core EmailComponent class makes creating and sending emails a snap. Rather than writing a controller method in a single controller that performs this logic. Controllers are also fitted with callbacks. These callbacks are available for just in case need to insert some logic between CakePHP’s core operations. Callbacks available include: beforeFilter(), executed before any controller action logic beforeRender(), executed after controller logic, but before the view is rendered afterFilter(), executed after all controller logic, including the view render. There may be no difference between afterRender() and afterFilter() unless manually made a call to render() in controller action and have included some logic after that call.

Helpers View Extensions A Helper is a class that aids in view logic. Much like a component used among controllers, helpers allow presentational logic to be accessed and shared between views. One of the core helpers, AjaxHelper, makes Ajax requests within views much easier. Most applications have pieces of view code that are used repeatedly. CakePHP facilitates view code reuse with layouts and elements. By default, every view rendered by a controller is placed inside a layout. Elements are used when small snippets of content need to be reused in multiple views.

Behaviors Model Extensions Similarly, Behaviors work as ways to add common functionality between models. For example, if you store user data in a tree structure, you can specify your User model as behaving like a tree, and gain free functionality for removing, adding, and shifting nodes in your underlying tree structure. Models also are supported by another class called a DataSource. DataSources are an abstraction that enable models to manipulate different types of data consistently. While the main source of data in a CakePHP application is often a database, you might write additional DataSources that allow your models to represent RSS feeds, CSV files, LDAP entries.

File and Classname Conventions
In general, filenames are underscored while classnames are CamelCased. So if you have a class MyNiftyClass, then in Cake, the file should be named my_nifty_class.php.
The Controller class UsersAndProfilesController would be found in a file named users_and_profiles_controller.php (notice _controller in the filename)
The Component class MyHandyComponent would be found in a file named my_handy.php
The Model class OptionValue would be found in a file named option_value.php
The Behavior class EspeciallyFunkableBehavior would be found in a file named especially_funkable.php
The View class SuperSimpleView would be found in a file named super_simple.php
The Helper class BestEverHelper would be found in a file named best_ever.php
Each file would be located in or under (can be in a subfolder) the appropriate folder in your app folder.

Database Conventions Table names corresponding to CakePHP models are plural and underscored. The underlying tables for the above mentioned models would be people, big_people, and really_big_people, respectively. Field names with two or more words are underscored like, first_name. Foreign keys in hasMany, belongsTo or hasOne relationships are recognized by default as the (singular) name of the related table followed by _id. So if a Baker hasMany Cake, the cakes table will refer to the bakers table via a baker_id foreign key. For a multiple worded table like category_types, the foreign key would be category_type_id.

Requirements
HTTP Server. For example: Apache. mod_rewrite is preferred, but by no means required.
PHP 4.3.2 or greater. Yes, CakePHP works great on PHP 4 and 5.
Technically a database engine isn’t required, but we imagine that most applications will utilize one. CakePHP supports a variety of database storage engines:
MySQL (4 or greater)
PostgreSQL
Firebird DB2
Microsoft SQL Server
Oracle
SQLite
ODBC
ADOdb

Easy Setup
Download the cakephp in http://github.com/cakephp/cakephp1x/downloads and extract to some location (say cake), and set the env path to cake/cake/console and for the php.
Locate to the webroot and use the command “cake bake <prj_name>” to create the new web application.
The above command will create the web application, then locate root directory to the application “cd <prj_name>”, use “cake bake model” to create the models for the database.
After creating the models use “cake bake controller” to create the controller files, by default the controllers for the basic CURD operation is created here.
Use “cake bake view” for creating the views for the created controller.
Try to open this web application in the browser.
To change the basic layout edit default.ctp file in the views/layouts directory and edit views/pages/home.ctp to edit homepage.

http://www.anubavam.com	242
http://www.slideshare.net	10
http://50.56.31.244	4
http://localhost	3
http://www.sivakumarv.com	2

Cakephp /development

by Anubavam on Jun 01, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

5 Embeds 261

Statistics

Cakephp /development — Presentation Transcript