diff options
author | xue <> | 2006-05-09 12:11:38 +0000 |
---|---|---|
committer | xue <> | 2006-05-09 12:11:38 +0000 |
commit | f4de82bcdafba51e4eed9cae6b2d3e5375ffd115 (patch) | |
tree | 08f98e1763e87f0639961c6da33224082345c7c3 /demos/quickstart/protected/pages/Configurations/Templates3.page | |
parent | 92dca3315f083f00dcff610ea207af52284d0616 (diff) |
Diffstat (limited to 'demos/quickstart/protected/pages/Configurations/Templates3.page')
-rw-r--r-- | demos/quickstart/protected/pages/Configurations/Templates3.page | 14 |
1 files changed, 7 insertions, 7 deletions
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>
|