summaryrefslogtreecommitdiff
path: root/demos
diff options
context:
space:
mode:
authorcarl <>2006-01-18 15:01:50 +0000
committercarl <>2006-01-18 15:01:50 +0000
commitefa8b9e7ce1c700d31fee7d16351159ac5f2e71f (patch)
treea31fd85e0dfdd43259349bf5f8143990890d0845 /demos
parentf5ff6a39ae808bc53513c1353769d9f3088cc0cf (diff)
Fixed a name bug Template pages
Diffstat (limited to 'demos')
-rw-r--r--demos/quickstart/protected/pages/Configurations/Templates1.page6
-rw-r--r--demos/quickstart/protected/pages/Configurations/Templates2.page12
-rw-r--r--demos/quickstart/protected/pages/Configurations/Templates3.page10
3 files changed, 14 insertions, 14 deletions
diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page
index ce539281..37a389ba 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates1.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates1.page
@@ -6,7 +6,7 @@ Templates are used to specify the presentational layout of controls. A template
<p>The template format is like HTML, with a few PRADO-specifc tags, including <a href="#ct">component tags</a>, <a href="#tct">template control tags</a>, <a href="#cot">comment tags</a>, <a href="?page=Configurations.Templates2#dct">dynamic content tags</a>, and <a href="?page=Configurations.Templates3#dpt">dynamic property tags</a>. .
</p>
-<a name="ct" />
+<a name="ct"></a>
<h2>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.
@@ -36,7 +36,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>
-<a name="tct" />
+<a name="tct"></a>
<h2>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">
@@ -51,7 +51,7 @@ Initial values specified via the template control tag are assigned to the corres
Template control tag is optional in a template. Each template can contain at most one template control tag. You can place the template control tag anywhere in the template. It is recommended that you place it at the beginning of the template for better visibility.
</p>
-<a name="cot" />
+<a name="cot"></a>
<h2>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,
diff --git a/demos/quickstart/protected/pages/Configurations/Templates2.page b/demos/quickstart/protected/pages/Configurations/Templates2.page
index cace46b3..ca8d7de4 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates2.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates2.page
@@ -1,13 +1,13 @@
<com:TContent ID="body" >
<h1>Templates: Part II</h1>
-<a name="dct" />
+<a name="dct"></a>
<h2>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 name="et"></a>
<h3>Expression Tags</h3>
<p>
An expression tag represents a PHP expression that is evaluated when the template control is being rendered. The expression evaluation result is inserted at the place where the tag resides in the template. Its format is as follows,
@@ -20,7 +20,7 @@ Inernally, an expression tag is represented by a <tt>TExpression</tt> control. T
</com:TTextHighlighter>
</p>
-<a name="st" />
+<a name="st"></a>
<h3>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. Inernally, a statement tag is represented by a <tt>TStatements</tt> control. Therefore, in the statements <tt>$this</tt> refers to the <tt>TStatements</tt> control. The format of statement tags is as follows,
@@ -40,7 +40,7 @@ echo strftime("%A %e %B %Y",time());
</com:TTextHighlighter>
</p>
-<a name="dt" />
+<a name="dt"></a>
<h3>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. Internally, a <tt>TLiteral</tt> control is used to represent a databind tag and <tt>$this</tt> in the expression would refer to the control. The format of databind tags is as follows,
@@ -49,7 +49,7 @@ Databind tags are similar to expression tags, except that the expressions are ev
</com:TTextHighlighter>
</p>
-<a name="pt" />
+<a name="pt"></a>
<h3>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,
@@ -59,7 +59,7 @@ Parameter tags are used to insert application parameters at the place where they
Note, application parameters are usually defined in application configurations or page directory configurations. The parameters are evaluated when the template is instantiated.
</p>
-<a name="at" />
+<a name="at"></a>
<h3>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.
diff --git a/demos/quickstart/protected/pages/Configurations/Templates3.page b/demos/quickstart/protected/pages/Configurations/Templates3.page
index bec25d13..c1e58e25 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates3.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates3.page
@@ -1,7 +1,7 @@
<com:TContent ID="body" >
<h1>Templates: Part III</h1>
-<a name="dpt" />
+<a name="dpt"></a>
<h2>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,
@@ -16,7 +16,7 @@ where you may enclose <tt>DynamicPropertyTag</tt> within single or double quotes
Like dynamic content tags, we have <a href="#et">expression 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>. (Note, there is no statement tag here.)
</p>
-<a name="et" />
+<a name="et"></a>
<h3>Expression Tags</h3>
<p>
An expression tag represents a PHP expression that is evaluated when the template is being instantiated. The expression evaluation result is assigned to the corresponding component property. The format of expression tags is as follows,
@@ -32,7 +32,7 @@ In the expression, <tt>$this</tt> refers to the component specified by the compo
Note, unlike dynamic content tags, the expressions tags for component properties are evaluated when the components are being constructed, while for the dynamic content tags, the expressions are evaluated when the controls are being rendered.
</p>
-<a name="dt" />
+<a name="dt"></a>
<h3>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 itself. Databind tags do not apply to all components. They can only be used for controls.
@@ -44,7 +44,7 @@ The format of databind tags is as follows,
</com:TTextHighlighter>
</p>
-<a name="pt" />
+<a name="pt"></a>
<h3>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,
@@ -54,7 +54,7 @@ Parameter tags are used to assign application parameter values to the correspond
Note, application parameters are usually defined in application configurations or page directory configurations. The parameters are evaluated when the template is instantiated.
</p>
-<a name="at" />
+<a name="at"></a>
<h3>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.