From d2df9bc7cc9d4b3e53818470c5d0977c9a36677c Mon Sep 17 00:00:00 2001 From: Derek Allard Date: Sun, 15 Apr 2007 17:41:17 +0000 Subject: update pMachine to EllisLab update copyright year update Code Igniter to CodeIgniter --- user_guide/overview/goals.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'user_guide/overview/goals.html') diff --git a/user_guide/overview/goals.html b/user_guide/overview/goals.html index 07549ed40..b531515f0 100644 --- a/user_guide/overview/goals.html +++ b/user_guide/overview/goals.html @@ -2,7 +2,7 @@ -Code Igniter User Guide +CodeIgniter User Guide @@ -22,7 +22,7 @@ window.onload = function() { - + @@ -33,7 +33,7 @@ window.onload = function() {

- +

Code Igniter User Guide Version 1.5.2

CodeIgniter User Guide Version 1.5.3

Table of Contents Page

@@ -45,7 +45,7 @@ window.onload = function() { @@ -64,20 +64,20 @@ Goals

Design and Architectural Goals

Our goal for Code Igniter is maximum performance, capability, and flexibility in the smallest, lightest possible package.

Our goal for CodeIgniter is maximum performance, capability, and flexibility in the smallest, lightest possible package.

To meet this goal we are committed to benchmarking, re-factoring, and simplifying at every step of the development process, rejecting anything that doesn't further the stated objective.

From an technical and architectural standpoint, Code Igniter was created with the following objectives:

From an technical and architectural standpoint, CodeIgniter was created with the following objectives:

Dynamic Instantiation. In Code Igniter, components are loaded and routines executed only when requested, rather than globally. No assumptions are made by the system regarding what may be needed beyond the minimal core resources, so the system is very light-weight by default. The events, as triggered by the HTTP request, and the controllers and views you design will determine what is invoked.
Dynamic Instantiation. In CodeIgniter, components are loaded and routines executed only when requested, rather than globally. No assumptions are made by the system regarding what may be needed beyond the minimal core resources, so the system is very light-weight by default. The events, as triggered by the HTTP request, and the controllers and views you design will determine what is invoked.
Loose Coupling. Coupling is the degree to which components of a system rely on each other. The less components depend on each other the more reusable and flexible the system becomes. Our goal was a very loosely coupled system.
Component Singularity. Singularity is the degree to which components have a narrowly focused purpose. In Code Igniter, each class and its functions are highly autonomous in order to allow maximum usefulness.
Component Singularity. Singularity is the degree to which components have a narrowly focused purpose. In CodeIgniter, each class and its functions are highly autonomous in order to allow maximum usefulness.

Code Igniter is a dynamically instantiated, loosely coupled system with high component singularity. It strives for simplicity, flexibility, and high performance in a small footprint package.

CodeIgniter is a dynamically instantiated, loosely coupled system with high component singularity. It strives for simplicity, flexibility, and high performance in a small footprint package.

@@ -96,7 +96,7 @@ Previous Topic: Model-View-Controller User Guide Home · Next Topic: Getting Started

-- cgit v1.2.3-24-g4f1b