4 files changed, 79 insertions, 8 deletions
diff --git a/buildscripts/phpbuilder/files.txt b/buildscripts/phpbuilder/files.txt
index 21779094..36ad5cc0 100644
--- a/buildscripts/phpbuilder/files.txt
+++ b/buildscripts/phpbuilder/files.txt
@@ -1,15 +1,21 @@
 TComponent.php
 Exceptions/TException.php
+
 Collections/TList.php
 Collections/TMap.php
 Collections/TAttributeCollection.php
+Collections/TPagedDataSource.php
+Collections/TDummyDataSource.php
+
 Data/TXmlDocument.php
 Web/THttpUtility.php
 Data/TCache.php
 Log/TLogger.php
+
 core.php
 prado.php
 TApplication.php
+
 Exceptions/TErrorHandler.php
 Web/THttpRequest.php
 Web/THttpResponse.php
@@ -48,6 +54,9 @@ Web/UI/WebControls/TFileUpload.php
 Web/UI/WebControls/THead.php
 Web/UI/WebControls/THiddenField.php
 Web/UI/WebControls/THyperLink.php
+Web/UI/WebControls/TTableCell.php
+Web/UI/WebControls/TTableHeaderCell.php
+Web/UI/WebControls/TTableRow.php
 Web/UI/WebControls/TTable.php
 
 Web/UI/WebControls/TDataSourceControl.php
@@ -78,8 +87,6 @@ Web/UI/WebControls/TRepeater.php
 
 Web/UI/WebControls/TBaseDataList.php
 Web/UI/WebControls/TDataList.php
-Collections/TPagedDataSource.php
-Collections/TDummyDataSource.php
 Web/UI/WebControls/TDataGrid.php
 Web/UI/WebControls/TDataGridColumn.php
 Web/UI/WebControls/TBoundColumn.php
diff --git a/demos/quickstart/protected/pages/Controls/DataList.page b/demos/quickstart/protected/pages/Controls/DataList.page
index 65919ee2..1927f558 100644
--- a/demos/quickstart/protected/pages/Controls/DataList.page
+++ b/demos/quickstart/protected/pages/Controls/DataList.page
@@ -2,8 +2,56 @@
 
 <h1>TDataList</h1>
 <p>
-TBC
+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>
+<p>
+TDataList displays its items in either a <tt>Table</tt> or <tt>Flow</tt> layout, which is specified by the <tt>RepeatLayout</tt> property. A table layout uses HTML table cells to organize the items while a flow layout uses line breaks to organize the items. When the layout is <tt>Table</tt>, the table's cellpadding and cellspacing can be adjusted by <tt>CellPadding</tt> and <tt>CellSpacing</tt> properties, respectively. And <tt>Caption</tt> and <tt>CaptionAlign</tt> can be used to add a table caption with the specified alignment. The number of columns used to display the data list items is specified via <tt>RepeatColumns</tt> property, while the <tt>RepeatDirection</tt> governs the order of the items being rendered.
+</p>
+<p>
+Each data list item is created according to one of the seven kinds of templates that developers may specified for a TDataList,
+</p>
+<ul>
+  <li><tt>HeaderTemplate</tt> - the template used for displaying content at the beginning of a data list;</li>
+  <li><tt>FooterTemplate</tt> - the template used for displaying content at the end of a data list;</li>
+  <li><tt>ItemTemplate</tt> - the template used for displaying every data list item. If <tt>AlternatingItemTemplate</tt> is also defined, <tt>ItemTemplate</tt> will be used for displaying item 1, 3, 5, etc.</li>
+  <li><tt>AlternatingItemTemplate</tt> - the template used for displaying every alternating data list item (i.e., item 2, 4, 6, etc.)</li>
+  <li><tt>SeparatorTemplate</tt> - the template used for displaying content between items.</li>
+  <li><tt>EditItemTemplate</tt> - the template used for displaying items in edit mode.</li>
+  <li><tt>SelectedItemTemplate</tt> - the template used for displaying items in selected mode.</li>
+</ul>
+<p>
+Each of the above templates is associated with a style property that is applied to the items using the template. For example, <tt>ItemTemplate</tt> is associated with a property named <tt>AlternatingItemStyle</tt>. Through this property, one can set CSS style fields or CSS classes for the data list items.
+</p>
+<p>
+Item styles are applied in a hierarchical way. Style 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>
+<p>
+A data list item can be in normal mode, edit mode or selected mode. Different templates will apply to items of different modes. 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>
+<p>
+TDataList provides several events to facilitate manipulation of its items,
+</p>
+<ul>
+  <li><tt>OnItemCreated</tt> - raised each time an item is newly created. When the event is raised, data and child controls are both available for the new item.</li>
+  <li><tt>OnItemDataBound</tt> - raised each time an item just completes databinding. When the event is raised, data and child controls are both available for the item, and the item has finished databindings of itself and all its child controls.</li>
+  <li><tt>OnItemCommand</tt> - raised when a child control of some item (such as a <tt>TButton</tt>) raises an <tt>OnCommand</tt> event.</li>
+  <li>command events - raised when a child control's <tt>OnCommand</tt> event has a specific command name,
+    <ul>
+      <li><tt>OnSelectedIndexChanged</tt> - if the command name is <tt>select</tt>.</li>
+      <li><tt>OnEditCommand</tt> - if the command name is <tt>edit</tt>.</li>
+      <li><tt>OnDeleteCommand</tt> - if the command name is <tt>delete</tt>.</li>
+      <li><tt>OnUpdateCommand</tt> - if the command name is <tt>update</tt>.</li>
+      <li><tt>OnCancelCommand</tt> - if the command name is <tt>cancel</tt>.</li>
+    </ul>
+  </li>
+</ul>
+<p>
+The following example shows how to use TDataList to display tabular data, with different layout and styles.
 </p>
 <com:RunBar PagePath="Controls.Samples.TDataList.Sample1" />
+<p>
+An important use of TDataList is for maintaining tabular data, including browsing, editting, deleting data items. This is enabled by the command events and various item templates of TDataList. The following example displays a computer product information. Users can add new products, modify or delete existing ones.
+</p>
+<com:RunBar PagePath="Controls.Samples.TDataList.Sample2" />
 
 </com:TContent>
 \ No newline at end of file
diff --git a/demos/quickstart/protected/pages/Controls/Repeater.page b/demos/quickstart/protected/pages/Controls/Repeater.page
index d8789dac..c40517f3 100644
--- a/demos/quickstart/protected/pages/Controls/Repeater.page
+++ b/demos/quickstart/protected/pages/Controls/Repeater.page
@@ -2,7 +2,7 @@
 
 <h1>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. TRepeater provides the <tt>OnItemCommand</tt> event that serves as a central place to process all <tt>OnCommand</tt> events raised by child controls of the repeater items. And an <tt>OnItemCreated</tt> event is raised each time when a new item is created based on a template.
+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>
 <p>
 Like normal control templates, the repeater templates can contain static text, controls and special tags, which after instantiation, become child contents of the corresponding item. TRepeater defiens five templates for different purposes,
@@ -31,6 +31,17 @@ class MyPage extends TPage {
 <p>
 Normally, you only need to do this when the page containing the repeater is initially requested. In postbacks, TRepeater is smart enough to remember the previous state, i.e., contents populated with datasource information.The following sample displays tabular data using TRepeater.
 </p>
+<p>
+TRepeater provides several events to facilitate manipulation of its items,
+</p>
+<ul>
+  <li><tt>OnItemCreated</tt> - raised each time an item is newly created. When the event is raised, data and child controls are both available for the new item.</li>
+  <li><tt>OnItemDataBound</tt> - raised each time an item just completes databinding. When the event is raised, data and child controls are both available for the item, and the item has finished databindings of itself and all its child controls.</li>
+  <li><tt>OnItemCommand</tt> - raised when a child control of some item (such as a <tt>TButton</tt>) raises an <tt>OnCommand</tt> event.</li>
+</ul>
+<p>
+The following example shows how to use TRepeater to display tabular data.
+</p>
 <com:RunBar PagePath="Controls.Samples.TRepeater.Sample1" />
 <p>
 TRepeater can be used in more complex situations. As an example, we show in the following how to use nested repeaters, i.e., repeater in repeater. This is commonly seen in presenting master-detail data. To use a repeater within another repeater, for an item for the outer repeater is created, we need to set the detail data source for the inner repeater. This can be achieved by responding to the <tt>OnItemDataBound</tt> event of the outer repeater. An <tt>OnItemDataBound</tt> event is raised each time an outer repeater item completes databinding. In the following example, we exploit another event of repeater called <tt>OnItemCreated</tt>, which is raised each time a repeater item (and its content) is newly created. We respond to this event by setting different background colors for repeater items to achieve alternating item background display. This saves us from writing an <tt>AlternatingItemTemplate</tt> for the repeaters.
diff --git a/framework/Web/UI/WebControls/TDataList.php b/framework/Web/UI/WebControls/TDataList.php
index 819febd6..e3748d22 100644
--- a/framework/Web/UI/WebControls/TDataList.php
+++ b/framework/Web/UI/WebControls/TDataList.php
@@ -34,8 +34,13 @@ Prado::using('System.Web.UI.WebControls.TRepeatInfo');
  * then the corresponding content will be displayed alternatively with that
  * in {@link setItemTemplate ItemTemplate}. The content in
  * {@link setSeparatorTemplate SeparatorTemplate}, if not empty, will be
- * displayed between items. All these templates are associated with styles that
- * may be applied to the corresponding generated items. For example,
+ * displayed between items. Besides the above templates, there are two additional
+ * templates, {@link setEditItemTemplate EditItemTemplate} and
+ * {@link setSelectedItemTemplate SelectedItemTemplate}, which are used to display
+ * items that are in edit and selected mode, respectively.
+ *
+ * All these templates are associated with styles that may be applied to
+ * the corresponding generated items. For example,
  * {@link getAlternatingItemStyle AlternatingItemStyle} will be applied to
  * every alternating item in the data list.
  *
@@ -81,10 +86,10 @@ Prado::using('System.Web.UI.WebControls.TRepeatInfo');
  * The event mainly informs the server side that the end-user has made a selection.
  *
  * TDataList raises an {@link onItemCommand OnItemCommand} whenever a button control
- * within some TDataList item raises a <b>Command</b> event. If the command name
+ * within some TDataList item raises a <b>OnCommand</b> event. If the command name
  * is one of the followings: 'edit', 'update', 'select', 'delete', 'cancel' (case-insensitive),
  * another event will also be raised. For example, if the command name is 'edit',
- * then the new event is {@link onEditCommand OnSelectCommand}.
+ * then the new event is {@link onEditCommand OnEditCommand}.
  *
  * @author Qiang Xue <qiang.xue@gmail.com>
  * @version $Revision: $  $Date: $