From 2a962765f0b687988384294cdb4baf51e291680c Mon Sep 17 00:00:00 2001 From: xue <> Date: Tue, 6 Feb 2007 22:44:55 +0000 Subject: updated QS pages. --- .../protected/pages/Configurations/Templates1.page | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) (limited to 'demos/quickstart/protected/pages/Configurations') diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page index 34ffc975..9a71d6a5 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates1.page +++ b/demos/quickstart/protected/pages/Configurations/Templates1.page @@ -34,19 +34,24 @@ Note, property names and event names are all case-insensitive, while component t Also note, initial values for properties whose name ends with Template are specially processed. In particular, the initial values are parsed as TTemplate objects. The ItemTemplate property of the TRepeater control is such an example.

-To deal conveniently with properties taking take big trunk of initial data, the following property initialization tag is introduced, +To facilitate initializing properties with big trunk of data, the following property initialization tag is introduced. It is equivalent to ...PropertyName="PropertyValue"... in every aspect. Property initialization tags must be directly enclosed between the corresponding opening and closing component tag. +

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

+Since version 3.1.0, the property initialization tag can also be used to initialize a set of subproperties who share the same parent property. For example, the following is equivalent to HeaderStyle.BackColor="black" and HeaderStyle.ForeColor="red".

+ +<prop:HeaderStyle BackColor="black" ForeColor="red" /> +

Component IDs

When specified in templates, component ID 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 Home page's template, the following component tag - + <com:TTextBox ID="TextBox" Text="First Name" /> makes it possible to get the textbox object in code using $page->TextBox. @@ -55,7 +60,7 @@ makes it possible to get the textbox object in code using $page->TextBox

Template Control Tags

A template control tag is used to configure the initial property values of the control owning the template. Its format is as follows, - + <%@ PropertyName="PropertyValue" ... %> Like in component tags, PropertyName is case-insensitive and can be a property or subproperty name. @@ -72,7 +77,7 @@ Template control tag is optional in a template. Each template can contain at mos

Comment tags are used to put in a template developer comments that will not display to end-users. Contents enclosed within a comment tag will be treated as raw text strings and PRADO will not attempt to parse them. Comment tags cannot be used within property values. The format of comment tags is as follows,

- + <!-- Comments INVISIBLE to end-users ---> @@ -84,7 +89,7 @@ The new comment tag <!-- ... ---> has been introduced since PRADO

Since version 3.0.5, PRADO starts to support external template inclusion. This is accomplished via include tags, where external template files are specified in namespace format and their file name must be terminated as .tpl.

- + <%include path.to.templateFile %> -- cgit v1.2.3