From ccdb91a35602377fe389c6c5b0945478929e0eca Mon Sep 17 00:00:00 2001 From: wei <> Date: Wed, 28 Dec 2005 22:41:20 +0000 Subject: Adding TTextHighlighter for quickstart docs. --- .../protected/pages/Configurations/Templates1.page | 20 ++++++++-------- .../protected/pages/Configurations/Templates2.page | 28 +++++++++++----------- .../protected/pages/Configurations/Templates3.page | 24 +++++++++---------- .../protected/pages/Fundamentals/Components.page | 12 +++++----- 4 files changed, 42 insertions(+), 42 deletions(-) (limited to 'demos/quickstart/protected/pages') diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page index d9b71d35..ec230599 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates1.page +++ b/demos/quickstart/protected/pages/Configurations/Templates1.page @@ -13,35 +13,35 @@ A component tag specifies a component as part of the body content of the templat

The format of a component tag is as follows, -

+
 <com:ComponentType PropertyName="PropertyValue" ... EventName="EventHandler" ...>
 body content
 </com:ComponentType>
-
+ ComponentType can be either the class name or the dotted type name (e.g. System.Web.UI.TControl) of the component. PropertyName and EventName are both case-insensitive. PropertyName can be a property or subproperty name (e.g. Font.Name). Note, PropertyValue will be HTML-decoded when assigned to the corresponding property. Content enclosed between the opening and closing component tag are normally treated the body of the component.

It is required that component tags nest properly with each other and an opening component tag be paired with a closing tag, similar to that in XML. The following shows a component tag specifying the Text property and Click event of a button control, -

+
 <com:TButton Text="Register" Click="registerUser" />
-
+

To deal conveniently with properties taking take big trunk of initial data, the following property initialization tag is introduced, -

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

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.

@@ -55,7 +55,7 @@ Template control tag is optional in a template. Each template can contain at mos

Comment Tags

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, -

+
 <!--
 Comments VISIBLE to end-users
 -->
@@ -63,7 +63,7 @@ Comments VISIBLE to end-users
 <!
 Comments INVISIBLE to end-users
 !>
-
+

\ No newline at end of file diff --git a/demos/quickstart/protected/pages/Configurations/Templates2.page b/demos/quickstart/protected/pages/Configurations/Templates2.page index c4528a0b..66d9d0d1 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates2.page +++ b/demos/quickstart/protected/pages/Configurations/Templates2.page @@ -11,51 +11,51 @@ Dynamic content tags are introduced as shortcuts to some commonly used + <%= PhpExpression %> - + Inernally, an expression tag is represented by a TExpression control. Therefore, in the expression $this refers to the TExpression control. For example, the following expression tag will display the current page title at the place, -
+
 <%= $this->Page->Title %>
-
+

Statement Tags

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 echo or print in PHP) are displayed at the place where the statement tag resides in the template. Inernally, a statement tag is represented by a TStatements control. Therefore, in the statements $this refers to the TStatements control. The format of statement tags is as follows, -

+
 <%%
 PHP Statements
 %>
-
+

The following example displays the current time in Dutch at the place, -

+
 <%%
 setlocale(LC_ALL, 'nl_NL');
 echo strftime("%A %e %B %Y",time());
 %>
-
+

Databind Tags

Databind tags are similar to expression tags, except that the expressions are evaluated only when a dataBind() call is invoked on the controls representing the databind tags. Internally, a TLiteral control is used to represent a databind tag and $this in the expression would refer to the control. The format of databind tags is as follows, -

+
 <%# PhpExpression %>
-
+

Parameter Tags

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, -

+
 <%$ ParameterName %>
-
+ Note, application parameters are usually defined in application configurations or page directory configurations. The parameters are evaluated when the template is instantiated.

@@ -66,9 +66,9 @@ Asset tags are used to publish private files and display the corresponding the U

The format of asset tags is as follows, -

+
 <%~ LocalFileName %>
-
+ where LocalFileName refers to a file path that is relative to the directory containing the current template file. The file path can be a single file or a directory. If the latter, the content in the whole directory will be made accessible by end-users.

diff --git a/demos/quickstart/protected/pages/Configurations/Templates3.page b/demos/quickstart/protected/pages/Configurations/Templates3.page index 7ab55281..ae496553 100644 --- a/demos/quickstart/protected/pages/Configurations/Templates3.page +++ b/demos/quickstart/protected/pages/Configurations/Templates3.page @@ -5,11 +5,11 @@

Dynamic Property Tags

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, -

+
 <com:ComponentType PropertyName=DynamicPropertyTag ...>
 body content
 </com:ComponentType>
-
+ where you may enclose DynamicPropertyTag within single or double quotes for better readability.

@@ -20,13 +20,13 @@ We now introduce the available types of dynamic property tags that may be used i

Expression Tags

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, -

+
 <%= PhpExpression %>
-
+ In the expression, $this refers to the component specified by the component tag. The following example specifies a TLabel control whose Text property is initialized as the current page title when the TLabel control is being constructed, -
+
 <com:TLabel Text=<%= $this->Page->Title %> />
-
+

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. @@ -39,18 +39,18 @@ Databind tags are similar to expression tags, except that the expressions are ev

The format of databind tags is as follows, -

+
 <%# PhpExpression %>
-
+

Parameter Tags

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

+
 <%$ ParameterName %>
-
+ Note, application parameters are usually defined in application configurations or page directory configurations. The parameters are evaluated when the template is instantiated.

@@ -61,9 +61,9 @@ Asset tags are used to publish private files and assign the corresponding the UR

The format of asset tags is as follows, -

+
 <%~ LocalFileName %>
-
+ where LocalFileName refers to a file path that is relative to the directory containing the current template file. The file path can be a single file or a directory. If the latter, the content in the whole directory will be made accessible by end-users.

diff --git a/demos/quickstart/protected/pages/Fundamentals/Components.page b/demos/quickstart/protected/pages/Fundamentals/Components.page index 20888fba..be71b18b 100644 --- a/demos/quickstart/protected/pages/Fundamentals/Components.page +++ b/demos/quickstart/protected/pages/Fundamentals/Components.page @@ -7,7 +7,7 @@ A component is an instance of TComponent or its child class. The base c

Component Properties

A component property can be viewed as a public variable describing a specific aspect of the component, such as the background color, the font size, etc. A property is defined by the existence of a getter and/or a setter method in the component class. For example, in TControl, we define its ID property using the following getter and setter methods, -

+
 class TControl extends TComponent {
     public function getID() {
         ...
@@ -16,7 +16,7 @@ class TControl extends TComponent {
         ...
     }
 }
-
+

To get or set the ID property, do as follows, just like working with a variable, @@ -58,20 +58,20 @@ Component events are special properties that take method names as their values.

A component event is defined by the existence of an on-method. For example, in TButton, we have -

+
 class TButton extends TWebControl {
     public function onClick($param) {
         ...
     }
 }
-
+ This defines an event named Click, and a handler can be attached to the event using one of the following ways, -
+
 $button->Click=$callback;
 $button->Click->add($callback);
 $button->Click[]=$callback;
 $button->attachEventHandler('Click',$callback);
-
+ where $callback refers to a valid PHP callback (e.g. a function name, a class method array($object,'method'), etc.)

-- cgit v1.2.3