Codeigniter framework
Download as PPTX, PDF0 likes1,534 views
This document provides an overview of the CodeIgniter PHP web application framework. It discusses motivations for using frameworks like CodeIgniter, including organizing large codebases, separating concerns, and enabling team collaboration. It then explains key CodeIgniter concepts like MVC architecture, and components like models, views, controllers, helpers and libraries. It provides examples of routing requests, loading views, and handling databases. Overall, the document serves as an introduction to CodeIgniter's features and best practices.
Codeigniter framework
- 2. Disclaimer: This presentation is prepared by trainees of baabtra as a part of mentoring program. This is not official document of baabtra –Mentoring Partner Baabtra-Mentoring Partner is the mentoring division of baabte System Technologies Pvt . Ltd
- 4. MOTIVATION • PHP, for small sites this works very well. HTML files can be easily extended with dynamic content from the database, form processing, etc. • When sites grow, you might have realized that across multiple pages lots of code repetition occurs. This is a problem when you need to change certain parts of a page, that affects many or all pages. • Furthermore, its hard to introduce new developers to code someone else has written. It takes a long time to get familiar with the code.
- 5. MOTIVATION… • Enterprise class (big) web applications need structure, one HTML file per page with PHP code is not optimal => things get confusing, hard to work in teams, etc. • Web Application Frameworks provide such a structure which introduce separation of concern, etc. • Most common for Web application development are frameworks that are based on the Model-View- Controller design pattern.
- 6. MODEL – VIEW – CONTROLLER (MVC) • “Separation of concerns” of Logic and Presentation. • Controller: Handles all incoming HTTP requests, passes data to the views. • Models: Encapsulate Business Logic, such as interaction with the database. • For PHP we introduce CodeIgniter.
- 7. CODEIGNITER • CodeIgniter is a PHP-based MVC framework that helps structure your code and make redundant tasks less tedious. • There are countless similar PHP frameworks, the most popular ones being CakePHP and symfony. Ruby on Rails is famous in the Ruby world. • CodeIgniter is very light weight. It doesn„t force any convention but provides • many commonly required features through a set of build in libraries.
- 8. CODEIGNITER - FEATURES • Model-View-Controller Based System • Extremely Light Weight, does not force any convention • Full Featured database classes with support for several platforms • Custom Routing • Form and Data Validation • Security
- 10. APPLICATION FLOW CHART… 1. The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter. 2. The Router examines the HTTP request to determine what should be done with it. 3. If a cache file exists, it is sent directly to the browser, bypassing the normal system execution.
- 11. APPLICATION FLOW CHART… 4. Security, Before the application controller is loaded, the HTTP request and any user submitted data is filtered for security. 5. The Controller loads the model, core libraries, plugins, helpers, and any other resources needed to process the specific request. 6. The finalized View is rendered then sent to the web browser to be seen. If caching is enabled, the view is cached first so that on subsequent requests it can be served.
- 12. GETTING STARTED • Directory Structure of CodeIgniter: • Index.php - recieves all requests and routes to the right controllers classes and actions, parameters are included in the URL. • /system - contains all CodeIgniter classes and libraries provided by the framework • /application - this is where your application code is located, including the model, view and controller classes
- 13. CONTROLLERS • Take incoming HTTP requests and process them • Must be the same filename as the capitalized class name • Must extend the main Controller class of CodeIgniter • Each class function represents an controller action, which is rendering a HTML page • “index” is the default action
- 14. ROUTING REQUESTS • Per default CodeIgniter maps URL to controller actions: /index.php/controller/action • The default controller is “welcome” and the default action is “index”. • Custom routing can be configured through: /application/config/routes.php
- 15. VIEWS • Are HTML pages or page fragments • Those are load and sent by the Controller to the Browser by the use of the following code in den Ctrl: $this->load->view(‘blog_view‘); • There is no application logic in the views, only display logic (to some degree) • <?= is short form for <?php echo
- 16. HELPERS • Helper functions are located in /application/helpers/ • These are small PHP functions that provide shortcuts, to outsource often used code • For example formatting, text, url or form helpers • Needs to be loaded through: $this->load->helper(‘name’);
- 17. LIBRARIES • Libraries are similar to helpers • The also need to be loaded through: $this->load->library('classname'); • The difference is that they encapsulate more complex functionality, such as image processing, form validation handling, caching, etc. • Libraries allow to dynamically extend CodeIgniters functionality and extendability
- 18. DATABASE HANDLING • CodeIgniter provides a simple way to access the database. • It encapsulates the underlying database (MySQL, Oracle, etc) • The connection handling is done by CodeIgniter and configured through: /application/config/database.php • Provides security through automatic escaping of inserted data, avoids Cross-Side Scripting (CSS) attacks
- 19. MODEL • The Model represents your data structures. • Typically your model classes will contain functions that help you retrieve, insert, and update information in your database.
- 20. If this presentation helped you, please visit our page facebook.com/baabtra and like it. Thanks in advance. www.baabtra.com | www.massbaab.com |www.baabte.com
- 21. Contact Us