6 files changed, 23 insertions, 23 deletions

diff --git a/demos/quickstart/protected/pages/Configurations/AppConfig.page b/demos/quickstart/protected/pages/Configurations/AppConfig.page
index 48243200..e15f1eea 100644
--- a/demos/quickstart/protected/pages/Configurations/AppConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/AppConfig.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Application Configurations</h1>

+<h1 id="1801">Application Configurations</h1>

 <p>

 Application configurations are used to specify the global behavior of an application. They include specification of path aliases, namespace usages, module and service configurations, and parameters.

 </p>

diff --git a/demos/quickstart/protected/pages/Configurations/Overview.page b/demos/quickstart/protected/pages/Configurations/Overview.page
index 4a23f306..ec606941 100644
--- a/demos/quickstart/protected/pages/Configurations/Overview.page
+++ b/demos/quickstart/protected/pages/Configurations/Overview.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>Configuration Overview</h1>

+<h1 id="1401">Configuration Overview</h1>

 <p>

 PRADO uses configurations to glue together components into pages and applications. There are <a href="?page=Configurations.AppConfig">application configurations</a>, <a href="?page=Configurations.PageConfig">page configurations</a>, and <a href="?page=Configurations.Templates1">templates</a>.

 </p>

diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page
index 01710d59..b0ef5ccb 100644
--- a/demos/quickstart/protected/pages/Configurations/PageConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Page Configurations</h1>

+<h1 id="1901">Page Configurations</h1>

 <p>

 Page configurations are mainly used by <tt>TPageService</tt> to modify or append the application configuration. As the name indicates, a page configuration is associated with a directory storing some page files. It is stored as an XML file named <tt>config.xml</tt>.

 </p>

diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page
index 483ef1d1..3f2fcc5e 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates1.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates1.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body" >

-<h1>Templates: Part I</h1>

+<h1 id="1501">Templates: Part I</h1>

 <p>

 Templates are used to specify the presentational layout of controls. A template can contain static text, components, or controls that contribute to the ultimate presentation of the associated control. By default, an instance of <tt>TTemplateControl</tt> or its subclass may automatically load and instantiate a template from a file whose name is the same as the control class name. For page templates, the file name suffix must be <tt>.page</tt>; for other regular template controls, the suffix is <tt>.tpl</tt>.

 </p>

@@ -7,7 +7,7 @@ Templates are used to specify the presentational layout of controls. A template
 </p>

 

 <a name="ct"></a>

-<h2>Component Tags</h2>

+<h2 id="1502">Component Tags</h2>

 <p>

 A component tag specifies a component as part of the body content of the template control. If the component is a control, it usually will become a child or grand child of the template control, and its rendering result will be inserted at the place where it is appearing in the template.

 </p>

@@ -43,7 +43,7 @@ PropertyValue
 It is equivalent to <tt>...PropertyName="PropertyValue"...</tt> in every aspect. Property initialization tags must be directly enclosed between the corresponding opening and closing component tag.

 </p>

 

-<h3>Component IDs</h3>

+<h3 id="1505">Component IDs</h3>

 <p>

 When specified in templates, component <tt>ID</tt> property has special meaning in addition to its normal property definition. A component tag specified with an ID value in template will register the corresponding component to the template owner control. The component can thus be directly accessed from the template control with its ID value. For example, in <tt>Home</tt> page's template, the following component tag

 <com:TTextHighlighter Language="prado" CssClass="source">

@@ -53,7 +53,7 @@ makes it possible to get the textbox object in code using <tt>$page->TextBox</tt
 </p>

 

 <a name="tct"></a>

-<h2>Template Control Tags</h2>

+<h2 id="1503">Template Control Tags</h2>

 A template control tag is used to configure the initial property values of the control owning the template. Its format is as follows,

 <com:TTextHighlighter Language="prado" CssClass="source">

 &lt;%@ PropertyName="PropertyValue" ... %&gt;

@@ -68,7 +68,7 @@ Template control tag is optional in a template. Each template can contain at mos
 </p>

 

 <a name="cot"></a>

-<h2>Comment Tags</h2>

+<h2 id="1504">Comment Tags</h2>

 <p>

 Comment tags are used to put comments in the template or the ultimate rendering result. There are two types of comment tags. One is like that in HTML and will be displayed to the end-users. The other only appear in a template and will be stripped out when the template is instantiated and displayed to the end-users. The format of these two comment tags is as follows,

 </p>

diff --git a/demos/quickstart/protected/pages/Configurations/Templates2.page b/demos/quickstart/protected/pages/Configurations/Templates2.page
index 17502151..201c526f 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates2.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates2.page
@@ -1,14 +1,14 @@
 <com:TContent ID="body" >

-<h1>Templates: Part II</h1>

+<h1 id="1601">Templates: Part II</h1>

 

 <a name="dct"></a>

-<h2>Dynamic Content Tags</h2>

+<h2 id="1602">Dynamic Content Tags</h2>

 <p>

 Dynamic content tags are introduced as shortcuts to some commonly used <a href="?page=Configurations.Templates1#ct">component tags</a>. These tags are mainly used to render contents resulted from evaluating some PHP expressions or statements. They include <a href="#et">expression tags</a>, <a href="#st">statement tags</a>, <a href="#dt">databind tags</a>, <a href="#pt">parameter tags</a>, <a href="#at">asset tags</a> and <a href="#lot">localization tags</a>.

 </p>

 

 <a name="et"></a>

-<h3>Expression Tags</h3>

+<h3 id="1603">Expression Tags</h3>

 <p>

 An expression tag represents a PHP expression that is evaluated when the template control is in <tt>PreRender</tt> stage. The expression evaluation result is inserted at the place where the tag resides in the template. The context (namely <tt>$this</tt>) of the expression is the control owning the template.

 </p>

@@ -26,7 +26,7 @@ For example, the following expression tag will display the current page title at
 </com:TTextHighlighter>

 

 <a name="st"></a>

-<h3>Statement Tags</h3>

+<h3 id="1604">Statement Tags</h3>

 <p>

 Statement tags are similar to expression tags, except that statement tags contain PHP statements rather than expressions. The output of the PHP statements (using for example <tt>echo</tt> or <tt>print</tt> in PHP) are displayed at the place where the statement tag resides in the template. The context (namely <tt>$this</tt>) of the statements is the control owning the template. The format of statement tags is as follows,

 </p>

@@ -46,7 +46,7 @@ echo strftime("%A %e %B %Y",time());
 </com:TTextHighlighter>

 

 <a name="dt"></a>

-<h3>Databind Tags</h3>

+<h3 id="1605">Databind Tags</h3>

 <p>

 Databind tags are similar to expression tags, except that the expressions are evaluated only when a <tt>dataBind()</tt> call is invoked on the controls representing the databind tags. The context (namely <tt>$this</tt>) of a databind expression is the control owning the template. The format of databind tags is as follows,

 </p>

@@ -55,7 +55,7 @@ Databind tags are similar to expression tags, except that the expressions are ev
 </com:TTextHighlighter>

 

 <a name="pt"></a>

-<h3>Parameter Tags</h3>

+<h3 id="1606">Parameter Tags</h3>

 <p>

 Parameter tags are used to insert application parameters at the place where they appear in the template. The format of parameter tags is as follows,

 </p>

@@ -67,7 +67,7 @@ Note, application parameters are usually defined in application configurations o
 </p>

 

 <a name="at"></a>

-<h3>Asset Tags</h3>

+<h3 id="1607">Asset Tags</h3>

 <p>

 Asset tags are used to publish private files and display the corresponding the URLs. For example, if you have an image file that is not Web-accessible and you want to make it visible to end-users, you can use asset tags to publish this file and show the URL to end-users so that they can fetch the published image.

 </p>

@@ -85,7 +85,7 @@ BE VERY CAUTIOUS when you are using asset tags as it may expose to end-users fil
 </p>

 

 <a name="lot"></a>

-<h3>Localization Tags</h3>

+<h3 id="1608">Localization Tags</h3>

 <p>

 Localization tags represent localized texts. They are in the following format,

 </p>

diff --git a/demos/quickstart/protected/pages/Configurations/Templates3.page b/demos/quickstart/protected/pages/Configurations/Templates3.page
index 457c1a38..99d43665 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates3.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates3.page
@@ -1,8 +1,8 @@
 <com:TContent ID="body" >

-<h1>Templates: Part III</h1>

+<h1 id="1701">Templates: Part III</h1>

 

 <a name="dpt"></a>

-<h2>Dynamic Property Tags</h2>

+<h2 id="1702">Dynamic Property Tags</h2>

 <p>

 Dynamic property tags are very similar to dynamic content tags, except that they are applied to component properties. The purpose of dynamic property tags is to allow more versatile component property configuration. Note, you are not required to use dynamic property tags because what can be done using dynamic property tags can also be done in PHP code. However, using dynamic property tags bring you much more convenience at accomplishing the same tasks. The basic usage of dynamic property tags is as follows,

 </p>

@@ -19,7 +19,7 @@ Like dynamic content tags, we have <a href="#et">expression tags</a>, <a href="#
 </p>

 

 <a name="et"></a>

-<h3>Expression Tags</h3>

+<h3 id="1703">Expression Tags</h3>

 <p>

 An expression tag represents a PHP expression that is evaluated when the control is in <tt>PreRender</tt> stage. The expression evaluation result is assigned to the corresponding component property. The format of expression tags is as follows,

 </p>

@@ -34,7 +34,7 @@ In the expression, <tt>$this</tt> refers to the control owning the template. The
 </com:TTextHighlighter>

 

 <a name="dt"></a>

-<h3>Databind Tags</h3>

+<h3 id="1704">Databind Tags</h3>

 <p>

 Databind tags are similar to expression tags, except that they can only be used with control properties and the expressions are evaluated only when a <tt>dataBind()</tt> call is invoked on the controls represented by the component tags. In the expression, <tt>$this</tt> refers to the control owning the template. Databind tags do not apply to all components. They can only be used for controls.

 </p>

@@ -46,7 +46,7 @@ The format of databind tags is as follows,
 </com:TTextHighlighter>

 

 <a name="pt"></a>

-<h3>Parameter Tags</h3>

+<h3 id="1705">Parameter Tags</h3>

 <p>

 Parameter tags are used to assign application parameter values to the corresponding component properties. The format of parameter tags is as follows,

 </p>

@@ -58,7 +58,7 @@ Note, application parameters are usually defined in application configurations o
 </p>

 

 <a name="at"></a>

-<h3>Asset Tags</h3>

+<h3 id="1706">Asset Tags</h3>

 <p>

 Asset tags are used to publish private files and assign the corresponding the URLs to the component properties. For example, if you have an image file that is not Web-accessible and you want to make it visible to end-users, you can use asset tags to publish this file and show the URL to end-users so that they can fetch the published image. The asset tags are evaluated when the template is instantiated.

 </p>

@@ -76,7 +76,7 @@ BE VERY CAUTIOUS when you are using asset tags as it may expose to end-users fil
 </p>

 

 <a name="lot"></a>

-<h3>Localization Tags</h3>

+<h3 id="1707">Localization Tags</h3>

 <p>

 Localization tags represent localized texts. They are in the following format,

 </p>