CodeIgniter - Application Architecture

The architecture of CodeIgniter application is shown below.

• As shown in the figure, whenever a request comes to CodeIgniter, it will first go to index.php page.
• In the second step, Routing will decide whether to pass this request to step-3 for caching or to pass this request to step-4 for security check.
• If the requested page is already in Caching, then Routing will pass the request to step-3 and the response will go back to the user.
• If the requested page does not exist in Caching, then Routing will pass the requested page to step-4 for Security checks.
• Before passing the request to Application Controller, the Securityof the submitted data is checked. After the Security check, the Application Controller loads necessary Models, Libraries, Helpers, Plugins and Scripts and pass it on to View.
• The View will render the page with available data and pass it on for Caching. As the requested page was not cached before so this time it will be cached in Caching, to process this page quickly for future requests.

Directory Structure

The image given below shows the directory structure of the CodeIgniter.

CodeIgniter directory structure is divided into 3 folders −

• Application
• System
• User_guide

Application

As the name indicates the Application folder contains all the code of your application that you are building. This is the folder where you will develop your project. The Application folder contains several other folders, which are explained below −

• Cache − This folder contains all the cached pages of your application. These cached pages will increase the overall speed of accessing the pages.
• Config − This folder contains various files to configure the application. With the help of config.php file, user can configure the application. Using database.php file, user can configure the database of the application.
• Controllers − This folder holds the controllers of your application. It is the basic part of your application.
• Core − This folder will contain base class of your application.
• Helpers − In this folder, you can put helper class of your application.
• Hooks − The files in this folder provide a means to tap into and modify the inner workings of the framework without hacking the core files.
• Language − This folder contains language related files.
• Libraries − This folder contains files of the libraries developed for your application.
• Logs − This folder contains files related to the log of the system.
• Models − The database login will be placed in this folder.
• Third_party − In this folder, you can place any plugins, which will be used for your application.
• Views − Application’s HTML files will be placed in this folder.

System

This folder contains CodeIgniter core codes, libraries, helpers and other files, which help make the coding easy. These libraries and helpers are loaded and used in web app development.

This folder contains all the CodeIgniter code of consequence, organized into various folders −

• Core − This folder contains CodeIgniter’s core class. Do not modify anything here. All of your work will take place in the application folder. Even if your intent is to extend the CodeIgniter core, you have to do it with hooks, and hooks live in the application folder.
• Database − The database folder contains core database drivers and other database utilities.
• Fonts − The fonts folder contains font related information and utilities.
• Helpers − The helpers folder contains standard CodeIgniter helpers (such as date, cookie, and URL helpers).
• Language − The language folder contains language files. You can ignore it for now.
• Libraries − The libraries folder contains standard CodeIgniter libraries (to help you with e-mail, calendars, file uploads, and more). You can create your own libraries or extend (and even replace) standard ones, but those will be saved in the application/libraries directory to keep them separate from the standard CodeIgniter libraries saved in this particular folder.

User_guide

This is your user guide to CodeIgniter. It is basically, the offline version of user guide on CodeIgniter website. Using this, one can learn the functions of various libraries, helpers and classes. It is recommended to go through this user guide before building your first web app in CodeIgniter.

Beside these three folders, there is one more important file named “index.php”. In this file, we can set the application environment and error level and we can define system and application folder name. It is recommended, not to edit these settings if you do not have enough knowledge about what you are going to do.

Read More

CodeIgniter - Overview

CodeIgniter is an application development framework, which can be used to develop websites, using PHP. It is an Open Source framework. It has a very rich set of functionality, which will increase the speed of website development work.

If you know PHP well, then CodeIgniter will make your task easier. It has a very rich set of libraries and helpers. By using CodeIgniter, you will save a lot of time, if you are developing a website from scratch. Not only that, a website built in CodeIgniter is secure too, as it has the ability to prevent various attacks that take place through websites.

CodeIgniter Features

Some of the important features of CodeIgniter are listed below −

• Model-View-Controller Based System
• Extremely Light Weight
• Full Featured database classes with support for several platforms.
• Query Builder Database Support
• Form and Data Validation
• Security and XSS Filtering
• Session Management
• Email Sending Class. Supports Attachments, HTML/Text email, multiple protocols (sendmail, SMTP, and Mail) and more.
• Image Manipulation Library (cropping, resizing, rotating, etc.). Supports GD, ImageMagick, and NetPBM
• File Uploading Class
• FTP Class
• Localization
• Pagination
• Data Encryption
• Benchmarking
• Full Page Caching
• Error Logging
• Application Profiling
• Calendaring Class
• User Agent Class
• Zip Encoding Class
• Template Engine Class
• Trackback Class
• XML-RPC Library
• Unit Testing Class
• Search-engine Friendly URLs
• Flexible URI Routing
• Support for Hooks and Class Extensions
• Large library of “helper” functions
• 
  

Read More

CodeIgniter - Overview

CodeIgniter is an application development framework, which can be used to develop websites, using PHP. It is an Open Source framework. It has a very rich set of functionality, which will increase the speed of website development work.

If you know PHP well, then CodeIgniter will make your task easier. It has a very rich set of libraries and helpers. By using CodeIgniter, you will save a lot of time, if you are developing a website from scratch. Not only that, a website built in CodeIgniter is secure too, as it has the ability to prevent various attacks that take place through websites.

CodeIgniter Features

Some of the important features of CodeIgniter are listed below −

• Model-View-Controller Based System
• Extremely Light Weight
• Full Featured database classes with support for several platforms.
• Query Builder Database Support
• Form and Data Validation
• Security and XSS Filtering
• Session Management
• Email Sending Class. Supports Attachments, HTML/Text email, multiple protocols (sendmail, SMTP, and Mail) and more.
• Image Manipulation Library (cropping, resizing, rotating, etc.). Supports GD, ImageMagick, and NetPBM
• File Uploading Class
• FTP Class
• Localization
• Pagination
• Data Encryption
• Benchmarking
• Full Page Caching
• Error Logging
• Application Profiling
• Calendaring Class
• User Agent Class
• Zip Encoding Class
• Template Engine Class
• Trackback Class
• XML-RPC Library
• Unit Testing Class
• Search-engine Friendly URLs
• Flexible URI Routing
• Support for Hooks and Class Extensions
• Large library of “helper” functions
• 
  

Read More

CodeIgniter Tutorial

CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications. CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology.

Audience

This tutorial has been prepared for developers who would like to learn the art of developing websites using CodeIgniter. It provides a complete understanding of this framework.

Prerequisites

Before you start proceeding with this tutorial, we assume that you are already exposed to HTML, Core PHP, and Advance PHP. We have used CodeIgniter version 3.0.1 in all the examples.

Read More

CodeIgniter Tutorial

CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications. CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology.

Audience

This tutorial has been prepared for developers who would like to learn the art of developing websites using CodeIgniter. It provides a complete understanding of this framework.

Prerequisites

Before you start proceeding with this tutorial, we assume that you are already exposed to HTML, Core PHP, and Advance PHP. We have used CodeIgniter version 3.0.1 in all the examples.

Read More

Laravel - Namespaces

Namespaces are used in various programming languages to create a separate group of variable, functions and classes. A program may contain various functions and this may result in conflict with existing functions. Namespaces play a key role in avoiding such conflicts. This chapter gives you a detailed knowledge of namespaces and their usage in Laravel.

Declaration of namespace

Namespaces can be defined as a class of elements in which each element has a unique name to that associated class. It may be shared with elements in other classes.

You can declare a namespace as shown in the syntax given below −

use <namespace-name>;

Please note that the use keyword allows the developers to shorten the namespace. The default namespace used in Laravel is app, however a user can change the namespace to match with a web application.

You can create a user defined namespace by using artisan command as shown below −

php artisan app:name Coderfunda

On giving the above command, you can observe the output as shown in the following screenshot −

The namespace once created can include various functionalities which can be used in controllers and various classes. The code created on the basis of namespace in controller and kernel with files namely app/console/kernel.php and app/Http/controller.php are shown below −

Kernel.php

<?php

namespace Coderfunda\Console;

use Illuminate\Console\Scheduling\Schedule;
use Illuminate\Foundation\Console\Kernel as ConsoleKernel;

class Kernel extends ConsoleKernel{
   
   /**
      * The Artisan commands provided by your application.
      *
      * @var array
   */
   
   protected $commands = [
    //
   ];
   
   /**
      * Define the application's command schedule.
      *
      * @param \Illuminate\Console\Scheduling\Schedule $schedule
      * @return void
   */
   
   protected function schedule(Schedule $schedule){
      // $schedule->command('inspire')
      // ->hourly();
   }
   
   /**
      * Register the Closure based commands for the application.
      *
      * @return void
   */
   
   protected function commands(){
      require base_path('routes/console.php');
   }
}

Note that the functions namely schedule and commands helps in scheduling methods for Cron jobs and other functionalities.

Controller.php

<?php
namespace Coderfunda\Http\Controllers;

use Illuminate\Foundation\Bus\DispatchesJobs;
use Illuminate\Routing\Controller as BaseController;
use Illuminate\Foundation\Validation\ValidatesRequests;
use Illuminate\Foundation\Auth\Access\AuthorizesRequests;

class Controller extends BaseController{
   use AuthorizesRequests, DispatchesJobs, ValidatesRequests;
}

The controllers act as an intermediary between models and views. For the namespace which we created called Coderfunda, they will be used in core file of controllers controller.php. The namespace is initialized properly with The namespace once created uses various other namespaces like AuthorizesRequests, DispatchesJobs and ValidatesRequests as mentioned in the above code.

Use Keyword

Namespaces take place in the position of current class. As mentioned in our example we have declared Coderfunda as our namespace and it is located in the app folder. The namespace declared will be . Whenever you want to use that class, you should use the use keyword.

The syntax for using use keyword is shown here −

Read More

Laravel - Namespaces

Namespaces are used in various programming languages to create a separate group of variable, functions and classes. A program may contain various functions and this may result in conflict with existing functions. Namespaces play a key role in avoiding such conflicts. This chapter gives you a detailed knowledge of namespaces and their usage in Laravel.

Declaration of namespace

Namespaces can be defined as a class of elements in which each element has a unique name to that associated class. It may be shared with elements in other classes.

You can declare a namespace as shown in the syntax given below −

use <namespace-name>;

Please note that the use keyword allows the developers to shorten the namespace. The default namespace used in Laravel is app, however a user can change the namespace to match with a web application.

You can create a user defined namespace by using artisan command as shown below −

php artisan app:name Coderfunda

On giving the above command, you can observe the output as shown in the following screenshot −

The namespace once created can include various functionalities which can be used in controllers and various classes. The code created on the basis of namespace in controller and kernel with files namely app/console/kernel.php and app/Http/controller.php are shown below −

Kernel.php

<?php

namespace Coderfunda\Console;

use Illuminate\Console\Scheduling\Schedule;
use Illuminate\Foundation\Console\Kernel as ConsoleKernel;

class Kernel extends ConsoleKernel{
   
   /**
      * The Artisan commands provided by your application.
      *
      * @var array
   */
   
   protected $commands = [
    //
   ];
   
   /**
      * Define the application's command schedule.
      *
      * @param \Illuminate\Console\Scheduling\Schedule $schedule
      * @return void
   */
   
   protected function schedule(Schedule $schedule){
      // $schedule->command('inspire')
      // ->hourly();
   }
   
   /**
      * Register the Closure based commands for the application.
      *
      * @return void
   */
   
   protected function commands(){
      require base_path('routes/console.php');
   }
}

Note that the functions namely schedule and commands helps in scheduling methods for Cron jobs and other functionalities.

Controller.php

<?php
namespace Coderfunda\Http\Controllers;

use Illuminate\Foundation\Bus\DispatchesJobs;
use Illuminate\Routing\Controller as BaseController;
use Illuminate\Foundation\Validation\ValidatesRequests;
use Illuminate\Foundation\Auth\Access\AuthorizesRequests;

class Controller extends BaseController{
   use AuthorizesRequests, DispatchesJobs, ValidatesRequests;
}

The controllers act as an intermediary between models and views. For the namespace which we created called Coderfunda, they will be used in core file of controllers controller.php. The namespace is initialized properly with The namespace once created uses various other namespaces like AuthorizesRequests, DispatchesJobs and ValidatesRequests as mentioned in the above code.

Use Keyword

Namespaces take place in the position of current class. As mentioned in our example we have declared Coderfunda as our namespace and it is located in the app folder. The namespace declared will be . Whenever you want to use that class, you should use the use keyword.

The syntax for using use keyword is shown here −

Read More