35 files changed, 73 insertions, 73 deletions

diff --git a/demos/quickstart/protected/pages/Controls/Button.page b/demos/quickstart/protected/pages/Controls/Button.page
index e58571d3..5c827725 100644
--- a/demos/quickstart/protected/pages/Controls/Button.page
+++ b/demos/quickstart/protected/pages/Controls/Button.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TButton</h1>

+<h1 id="2001">TButton</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TButton" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/CheckBox.page b/demos/quickstart/protected/pages/Controls/CheckBox.page
index 77052997..7f2767c0 100644
--- a/demos/quickstart/protected/pages/Controls/CheckBox.page
+++ b/demos/quickstart/protected/pages/Controls/CheckBox.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TCheckBox</h1>

+<h1 id="2101">TCheckBox</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TCheckBox" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/ColorPicker.page b/demos/quickstart/protected/pages/Controls/ColorPicker.page
index 6e05584a..8909ad98 100644
--- a/demos/quickstart/protected/pages/Controls/ColorPicker.page
+++ b/demos/quickstart/protected/pages/Controls/ColorPicker.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TColorPicker</h1>

+<h1 id="2201">TColorPicker</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TColorPicker" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Data.page b/demos/quickstart/protected/pages/Controls/Data.page
index 36839582..6a93ec6f 100644
--- a/demos/quickstart/protected/pages/Controls/Data.page
+++ b/demos/quickstart/protected/pages/Controls/Data.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Data Controls</h1>

+<h1 id="5001">Data Controls</h1>

 

 <ul>

   <li>

diff --git a/demos/quickstart/protected/pages/Controls/DataGrid.page b/demos/quickstart/protected/pages/Controls/DataGrid.page
index de6a94e9..ed1ad32b 100644
--- a/demos/quickstart/protected/pages/Controls/DataGrid.page
+++ b/demos/quickstart/protected/pages/Controls/DataGrid.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TDataGrid</h1>

+<h1 id="5201">TDataGrid</h1>

 

 <p>

 TDatagrid is an important control in building complex Web applications. It displays data in a tabular format with rows (also called items) and columns. A row is composed by cells, while columns govern how cells should be displayed according to their association with the columns. Data specified via <tt>DataSource</tt> or <tt>DataSourceID</tt> are bound to the rows and feed contents to cells.

@@ -12,7 +12,7 @@ TDataGrid is highly interactive. Users can sort the data along specified columns
 Rows of TDataGrid can be accessed via its <tt>Items</tt> property. A row (item) can be in one of several modes: browsing, editting and selecting, which affects how cells in the row are displayed. To change an item's mode, modify <tt>EditItemIndex</tt> or <tt>SelectedItemIndex</tt>. Note, if an item is in edit mode, then selecting this item will have no effect.

 </p>

 

-<h2>Columns</h2>

+<h2 id="5202">Columns</h2>

 <p>

 Columns of a data grid determine how the associated cells are displayed. For example, cells associated with a <tt>TBoundColumn</tt> are displayed differently according to their modes. A cell is displayed as a static text if the cell is in browsing mode, a text box if it is in editting mode, and so on.

 </p>

@@ -28,7 +28,7 @@ PRADO provides five types of columns:
   <li><tt>TTemplateColumn</tt> displays the cells according to different templates defined for it.</li>

 </ul>

 

-<h2>Item Styles</h2>

+<h2 id="5203">Item Styles</h2>

 <p>

 TDataGrid defines different styles applied to its items. For example, <tt>AlternatingItemStyle</tt> is applied to alternating items (item 2, 4, 6, etc.) Through these properties, one can set CSS style fields or CSS classes for the items.

 </p>

@@ -36,7 +36,7 @@ TDataGrid defines different styles applied to its items. For example, <tt>Altern
 Item styles are applied in a hierarchical way. Styles in higher hierarchy will inherit from styles in lower hierarchy. Starting from the lowest hierarchy, the item styles include item's own style, <tt>ItemStyle</tt>, <tt>AlternatingItemStyle</tt>, <tt>SelectedItemStyle</tt>, and <tt>EditItemStyle</tt>. Therefore, if background color is set as red in <tt>ItemStyle</tt>, <tt>EditItemStyle</tt> will also have red background color, unless it is explicitly set to a different value.

 </p>

 

-<h2>Events</h2>

+<h2 id="5204">Events</h2>

 <p>

 TDataGrid provides several events to facilitate manipulation of its items,

 </p>

@@ -57,9 +57,9 @@ TDataGrid provides several events to facilitate manipulation of its items,
   </li>

 </ul>

 

-<h2>Using TDataGrid</h2>

+<h2 id="5205">Using TDataGrid</h2>

 

-<h3>Automatically Generated Columns</h3>

+<h3 id="5210">Automatically Generated Columns</h3>

 <p>

 TDataGrid by default will create a list of columns based on the structure of the bound data. TDataGrid will read the first row of the data, extract the field names of the row, and construct a column for each field. Each column is of type <tt>TBoundColumn</tt>.

 </p>

@@ -77,7 +77,7 @@ public function onLoad($param) {
 </com:TTextHighlighter>

 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample1" />

 

-<h3>Manually Specified Columns</h3>

+<h3 id="5211">Manually Specified Columns</h3>

 <p>

 Using automatically generated columns gives a quick way of browsing tabular data. In real applications, however, automatically generated columns are often not sufficient because developers have no way customizing their appearance. Manually specified columns are thus more desirable.

 </p>

@@ -109,7 +109,7 @@ The following example uses manually specified columns to show a list of book inf
 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample2" />

 

 

-<h2>Interacting with TDataGrid</h2>

+<h2 id="5206">Interacting with TDataGrid</h2>

 <p>

 Besides the rich data presentation functionalities as demonstrated in previous section, TDataGrid is also highly user interactive. An import usage of TDataGrid is editting or deleting rows of data. The <tt>TBoundColumn</tt> can adjust the associated cell presentation according to the mode of datagrid items. When an item is in browsing mode, the cell is displayed with a static text; when the item is in editting mode, a textbox is displayed to collect user inputs. TDataGrid provides <tt>TEditCommandColumn</tt> for switching item modes. In addition, <tt>TButtonColumn</tt> offers developers the flexibility of creating arbitrary buttons for various user interactions.

 </p>

@@ -118,7 +118,7 @@ The following example shows how to make the previous book information table an i
 </p>

 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample3" />

 

-<h2>Sorting</h2>

+<h2 id="5207">Sorting</h2>

 <p>

 TDataGrid supports sorting its items according to specific columns. To enable sorting, set <tt>AllowSorting</tt> to true. This will turn column headers into clickable buttons if their <tt>SortExpression</tt> property is not empty. When users click on the header buttons, an <tt>OnSortCommand</tt> event will be raised. Developers can write handlers to respond to the sort command and sort the data according to <tt>SortExpression</tt> which is specified in the corresponding column.

 </p>

@@ -127,7 +127,7 @@ The following example turns the datagrid in <a href="?page=Controls.Samples.TDat
 </p>

 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample4" />

 

-<h2>Paging</h2>

+<h2 id="5208">Paging</h2>

 <p>

 When dealing with large datasets, paging is helpful in reducing the page size and complexity. TDataGrid has an embedded pager that allows users to specify which page of data they want to see. The pager can be customized via <tt>PagerStyle</tt>. For example, <tt>PagerStyle.Visible</tt> determines whether the pager is visible or not; <tt>PagerStyle.Position</tt> indicates where the pager is displayed; and <tt>PagerStyle.Mode</tt> specifies what type of pager is displayed, a numeric one or a next-prev one.

 </p>

@@ -146,7 +146,7 @@ The following example enables the paging functionality of the datagrid shown in
 </p>

 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample5" />

 

-<h3>Custom Paging</h3>

+<h3 id="5212">Custom Paging</h3>

 <p>

 The paging functionality shown above requires loading all data into memory, even though only a portion of them is displayed in a page. For large datasets, this is inefficient and may not always be feasible. TDataGrid provides custom paging to solve this problem. Custom paging only requires the portion of the data to be displayed to end users.

 </p>

@@ -155,7 +155,7 @@ To enable custom paging, set both <tt>AllowPaging</tt> and <tt>AllowCustomPaging
 </p>

 <com:RunBar PagePath="Controls.Samples.TDataGrid.Sample6" />

 

-<h2>Extending TDataGrid</h2>

+<h2 id="5209">Extending TDataGrid</h2>

 <p>

 Besides traditional class inheritance, extensibility of TDataGrid is mainly through developing new datagrid column components. For example, one may want to display an image column. He may use <tt>TTemplateColumn</tt> to accomplish this task. A better solution is to develop an image column component so that the work can be reused easily in other projects.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/DataList.page b/demos/quickstart/protected/pages/Controls/DataList.page
index 9d904870..c1ff1147 100644
--- a/demos/quickstart/protected/pages/Controls/DataList.page
+++ b/demos/quickstart/protected/pages/Controls/DataList.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TDataList</h1>

+<h1 id="5101">TDataList</h1>

 <p>

 TDataList is used to display or modify a list of data items specified by its <tt>DataSource</tt> or <tt>DataSourceID</tt> property. Each data item is displayed by a data list item which is a child control of the data list. The <tt>Items</tt> property contains the list of all data list items.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/DatePicker.page b/demos/quickstart/protected/pages/Controls/DatePicker.page
index 17d28382..a37ff048 100644
--- a/demos/quickstart/protected/pages/Controls/DatePicker.page
+++ b/demos/quickstart/protected/pages/Controls/DatePicker.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TDatePicker</h1>

+<h1 id="2301">TDatePicker</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TDatePicker" />

 

 <p><tt>TDatePicker</tt> displays a text box for date input purpose. 

diff --git a/demos/quickstart/protected/pages/Controls/Expression.page b/demos/quickstart/protected/pages/Controls/Expression.page
index 80a45a3a..044808c6 100644
--- a/demos/quickstart/protected/pages/Controls/Expression.page
+++ b/demos/quickstart/protected/pages/Controls/Expression.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TExpression</h1>

+<h1 id="2401">TExpression</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TExpression" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/FileUpload.page b/demos/quickstart/protected/pages/Controls/FileUpload.page
index 8aa5a0fb..404a144e 100644
--- a/demos/quickstart/protected/pages/Controls/FileUpload.page
+++ b/demos/quickstart/protected/pages/Controls/FileUpload.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TFileUpload</h1>

+<h1 id="2501">TFileUpload</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TFileUpload" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Head.page b/demos/quickstart/protected/pages/Controls/Head.page
index 269ec404..227b5282 100644
--- a/demos/quickstart/protected/pages/Controls/Head.page
+++ b/demos/quickstart/protected/pages/Controls/Head.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>THead</h1>

+<h1 id="2601">THead</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.THead" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/HiddenField.page b/demos/quickstart/protected/pages/Controls/HiddenField.page
index c068d01b..aa2e7c87 100644
--- a/demos/quickstart/protected/pages/Controls/HiddenField.page
+++ b/demos/quickstart/protected/pages/Controls/HiddenField.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>THiddenField</h1>

+<h1 id="2701">THiddenField</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.THiddenField" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/HtmlArea.page b/demos/quickstart/protected/pages/Controls/HtmlArea.page
index 0af685d5..00a65573 100644
--- a/demos/quickstart/protected/pages/Controls/HtmlArea.page
+++ b/demos/quickstart/protected/pages/Controls/HtmlArea.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>THtmlArea</h1>

+<h1 id="2801">THtmlArea</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.THtmlArea" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/HyperLink.page b/demos/quickstart/protected/pages/Controls/HyperLink.page
index afccd041..9fa6bde3 100644
--- a/demos/quickstart/protected/pages/Controls/HyperLink.page
+++ b/demos/quickstart/protected/pages/Controls/HyperLink.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>THyperLink</h1>

+<h1 id="2901">THyperLink</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.THyperLink" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Image.page b/demos/quickstart/protected/pages/Controls/Image.page
index a926c204..1e8df3de 100644
--- a/demos/quickstart/protected/pages/Controls/Image.page
+++ b/demos/quickstart/protected/pages/Controls/Image.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TImage</h1>

+<h1 id="3201">TImage</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TImage" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/ImageButton.page b/demos/quickstart/protected/pages/Controls/ImageButton.page
index b4a8de93..a79ecb6a 100644
--- a/demos/quickstart/protected/pages/Controls/ImageButton.page
+++ b/demos/quickstart/protected/pages/Controls/ImageButton.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TImageButton</h1>

+<h1 id="3001">TImageButton</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TImageButton" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/ImageMap.page b/demos/quickstart/protected/pages/Controls/ImageMap.page
index 997faad6..002861a3 100644
--- a/demos/quickstart/protected/pages/Controls/ImageMap.page
+++ b/demos/quickstart/protected/pages/Controls/ImageMap.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TImageMap</h1>

+<h1 id="3101">TImageMap</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TImageMap" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/InlineFrame.page b/demos/quickstart/protected/pages/Controls/InlineFrame.page
index 56e3f382..efd5144d 100644
--- a/demos/quickstart/protected/pages/Controls/InlineFrame.page
+++ b/demos/quickstart/protected/pages/Controls/InlineFrame.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TInlineFrame</h1>

+<h1 id="3301">TInlineFrame</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TInlineFrame" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/JavascriptLogger.page b/demos/quickstart/protected/pages/Controls/JavascriptLogger.page
index cff2b7aa..ccb4a27b 100644
--- a/demos/quickstart/protected/pages/Controls/JavascriptLogger.page
+++ b/demos/quickstart/protected/pages/Controls/JavascriptLogger.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TJavascriptLogger</h1>

+<h1 id="3401">TJavascriptLogger</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TJavascriptLogger" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Label.page b/demos/quickstart/protected/pages/Controls/Label.page
index 69329c8a..b7d5b094 100644
--- a/demos/quickstart/protected/pages/Controls/Label.page
+++ b/demos/quickstart/protected/pages/Controls/Label.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TLabel</h1>

+<h1 id="3501">TLabel</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TLabel" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/LinkButton.page b/demos/quickstart/protected/pages/Controls/LinkButton.page
index eb22f9ce..e0255141 100644
--- a/demos/quickstart/protected/pages/Controls/LinkButton.page
+++ b/demos/quickstart/protected/pages/Controls/LinkButton.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TLinkButton</h1>

+<h1 id="3601">TLinkButton</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TLinkButton" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/List.page b/demos/quickstart/protected/pages/Controls/List.page
index cac07330..b5915693 100644
--- a/demos/quickstart/protected/pages/Controls/List.page
+++ b/demos/quickstart/protected/pages/Controls/List.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>List Controls</h1>

+<h1 id="4801">List Controls</h1>

 <p>

 List controls covered in this section all inherit directly or indirectly from <tt>TListControl</tt>. Therefore, they share the same set of commonly used properties, including,

 </p>

@@ -48,19 +48,19 @@ $listbox->dataBind();
 </li>

 </ul>

 

-<h2>TListBox</h2>

+<h2 id="4802">TListBox</h2>

 <p>

 <tt>TListBox</tt> displays a list box that allows single or multiple selection. Set the property <tt>SelectionMode</tt> as <tt>Single</tt> to make a single selection list box, and <tt>Multiple</tt> a multiple selection list box. The number of rows displayed in the box is specified via the <tt>Rows</tt> property value.

 </p>

 <com:RunBar PagePath="Controls.Samples.TListBox.Home" />

 

-<h2>TDropDownList</h2>

+<h2 id="4803">TDropDownList</h2>

 <p>

 <tt>TDropDownList</tt> displays a dropdown list box that allows users to select a single option from a few prespecified ones.

 </p>

 <com:RunBar PagePath="Controls.Samples.TDropDownList.Home" />

 

-<h2>TCheckBoxList</h2>

+<h2 id="4804">TCheckBoxList</h2>

 <p>

 <tt>TCheckBoxList</tt> displays a list of checkboxes on a Web page. The alignment of the text besides each checkbox can be specified <tt>TextAlign</tt>. The layout of the checkboxes can be controlled by the following properties:

 </p>

@@ -72,13 +72,13 @@ $listbox->dataBind();
 

 <com:RunBar PagePath="Controls.Samples.TCheckBoxList.Home" />

 

-<h2>TRadioButtonList</h2>

+<h2 id="4805">TRadioButtonList</h2>

 <p>

 <tt>TRadioButtonList</tt> is similar to <tt>TCheckBoxList</tt> in every aspect except that each <tt>TRadioButtonList</tt> displays a group of radiobuttons. Only one of the radiobuttions can be selected (<tt>TCheckBoxList</tt> allows multiple selections.)

 </p>

 <com:RunBar PagePath="Controls.Samples.TRadioButtonList.Home" />

 

-<h2>TBulletedList</h2>

+<h2 id="4806">TBulletedList</h2>

 <p>

 <tt>TBulletedList</tt> displays items in a bullet format on a Web page. The style of the bullets can be specified by <tt>BulletStyle</tt>. When the style is <tt>CustomImage</tt>, the bullets are displayed as images, which is specified by <tt>BulletImageUrl</tt>.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/Literal.page b/demos/quickstart/protected/pages/Controls/Literal.page
index 30a84880..d5d40a13 100644
--- a/demos/quickstart/protected/pages/Controls/Literal.page
+++ b/demos/quickstart/protected/pages/Controls/Literal.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TLiteral</h1>

+<h1 id="3701">TLiteral</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TLiteral" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/MultiView.page b/demos/quickstart/protected/pages/Controls/MultiView.page
index 7e566181..a22711b6 100644
--- a/demos/quickstart/protected/pages/Controls/MultiView.page
+++ b/demos/quickstart/protected/pages/Controls/MultiView.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TMultiView</h1>

+<h1 id="3801">TMultiView</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TMultiView" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/NewControl.page b/demos/quickstart/protected/pages/Controls/NewControl.page
index 51d0cc02..8f4b9be9 100644
--- a/demos/quickstart/protected/pages/Controls/NewControl.page
+++ b/demos/quickstart/protected/pages/Controls/NewControl.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Writing New Controls</h1>

+<h1 id="5401">Writing New Controls</h1>

 <p>

 Writing new controls is often desired by advanced programmers, because they want to reuse the code that they write for dealing with complex presentation and user interactions.

 </p>

@@ -8,7 +8,7 @@ Writing new controls is often desired by advanced programmers, because they want
 In general, there are two ways of writing new controls: composition of existing controls and extending existing controls. They all require that the new control inherit from <tt>TControl</tt> or its child classes.

 </p>

 

-<h2>Composition of Existing Controls</h2>

+<h2 id="5402">Composition of Existing Controls</h2>

 <p>

 Composition is the easiest way of creating new controls. It mainly involves instantiating existing controls, configuring them and making them the constituent components. The properties of the constituent components are exposed through <a href="?page=Fundamentals.Components">subproperties</a>.

 </p>

@@ -19,7 +19,7 @@ One can compose a new control in two ways. One is to extend <tt>TCompositeContro
 As an example, we show how to create a labeled textbox called <tt>LabeledTextBox</tt> using the above two approaches. A labeled textbox displays a label besides a textbox. We want reuse the PRADO provided <tt>TLabel</tt> and <tt>TTextBox</tt> to accomplish this task.

 </p>

 

-<h3>Composition by Writing Templates</h3>

+<h3 id="5404">Composition by Writing Templates</h3>

 <p>

 We need two files: a control class file named <tt>LabeledTextBox.php</tt> and a control template file named <tt>LabeledTextBox.tpl</tt>. Both must reside under the same directory.

 </p>

@@ -46,7 +46,7 @@ In the above, the method call to <tt>ensureChildControls()</tt> ensures that bot
 </p>

 <com:RunBar PagePath="Controls.Samples.LabeledTextBox1.Home" />

 

-<h3>Composition by Overriding <tt>createChildControls()</tt></h3>

+<h3 id="5405">Composition by Overriding <tt>createChildControls()</tt></h3>

 <p>

 For a composite control as simple as <tt>LabeledTextBox</tt>, it is better to create it by extending <tt>TCompositeControl</tt> and overriding the <tt>createChildControls()</tt> method, because it does not use templates and thus saves template parsing time.

 </p>

@@ -80,7 +80,7 @@ class LabeledTextBox extends TCompositeControl {
 </com:TTextHighlighter>

 <com:RunBar PagePath="Controls.Samples.LabeledTextBox2.Home" />

 

-<h3>Using <tt>LabeledTextBox</tt></h3>

+<h3 id="5406">Using <tt>LabeledTextBox</tt></h3>

 <p>

 To use <tt>LabeledTextBox</tt> control, first we need to include the corresponding class file. Then in a page template, we can write lines like the following,

 </p>

@@ -91,7 +91,7 @@ To use <tt>LabeledTextBox</tt> control, first we need to include the correspondi
 In the above, <tt>Label.Text</tt> is a subproperty of <tt>LabeledTextBox</tt>, which refers to the <tt>Text</tt> property of the <tt>Label</tt> property. For other details of using <tt>LabeledTextBox</tt>, see the above online examples.

 </p>

 

-<h2>Extending Existing Controls</h2>

+<h2 id="5403">Extending Existing Controls</h2>

 <p>

 Extending existing controls is the same as conventional class inheritance. It allows developers to customize existing control classes by overriding their properties, methods, events, or creating new ones.

 </p>

@@ -102,7 +102,7 @@ The difficulty of the task depends on how much an existing class needs to be cus
 In this section, we mainly introduce the base control classes <tt>TControl</tt> and <tt>TWebControl</tt>, showing how they can be customized. We also introduce how to write controls with specific functionalities, such as loading post data, raising post data and databinding with data source.

 </p>

 

-<h3>Extending <tt>TControl</tt></h3>

+<h3 id="5407">Extending <tt>TControl</tt></h3>

 <p>

 <tt>TControl</tt> is the base class of all control classes. Two methods are of the most importance for derived control classes:

 </p>

@@ -125,7 +125,7 @@ Other important properties and methods include:
   <li>Control lifecycles - Life page lifecycles, controls also have lifecycles. Each control undergoes the following lifecycles in order: constructor, <tt>onInit()</tt>, <tt>onLoad()</tt>, <tt>onPreRender()</tt>, <tt>render()</tt>, and <tt>onUnload</tt>. More details can be found in the <a href="?page=Fundamentals.Pages">page</a> section.</li>

 </ul>

 

-<h3>Extending <tt>TWebControl</tt></h3>

+<h3 id="5408">Extending <tt>TWebControl</tt></h3>

 <p>

 <tt>TWebControl</tt> is mainly used as a base class for controls representing HTML elements. It provides a set of properties that are common among HTML elements. It breaks the <tt>TControl::render()</tt> into the following methods that are more suitable for rendering an HTML element:

 </p>

@@ -139,7 +139,7 @@ Other important properties and methods include:
 When rendering the openning HTML tag, <tt>TWebControl</tt> calls <tt>getTagName()</tt> to obtain the tag name. Derived classes may override this method to render different tag names.

 </p>

 

-<h3>Creating Controls with Special Functionalities</h3>

+<h3 id="5409">Creating Controls with Special Functionalities</h3>

 <p>

 If a control wants to respond to client-side events and translate them into server side events (called postback events), such as <tt>TButton</tt>, it has to implement the <tt>IPostBackEventHandler</tt> interface.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/Panel.page b/demos/quickstart/protected/pages/Controls/Panel.page
index b402cd8f..d507da36 100644
--- a/demos/quickstart/protected/pages/Controls/Panel.page
+++ b/demos/quickstart/protected/pages/Controls/Panel.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TPanel</h1>

+<h1 id="3901">TPanel</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TPanel" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/PlaceHolder.page b/demos/quickstart/protected/pages/Controls/PlaceHolder.page
index 323b1d52..b55d1616 100644
--- a/demos/quickstart/protected/pages/Controls/PlaceHolder.page
+++ b/demos/quickstart/protected/pages/Controls/PlaceHolder.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TPlaceHolder</h1>

+<h1 id="4001">TPlaceHolder</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TPlaceHolder" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/RadioButton.page b/demos/quickstart/protected/pages/Controls/RadioButton.page
index 5e1d9d21..b40f37bd 100644
--- a/demos/quickstart/protected/pages/Controls/RadioButton.page
+++ b/demos/quickstart/protected/pages/Controls/RadioButton.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TRadioButton</h1>

+<h1 id="4101">TRadioButton</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TRadioButton" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Repeater.page b/demos/quickstart/protected/pages/Controls/Repeater.page
index c40517f3..795e27aa 100644
--- a/demos/quickstart/protected/pages/Controls/Repeater.page
+++ b/demos/quickstart/protected/pages/Controls/Repeater.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TRepeater</h1>

+<h1 id="5301">TRepeater</h1>

 <p>

 TRepeater displays its content defined in templates repeatedly based on the given data specified by the <tt>DataSource</tt> or <tt>DataSourceID</tt> property. The repeated contents can be retrieved from the <tt>Items</tt> property. Each item is created by instantiating a template and each is a child control of the repeater.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/SafeHtml.page b/demos/quickstart/protected/pages/Controls/SafeHtml.page
index 565c8251..995ceb50 100644
--- a/demos/quickstart/protected/pages/Controls/SafeHtml.page
+++ b/demos/quickstart/protected/pages/Controls/SafeHtml.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TSafeHtml</h1>

+<h1 id="4201">TSafeHtml</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TSafeHtml" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Statements.page b/demos/quickstart/protected/pages/Controls/Statements.page
index dd26ec1b..3f3bd1fc 100644
--- a/demos/quickstart/protected/pages/Controls/Statements.page
+++ b/demos/quickstart/protected/pages/Controls/Statements.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TStatements</h1>

+<h1 id="4301">TStatements</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TStatements" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Table.page b/demos/quickstart/protected/pages/Controls/Table.page
index 75fa3fc1..e0f5586e 100644
--- a/demos/quickstart/protected/pages/Controls/Table.page
+++ b/demos/quickstart/protected/pages/Controls/Table.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TTable</h1>

+<h1 id="4401">TTable</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TTable" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/TextBox.page b/demos/quickstart/protected/pages/Controls/TextBox.page
index 64cb826a..b4d1576f 100644
--- a/demos/quickstart/protected/pages/Controls/TextBox.page
+++ b/demos/quickstart/protected/pages/Controls/TextBox.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TTextBox</h1>

+<h1 id="4501">TTextBox</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TTextBox" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/TextHighlighter.page b/demos/quickstart/protected/pages/Controls/TextHighlighter.page
index 40806b02..285a6f3e 100644
--- a/demos/quickstart/protected/pages/Controls/TextHighlighter.page
+++ b/demos/quickstart/protected/pages/Controls/TextHighlighter.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TTextHighlighter</h1>

+<h1 id="4601">TTextHighlighter</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TTextHighlighter" />

 

 <p>

diff --git a/demos/quickstart/protected/pages/Controls/Validation.page b/demos/quickstart/protected/pages/Controls/Validation.page
index 6d83af3d..a28c8faf 100644
--- a/demos/quickstart/protected/pages/Controls/Validation.page
+++ b/demos/quickstart/protected/pages/Controls/Validation.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>Validation Controls</h1>

+<h1 id="4901">Validation Controls</h1>

 

 <p>

 Validation controls, called validators, perform validation on user-entered data values when they are post back to the server. The validation is triggered by a postback control, such as a <tt>TButton</tt>, a <tt>TLinkButton</tt> or a <tt>TTextBox</tt> (under <tt>AutoPostBack</tt> mode) whose <tt>CausesValidation</tt> property is true.

@@ -32,14 +32,14 @@ Validators share a common set of properties, which are defined in the base class
 </ul>

 

 <a name="TRequiredFieldValidator"></a>

-<h2>TRequiredFieldValidator</h2>

+<h2 id="4902">TRequiredFieldValidator</h2>

 <p>

 TRequiredFieldValidator ensures that the user enters some data in the specified input field. By default, TRequiredFieldValidator will check if the user input is empty or not. The validation fails if the input is empty. By setting <tt>InitialValue</tt>, the validator can check if the user input is different from <tt>InitialValue</tt>. If not, the validation fails.

 </p>

 <com:RunBar PagePath="Controls.Samples.TRequiredFieldValidator.Home" />

 

 <a name="TRegularExpressionValidator"></a>

-<h2>TRegularExpressionValidator</h2>

+<h2 id="4903">TRegularExpressionValidator</h2>

 <p>

 TRegularExpressionValidator verifies the user input against a regular pattern. The validation fails if the input does not match the pattern. The regular expression can be specified by the <tt>RegularExpression</tt> property. Some commonly used regular expressions include:

 </p>

@@ -73,7 +73,7 @@ Note, if the input being validated is empty, TEmailAddressValidator will not do
 <com:RunBar PagePath="Controls.Samples.TEmailAddressValidator.Home" />

 	

 <a name="TCompareValidator"></a>

-<h2>TCompareValidator</h2>

+<h2 id="4904">TCompareValidator</h2>

 <p>

 TCompareValidator compares the user input with a constant value specified by <tt>ValueToCompare</tt>, or another user input specified by <tt>ControlToCompare</tt>. The <tt>Operator</tt> property specifies how to compare the values, which includes <tt>Equal</tt>, <tt>NotEqual</tt>, <tt>GreaterThan</tt>, <tt>GreaterThanEqual</tt>, <tt>LessThan</tt> and <tt>LessThanEqual</tt>. Before comparison, the values being compared will be converted to the type specified by <tt>DataType</tt> listed as follows,

 </p>

@@ -92,7 +92,7 @@ Note, if the input being validated is empty, TEmailAddressValidator will not do
 <com:RunBar PagePath="Controls.Samples.TCompareValidator.Home" />

 

 <a name="TDataTypeValidator"></a>

-<h2>TDataTypeValidator</h2>

+<h2 id="4905">TDataTypeValidator</h2>

 <p>

 TDataTypeValidator verifies if the input data is of specific type indicated by <tt>DataType</tt>. The data types that can be checked against are the same as those in TCompareValidator.

 </p>

@@ -104,7 +104,7 @@ TDataTypeValidator verifies if the input data is of specific type indicated by <
 <com:RunBar PagePath="Controls.Samples.TDataTypeValidator.Home" />

 

 <a name="TRangeValidator"></a>

-<h2>TRangeValidator</h2>

+<h2 id="4906">TRangeValidator</h2>

 <p>

 TRangeValidator verifies whether an input value is within a specified range. TRangeValidator uses three key properties to perform its validation. The <tt>MinValue</tt> and <tt>MaxValue</tt> properties specify the minimum and maximum values of the valid range. The <tt>DataType</tt> property specifies the data type of the value being validated. The value will be first converted into the specified type and then compare with the valid range. The data types that can be checked against are the same as those in TCompareValidator.

 </p>

@@ -115,7 +115,7 @@ TRangeValidator verifies whether an input value is within a specified range. TRa
 <com:RunBar PagePath="Controls.Samples.TRangeValidator.Home" />

 

 <a name="TCustomValidator"></a>

-<h2>TCustomValidator</h2>

+<h2 id="4907">TCustomValidator</h2>

 <p>

 TCustomValidator performs user-defined validation (either server-side or client-side or both) on an input control.

 </p>

@@ -139,7 +139,7 @@ function ValidationFunctionName(sender, parameter)
 <com:RunBar PagePath="Controls.Samples.TCustomValidator.Home" />

 

 <a name="TValidationSummary"></a>

-<h2>TValidationSummary</h2>

+<h2 id="4908">TValidationSummary</h2>

 <p>

 TValidationSummary displays a summary of validation errors inline on a Web page, in a message box, or both.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/Wizard.page b/demos/quickstart/protected/pages/Controls/Wizard.page
index f903e183..ce8bc774 100644
--- a/demos/quickstart/protected/pages/Controls/Wizard.page
+++ b/demos/quickstart/protected/pages/Controls/Wizard.page
@@ -1,9 +1,9 @@
 <com:TContent ID="body" >

 

-<h1>TWizard</h1>

+<h1 id="4701">TWizard</h1>

 <com:DocLink ClassPath="System.Web.UI.WebControls.TWizard" />

 

-<h2>Overview</h2>

+<h2 id="4702">Overview</h2>

 <p>

 <tt>TWizard</tt> is analogous to the installation wizard commonly used to install software on Windows. It splits a large form and presents the user with a series of smaller forms, called wizard steps, to complete. The following figure shows how a wizard is composed of when presented to users, where <tt>step content</tt> is the main content of a wizard step for users to complete, <tt>header</tt> refers to header content common to all steps, <tt>navigation</tt> contains buttons that allow users to navigate step by step, and <tt>side bar</tt> contains a list of hyperlinks by which users can reach to any step with one click. The visibility of the side bar can be toggled by setting <tt>ShowSideBar</tt>.

 </p>

@@ -49,15 +49,15 @@ In the above, <tt>StepType</tt> refers to the type of a wizard step, which can a
 </ul>

 

 

-<h2>Using TWizard</h2>

+<h2 id="4703">Using TWizard</h2>

 

-<h3>A Single-Step Wizard Sample</h3>

+<h3 id="4704">A Single-Step Wizard Sample</h3>

 <p>

 In this sample, we use wizard to collect user's preference of color. In the first step, the user is presented with a dropdown list from which he can choose hist favorite color. In the second step, the complete step, his choice in the previous step is displayed. In real application, at this step the choice may be stored in database in the backend.

 </p>

 <com:RunBar PagePath="Controls.Samples.TWizard.Sample1" />

 

-<h3>Customizing Wizard Styles</h3>

+<h3 id="4705">Customizing Wizard Styles</h3>

 <p>

 <tt>TWizard</tt> defines a whole set of properties for customization of appearance of its various components as shown in the above figure. In particular, the following properties are provided for style customization:

 </p>

@@ -69,7 +69,7 @@ In this sample, we use wizard to collect user's preference of color. In the firs
 </ul>

 <com:RunBar PagePath="Controls.Samples.TWizard.Sample2" />

 

-<h3>Customizing Wizard Navigation</h3>

+<h3 id="4706">Customizing Wizard Navigation</h3>

 <p>

 Given a set of wizard steps, <tt>TWizard</tt> supports three different ways of navigation among them:

 </p>

@@ -80,7 +80,7 @@ Given a set of wizard steps, <tt>TWizard</tt> supports three different ways of n
 </ul>

 <com:RunBar PagePath="Controls.Samples.TWizard.Sample3" />

 

-<h3>Using Templates in Wizard</h3>

+<h3 id="4707">Using Templates in Wizard</h3>

 <p>

 <tt>TWizard</tt> supports more concrete control of its outlook through templating. In particular, it provides the following template properties that allow complete customization of the wizard's header, navigation and side bar.

 </p>

@@ -91,7 +91,7 @@ Given a set of wizard steps, <tt>TWizard</tt> supports three different ways of n
 </ul>

 <com:RunBar PagePath="Controls.Samples.TWizard.Sample4" />

 

-<h3>Using Templated Wizard Steps</h3>

+<h3 id="4708">Using Templated Wizard Steps</h3>

 <p>

 Wizard steps can also be templated. By using <tt>TTemplatedWizardStep</tt>, one can customize step content and navigation through its <tt>ContentTemplate</tt> and <tt>NavigationTemplate</tt> properties, respectively. This is useful for control developers to build specialized wizards, such as user registration, shopping carts, etc.

 </p>