diff options
Diffstat (limited to 'user_guide')
| -rw-r--r-- | user_guide/index.html | 9 | ||||
| -rw-r--r-- | user_guide/overview/at_a_glance.html | 13 | ||||
| -rw-r--r-- | user_guide/overview/mvc.html | 2 |
3 files changed, 14 insertions, 10 deletions
diff --git a/user_guide/index.html b/user_guide/index.html index 19a29a6f5..fd2279d5a 100644 --- a/user_guide/index.html +++ b/user_guide/index.html @@ -80,12 +80,13 @@ then read the <a href="general/index.html">Getting Started</a> page.</p> <ul>
<li>You want a framework with a small footprint.</li>
-<li>You are not interested in large-scale, monolithic libraries, like PEAR.</li>
-<li>You need broad compatibility with standard hosting accounts that run a variety of PHP versions and configurations.</li>
+<li>You need exceptional performance.</li>
+<li>You need broad compatibility with standard hosting accounts that run a variety of PHP versions and configurations.</li>
<li>You want a framework that requires nearly zero configuration.</li>
<li>You want a framework that does not require you to use the command line.</li>
-<li>You do not want to be forced to learn a templating language.</li>
-<li>You need exceptional performance.</li>
+<li>You want a framework that doesn't require you to adhere to restrictive coding rules.</li>
+<li>You are not interested in large-scale monolithic libraries like PEAR.</li>
+<li>You do not want to be forced to learn a templating language (although a template parser is optionally available if you desire one).</li>
<li>You eschew complexity, favoring simple solutions.</li>
<li>You need clear, thorough documentation.</li>
</ul>
diff --git a/user_guide/overview/at_a_glance.html b/user_guide/overview/at_a_glance.html index ca911cbe0..14e2f0524 100644 --- a/user_guide/overview/at_a_glance.html +++ b/user_guide/overview/at_a_glance.html @@ -90,6 +90,10 @@ Additional libraries are loaded dynamically upon request, based on your needs fo is very lean and quite fast.
</p>
+<h2>Code Igniter is Fast</h2>
+<p>Really fast. We challenge you to find a framework that has better performance the Code Igniter.</p>
+
+
<h2>Code Igniter Uses M-V-C</h2>
<p>Code Igniter uses the Model-View-Controller approach, which allows great separation between logic and presentation.
This is particularly good for projects in which designers are working with your template files, as the code these file contain will be minimized. We describe MVC in more detail on its own page.</p>
@@ -104,13 +108,15 @@ approach to URLs that is synonymous with dynamic systems, Code Igniter uses a se <h2>Code Igniter Packs a Punch</h2>
<p>Code Igniter comes with a very nice set of libraries that enable the most commonly needed web development tasks,
-like connecting to a database, sending email, validating form data, maintaining sessions, manipulating images, and more.</p>
+like accessing a database, sending email, validating form data, maintaining sessions, manipulating images, working with XML-RPC data and more.</p>
<h2>Code Igniter is Extensible</h2>
<p>The system can be easily extended through the use of plugins and helper files, or even through class extensions or standard includes.</p>
<h2>Code Igniter Does Not Require a Template Engine</h2>
-<p>Template engines simply can not match the performance of native PHP, and the syntax that must be learned to use a template
+<p>Although Code Igniter <em>does</em> come with a simple template parser that can be optionally used, it does not force you to use one.
+
+Template engines simply can not match the performance of native PHP, and the syntax that must be learned to use a template
engine is usually only marginally easier than learning the basics of PHP. Consider this block of PHP code:</p>
<code><ul><br />
@@ -138,9 +144,6 @@ engine is usually only marginally easier than learning the basics of PHP. Consi <p>Yes, the template engine example is a bit cleaner, but it comes at the price of performance, as the pseudo-code must be converted
back into PHP to run. Since one of our goals is <em>maximum performance</em>, we opted to not require the use of a template engine.</p>
-<p>That said, Code Igniter <strong>does</strong> come with a simple template engine class which you can optionally use. Or, if you
-prefer using a full-blown template engine such as Smarty, there's no reason why you can't use it with Code Igniter.
-Just include your template engine script when you write your controllers, and continue working as you normally do.</p>
<h2>Code Igniter is Thoroughly Documented</h2>
<p>Programmers love to code and hate to write documentation. We're no different, of course, but
diff --git a/user_guide/overview/mvc.html b/user_guide/overview/mvc.html index 869451a79..d84d87992 100644 --- a/user_guide/overview/mvc.html +++ b/user_guide/overview/mvc.html @@ -71,7 +71,7 @@ MVC is a software approach that separates application logic from presentation. <li>The <strong>Model</strong> represents your data structures. Typically your model classes will contains functions that help you
retrieve, insert, and update information in your your database.</li>
<li>The <strong>View</strong> is the information that is being presented to a user. A View will normally be a web page, but
-in Code Igniter, a view can also be a page fragment like a header or footer. </li>
+in Code Igniter, a view can also be a page fragment like a header or footer. It can also be an RSS page, or any other type of "page".</li>
<li>The <strong>Controller</strong> serves as an <em>intermediary</em> between the Model, the View,
and any other resources needed to process the HTTP request and generate a web page.</li>
|