5 files changed, 15 insertions, 15 deletions

diff --git a/demos/quickstart/protected/pages/GettingStarted/AboutPrado.page b/demos/quickstart/protected/pages/GettingStarted/AboutPrado.page
index 6ac58b73..dc8de7ae 100644
--- a/demos/quickstart/protected/pages/GettingStarted/AboutPrado.page
+++ b/demos/quickstart/protected/pages/GettingStarted/AboutPrado.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>What is PRADO?</h1>

+<h1 id="201">What is PRADO?</h1>

 <p>

 PRADO is a component-based and event-driven programming framework for developing Web applications in PHP 5. PRADO stands for <b>P</b>HP <b>R</b>apid <b>A</b>pplication <b>D</b>evelopment <b>O</b>bject-oriented.

 </p>

@@ -16,7 +16,7 @@ To facilitate interacting with components, PRADO implements an event-driven prog
 In summary, developing a PRADO Web application mainly involves instantiating prebuilt component types, configuring them by setting their properties, responding to their events by writing handler functions, and composing them into pages for the application. It is very similar to RAD toolkits, such as Borland Delphi and Microsoft Visual Basic, that are used to develop desktop GUI applications.

 </p>

 

-<h2>Why PRADO?</h2>

+<h2 id="202">Why PRADO?</h2>

 <p>

 PRADO is mostly quoted as a unique framework. In fact, it is so unique that it may turn your boring PHP programming into a fun task. The following list is a short summary of the main features of PRADO,

 </p>

@@ -32,7 +32,7 @@ PRADO is mostly quoted as a unique framework. In fact, it is so unique that it m
 <li>Other features - Powerful error/exception handling and message logging; generic caching and selective output caching; customizable and localizable error handling; extensible authentication and authorization; security measures such as cross-site script (CSS) prevention, cookie protection, etc.</li>

 </ul>

 

-<h2>What Is PRADO Best For?</h2>

+<h2 id="203">What Is PRADO Best For?</h2>

 <p>

 PRADO is best suitable for creating Web front-ends that are highly user-interactive and require small to medium traffic. It can be used to develop systems as simple as a blog system to systems as complex as a content management system (CMS) or a complete e-commerce solution. PRADO can help you cut your development time significantly.

 </p>

@@ -43,7 +43,7 @@ PRADO does not exclude other back-end solutions such as most DB abstraction laye
 Without caching techniques, PRADO may not be suitable for developing extremely high-traffic Web applications, such as popular portals, forums, etc. In these applications, every niche of potential performance gain must be exploited and server caching (e.g. Zend optimizer) is almost a must. PRADO implements a generic cache technique and enables selective caching of part of Web contents.

 </p>

 

-<h2>How Is PRADO Compared with Other Frameworks?</h2>

+<h2 id="204">How Is PRADO Compared with Other Frameworks?</h2>

 <p>

 PRADO is described as a unique framework. Its uniqueness mainly lies in the component-based and event-driven programming paradigm that it tries to promote. Although this programming paradigm is not new in desktop application programming and not new in a few Web programming languages, PRADO is perhaps the first PHP framework enabling it.

 </p>

@@ -51,7 +51,7 @@ PRADO is described as a unique framework. Its uniqueness mainly lies in the comp
 Most PHP frameworks are trying to establish a loose standard of organizing PHP programming, most preferably the MVC (model-view-controller) model. It is difficult to compare PRADO with these frameworks because they have different focuses. What we can say is, PRADO is more like a high-level language built upon PHP, while the MVC frameworks stand for the best programming practices. Both aim to help developers to rapidly complete Web application development. The advantage of PRADO is its rich set of prebuilt powerful components and extreme reusability of the PRADO code, while the advantage of the MVC frameworks is the complete separation of model, view and controller, which greatly facilitates team integration.

 </p>

 

-<h2>History of PRADO</h2>

+<h2 id="205">History of PRADO</h2>

 <p>

 The very original inspiration of PRADO came from Apache Tapestry. During the design and implementation, I borrowed many ideas from Borland Delphi and Microsoft ASP.NET. The first version of PRADO came out in June 2004 and was written in PHP 4. Driven by the Zend PHP 5 coding contest, I rewrote PRADO in PHP 5, which proved to be a wise move, thanks to the new object model provided by PHP 5. PRADO won the grand prize in the Zend contest, earning the highest votes from both the public and the judges' panel.

 </p>

diff --git a/demos/quickstart/protected/pages/GettingStarted/HelloWorld.page b/demos/quickstart/protected/pages/GettingStarted/HelloWorld.page
index b5016f4e..780c92b9 100644
--- a/demos/quickstart/protected/pages/GettingStarted/HelloWorld.page
+++ b/demos/quickstart/protected/pages/GettingStarted/HelloWorld.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>My First PRADO Application</h1>

+<h1 id="401">My First PRADO Application</h1>

 <p>

 In this section, we guide you through creating your first PRADO application, the famous "Hello World" application.

 </p>

diff --git a/demos/quickstart/protected/pages/GettingStarted/Installation.page b/demos/quickstart/protected/pages/GettingStarted/Installation.page
index ae3d18c3..07a76042 100644
--- a/demos/quickstart/protected/pages/GettingStarted/Installation.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Installation.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>Installing PRADO</h1>

+<h1 id="301">Installing PRADO</h1>

 <p>

 If you are viewing this page from your own Web server, you are already done with the installation.

 </p>

diff --git a/demos/quickstart/protected/pages/GettingStarted/Introduction.page b/demos/quickstart/protected/pages/GettingStarted/Introduction.page
index 3f3ea168..42ee0dad 100644
--- a/demos/quickstart/protected/pages/GettingStarted/Introduction.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Introduction.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>Welcome to the PRADO QuickStart Tutorial</h1>

+<h1 id="101">Welcome to the PRADO QuickStart Tutorial</h1>

 <p>

 This QuickStart tutorial is provided to help you quickly start building your own Web applications based on PRADO version 3.0.

 </p>

diff --git a/demos/quickstart/protected/pages/GettingStarted/Upgrading.page b/demos/quickstart/protected/pages/GettingStarted/Upgrading.page
index 287d3f84..cff4e72f 100644
--- a/demos/quickstart/protected/pages/GettingStarted/Upgrading.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Upgrading.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Upgrading from v2.x and v1.x</h1>

+<h1 id="501">Upgrading from v2.x and v1.x</h1>

 

 <p>

 PRADO v3.0 is NOT backward compatible with earlier versions of PRADO.

@@ -12,7 +12,7 @@ A good news is, properties and events of most controls remain intact, and the sy
 We summarize in the following the most significant changes in v3.0 to help developers upgrade their v2.x and v1.x PRADO applications more easily, if needed.

 </p>

 

-<h2>Component Definition</h2>

+<h2 id="502">Component Definition</h2>

 <p>

 Version 3.0 has completely discarded the need of component specification files. It relies more on conventions for defining component properties and events. In particular, a property is defined by the existence of a getter method and/or a setter method, while an event is defined by the existence of an <tt>on</tt>-method. Property and event names in v3.0 are both case-insensitive. As a consequence, developers are now required to take care of type conversions when a component property is being set. For example, the following code is used to define the setter method for the <tt>Enabled</tt> property of <tt>TControl</tt>, which is of <tt>boolean</tt> type,

 </p>

@@ -27,22 +27,22 @@ public function setEnabled($value)
 where <tt>TPropertyValue::ensureBoolean()</tt> is used to ensure that the input value be a boolean. This is because when the property is configured in template, a string value is passed to the setter. In previous versions, PRADO knows the property type based on the component specification files and does the type conversion for you.

 </p>

 

-<h2>Application Controller</h2>

+<h2 id="503">Application Controller</h2>

 <p>

 Application controller now implements a modular architecture. Modules can be plugged in and configured in application specifications. Each module assumes a particular functionality, and they are coordinated together by the <a href="?page=Fundamentals.Applications">application lifecycle</a>. The concept of v2.x modules is replaced in v3.0 by <a href="?page=Configurations.PageConfig">page directories</a>. As a result, the format of v3.0 <a href="?page=Configurations.AppConfig">application specification</a> is also different from earlier versions.

 </p>

 

-<h2>Pages</h2>

+<h2 id="504">Pages</h2>

 <p>

 Pages in v3.0 are organized in directories which may be compared to the module concept in v2.x. Pages are requested using the path to them. For example, a URL <tt>index.php?page=Controls.Samples.Sample1</tt> would be used to request for a page named <tt>Sample1</tt> stored under the <tt>[BasePath]/Controls/Samples</tt> directory, where <tt>[BasePath]</tt> refers to the root page path. The file name of a page template must be ended with <tt>.page</tt>, mainly to differentiate page templates from non-page control templates whose file names must be ended with <tt>.tpl</tt>.

 </p>

 

-<h2>Control Relationship</h2>

+<h2 id="505">Control Relationship</h2>

 <p>

 Version 3.0 redefines the relationships between controls. In particular, the parent-child relationship now refers to the enclosure relationship between controls' presentation. And a new naming-container relationship is introduced to help better manage control IDs. For more details, see the <a href="?page=Fundamentals.Controls">controls</a> section.

 </p>

 

-<h2>Template Syntax</h2>

+<h2 id="506">Template Syntax</h2>

 <p>

 The syntax of control templates in v3.0 remains similar to those in earlier versions, with many enhancements. A major change is about the databinding expression. In v3.0, this is done by the following,

 </p>

@@ -53,7 +53,7 @@ The syntax of control templates in v3.0 remains similar to those in earlier vers
 Expression and statement tags are also changed similarly. For more details, see the <a href="?page=Configurations.Templates1">template definition</a> section.

 </p>

 

-<h2>Theme Syntax</h2>

+<h2 id="507">Theme Syntax</h2>

 <p>

 Themes in v3.0 are defined like control templates with a few restrictions.

 </p>