upported to trunk/ last doc changes, everything should be fine now

8 files changed, 60 insertions, 32 deletions

diff --git a/demos/quickstart/protected/pages/Controls/Captcha.page b/demos/quickstart/protected/pages/Controls/Captcha.page
index 8a6e8a81..fd1accb2 100644
--- a/demos/quickstart/protected/pages/Controls/Captcha.page
+++ b/demos/quickstart/protected/pages/Controls/Captcha.page
@@ -1,36 +1,36 @@
 <com:TContent ID="body" >

 

-<h1>TCaptcha</h1>

+<h1 id="56002">TCaptcha</h1>

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

 

-<p>

+<p id="280002" class="block-content">

 <tt>TCaptcha</tt> displays a <a href="http://en.wikipedia.org/wiki/Captcha">CAPTCHA</a> that can be used to determine if the input is entered by a real user instead of some program. <tt>TCaptcha</tt> displays a token (a string consisting of alphanumeric characters) as an image and the user is expected to repeat the token in a text box. The token image is generated in a way such that it can be recognized by a human being, but not a program.

 </p>

 

-<p>

+<p id="280003" class="block-content">

 To use <tt>TCaptcha</tt>, you must enable the PHP GD2 extension with TrueType font support. Unlike other CAPTCHA scripts, <tt>TCaptcha</tt> does not need session or cookie.

 </p>

 

-<p>

+<p id="280004" class="block-content">

 The token generated by <tt>TCaptcha</tt> can be configured in several ways. To specify the length of characters in the token, set <tt>MinTokenLength</tt> and <tt>MaxTokenLength</tt>. To use case-insensitive token comparison and generate upper-case-only token, set <tt>CaseSensitive</tt> to false. More advanced users can try to set <tt>TokenAlphabet</tt> to specify which characters may appear in the generated tokens.

 </p>

 

-<p>

+<p id="280005" class="block-content">

 The validation of the token is related with two properties: <tt>TestLimit</tt> (defaults to 5 times) and <tt>TokenExpiry</tt> (defaults to 600 seconds). The former specifies how many times a token can be tested with on the server side, and the latter says when a generated token will expire. If the validation fails in any of the two scenarios, a new token will be automatically generated.

 </p>

 

-<p>

+<p id="280006" class="block-content">

 To specify the appearance of the generated token image, set <tt>TokenImageTheme</tt> to be an integer between 0 and 63. You may try the following example to see how this value affects the generated token image. The size of the generated token image is determined by <tt>TokenFontSize</tt>. In particular, the image width is proportional to the font size. You may also set <tt>Width</tt> to scale the generated image to your desired size, but the scaled image may not look good. By setting <tt>ChangingTokenBackground</tt> to true, the image background of the token will be variating even though the token is the same during postbacks.

 </p>

 

-<p>

+<p id="280007" class="block-content">

 Upon postback, user input can be validated by calling the method <tt>TCaptcha.validate()</tt>. More easily, you can use a <tt>TCaptchaValidator</tt> to automate the validation work for you. The <tt>TCaptchaValidator</tt> has the additional benefit of being able to validate the user input on the client-side. By default, a generated token will remain unchanged during postbacks. A new token can be generated by calling <tt>TCaptcha.regenerateToken()</tt> manually.

 </p>

 

-<p>

+<p id="280008" class="block-content">

 The following template shows a typical use of the <tt>TCaptcha</tt> control:

 </p>

-<com:TTextHighlighter Language="prado" CssClass="source">

+<com:TTextHighlighter Language="prado" CssClass="source block-content" id="code_280105">

 &lt;com:TCaptcha ID="Captcha" />

 &lt;com:TTextBox ID="Input" />

 &lt;com:TCaptchaValidator CaptchaControl="Captcha"

diff --git a/demos/quickstart/protected/pages/Controls/ClientScriptLoader.page b/demos/quickstart/protected/pages/Controls/ClientScriptLoader.page
index 590aa2d8..20fcb30b 100644
--- a/demos/quickstart/protected/pages/Controls/ClientScriptLoader.page
+++ b/demos/quickstart/protected/pages/Controls/ClientScriptLoader.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >
 
-<h1>TClientScriptLoader</h1>
+<h1 id="62003">TClientScriptLoader</h1>
 
 <com:DocLink ClassPath="System.Web.UI.WebControls.TClientScriptLoader" />
 
@@ -44,7 +44,7 @@ When the files in the <tt>PackagePath</tt> are published as assets, a script loa
  to that asset directory.
  The script loader, combines multiple javascript files and serve up as gzip if possible.
 </p>
-<h2>Grouping Javascript Files</h2>
+<h2 id="62004">Grouping Javascript Files</h2>
 <p class="block-content">
 Allowable scripts and script dependencies can be grouped by using a "<tt>packages.php</tt>" file
 with the following format. This "<tt>packages.php</tt>" is optional, if absent the file names
@@ -81,7 +81,7 @@ on both '<tt>package1</tt>' and '<tt>package2</tt>' groupings. That is, '<tt>pac
 will combine, in order, '<tt>file1.js</tt>', '<tt>file2.js</tt>', '<tt>file3.js</tt>', and '<tt>file4.js</tt>'.
 </p>
 
-<h2>Loading Javascript Packages</h2>
+<h2 id="62005">Loading Javascript Packages</h2>
 
 <p class="block-content">To load a particular javascript file or package, set the <tt>PackageScripts</tt> 
 property with value '<tt>package1</tt>' to load the '<tt>package1</tt>' scripts. 
@@ -96,10 +96,10 @@ Dependencies of the packages are automatically resolved by the script loader php
 &lt;/script&gt;
 </com:TTextHighlighter>
 
-<p>Each <tt>&lt;com:TClientScriptLoader&gt;</tt> generates an HTML <tt>&lt;script&gt;</tt>
+<p id="310009" class="block-content">Each <tt>&lt;com:TClientScriptLoader&gt;</tt> generates an HTML <tt>&lt;script&gt;</tt>
 element to load the required javascript files.</p>
 
-<h2>Removing Javascript Comments</h2>
+<h2 id="62006">Removing Javascript Comments</h2>
 <p class="block-content">The <tt>DebugMode</tt> property when false
 removes comments and white spaces from the published javascript files. If
 the <tt>DebugMode</tt> property is not set, the debug mode is determined from the 
@@ -113,7 +113,7 @@ directory for the next requests. That is, in non-debug mode the scripts are cach
 in the assets directory until they are deleted.
 </div>
 
-<h2>Compressing Javascript with GZip</h2>
+<h2 id="62007">Compressing Javascript with GZip</h2>
 <p class="block-content">
 The <tt>EnableGzip</tt> property (default is true) enables the
 published javascripts to be served as zipped if the browser and php server allows it.
diff --git a/demos/quickstart/protected/pages/Controls/Conditional.page b/demos/quickstart/protected/pages/Controls/Conditional.page
index e8ea4a65..1fd35e6a 100644
--- a/demos/quickstart/protected/pages/Controls/Conditional.page
+++ b/demos/quickstart/protected/pages/Controls/Conditional.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >

 

-<h1>TConditional</h1>

+<h1 id="64008">TConditional</h1>

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

 

 <p class="block-content">

@@ -17,13 +17,13 @@ you set <tt>Condition</tt> in template only and the expression should not refer
 objects that are available on or after the <tt>onInit</tt> lifecycle.

 </p>

 

-<p>

+<p id="320010" class="block-content">

 <tt>TConditional</tt> is very light. It instantiates either <tt>TrueTemplate</tt>

 <tt>FalseTemplate</tt>, but never both. And the condition is evaluated only once.

 A typical usage of TConditional is shown as following:

 </p>

 

-<com:TTextHighlighter Language="prado" CssClass="source">

+<com:TTextHighlighter Language="prado" CssClass="source block-content" id="code_320112">

 &lt;com:TConditional Condition="$this->User->IsGuest">

 	&lt;prop:TrueTemplate>

 		<a href="path/to/login">Login</a>

diff --git a/demos/quickstart/protected/pages/Controls/Keyboard.page b/demos/quickstart/protected/pages/Controls/Keyboard.page
index 06c91049..8b280718 100644
--- a/demos/quickstart/protected/pages/Controls/Keyboard.page
+++ b/demos/quickstart/protected/pages/Controls/Keyboard.page
@@ -1,29 +1,29 @@
 <com:TContent ID="body" >

 

-<h1>TKeyboard</h1>

+<h1 id="92009">TKeyboard</h1>

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

 

-<p>

+<p id="460011" class="block-content">

 <tt>TKeyboard</tt> displays a virtual keyboard that users can click on to enter input in

 an associated text box. It helps to reduce the keyboard recording hacking.

 </p>

 

-<p>

+<p id="460012" class="block-content">

 To use TKeyboard, write a template like following:

 </p>

-<com:TTextHighlighter Language="prado" CssClass="source">

+<com:TTextHighlighter Language="prado" CssClass="source block-content" id="code_460120">

 &lt;com:TTextBox ID="PasswordInput" />

 &lt;com:TKeyboard ForControl="PasswordInput" />

 </com:TTextHighlighter>

 

-<p>

+<p id="460013" class="block-content">

 A TKeyboard control is associated with a <tt>TTextBox</tt> control by specifying

 <tt>ForControl</tt> to be the ID of that control. When the textbox is in focus,

 a virtual keyboard will pop up; and when the text box is losing focus, the keyboard

 will hide automatically. Set <tt>AutoHide</tt> to false to keep the keyboard showing all the time.

 </p>

 

-<p>

+<p id="460014" class="block-content">

 The appearance of the keyboard can also be changed by specifying a customized CSS file via

 <tt>CssUrl</tt>. By default, the CSS class name for the keyboard is 'Keyboard'. This may

 also be changed by specifying <tt>KeyboardCssClass</tt>

diff --git a/demos/quickstart/protected/pages/Controls/List.page b/demos/quickstart/protected/pages/Controls/List.page
index c7505181..241fdaf4 100644
--- a/demos/quickstart/protected/pages/Controls/List.page
+++ b/demos/quickstart/protected/pages/Controls/List.page
@@ -49,12 +49,14 @@ $listbox->dataBind();
 </ul>

 

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

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

 <p id="550331" class="block-content">

 <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 id="4803">TDropDownList</h2>

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

 <p id="550332" class="block-content">

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

 </p>

@@ -64,6 +66,7 @@ Since v3.1.1, <tt>TDropDownList</tt> starts to support prompt text (something li
 <com:RunBar PagePath="Controls.Samples.TDropDownList.Home" />

 

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

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

 <p id="550333" class="block-content">

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

@@ -76,12 +79,14 @@ Since v3.1.1, <tt>TDropDownList</tt> starts to support prompt text (something li
 <com:RunBar PagePath="Controls.Samples.TCheckBoxList.Home" />

 

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

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

 <p id="550334" class="block-content">

 <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 id="4806">TBulletedList</h2>

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

 <p id="550335" class="block-content">

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

@@ -96,4 +101,11 @@ Since v3.1.1, <tt>TDropDownList</tt> starts to support prompt text (something li
 

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

 

+<h2 id="128001">TRatingList</h2>

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

+

+<p class="block-content">

+This is an EXPERIMENTAL class that displays clickable images that represent a TRadioButtonList.

+</p>

+

 <div class="last-modified">$Id$</div></com:TContent>
\ No newline at end of file
diff --git a/demos/quickstart/protected/pages/Controls/Slider.page b/demos/quickstart/protected/pages/Controls/Slider.page
index d71c28a0..5a6fa0d5 100644
--- a/demos/quickstart/protected/pages/Controls/Slider.page
+++ b/demos/quickstart/protected/pages/Controls/Slider.page
@@ -9,7 +9,7 @@ which define the range of possible value, and a <em>handle</em> which can slide
 a value in the range. The track can be either Horizontal or Vertical, depending of the <tt>Direction</tt>
 property. By default, it's horizontal.
 </p>
-<p>
+<p id="570015" class="block-content">
 The range boundaries are defined by <tt> MinValue</tt> and <tt>MaxValue</tt> properties. 
 The default range is from 0 to 100. 
 The <tt>StepSize</tt> property can be used to define the <em>step</em> between 2 values inside the range.
@@ -17,13 +17,13 @@ Notice that this step will be recomputed if there is more than 200 values betwee
 You can also provide the allowed values by setting the <tt>Values</tt> array.
 </p>
 
-<p>
+<p id="570016" class="block-content">
 The handle sub-properties can be accessed by <tt>Handle</tt> property. You can also provide your own control
 for the handle, using <tt>HandleClass</tt> property. Note that this class must be a subclass of 
 <tt>TSliderHandle</tt>
 </p>
 
-<p>
+<p id="570017" class="block-content">
 The TSlider control can be easily customized using CssClasses. You can provide your own css file, using the 
 <tt>CssUrl</tt> property.
 The css class for TSlider can be set by the <tt>CssClass</tt> property. Defaults values are <b>'hslider'</b> for
@@ -33,15 +33,15 @@ draw a red block as a cursor. <b>'handle-image'</b> css class is also provided f
 as the handle.
 </p>
 
-<p>
+<p id="570018" class="block-content">
 If <tt>AutoPostBack</tt> property is true, postback is performed as soon as the value changed.
 </p>
 
-<p>
+<p id="570019" class="block-content">
 TSlider raises the <tt>onValueChanged</tt> event when the value of the slider has changed during postback.
 </p>
 
-<p>
+<p id="570020" class="block-content">
 You can also attach ClientSide javascript events handler to the slider :
 <ul>
 <li><tt>ClientSide.onSlide</tt> is called when the handle is slided on the track. You can get the current value in the <b>value</b>
diff --git a/demos/quickstart/protected/pages/Controls/Standard.page b/demos/quickstart/protected/pages/Controls/Standard.page
index 9fde5a29..6a9cc769 100644
--- a/demos/quickstart/protected/pages/Controls/Standard.page
+++ b/demos/quickstart/protected/pages/Controls/Standard.page
@@ -1,7 +1,7 @@
 <com:TContent ID="body" >

 

-<h1>Standard Controls</h1>

-<p>* the tutorial for this control is not completed yet.</p>

+<h1 id="52001">Standard Controls</h1>

+<p id="260001" class="block-content">* the tutorial for this control is not completed yet.</p>

 <ul id="u1" class="block-content">

   <li>

   <a href="?page=Controls.Button">TButton</a> represents a click button on a Web page. It is mainly used to trigger page postback.

diff --git a/demos/quickstart/protected/pages/Controls/Validation.page b/demos/quickstart/protected/pages/Controls/Validation.page
index 74db7b07..cabb9371 100644
--- a/demos/quickstart/protected/pages/Controls/Validation.page
+++ b/demos/quickstart/protected/pages/Controls/Validation.page
@@ -34,6 +34,8 @@ Validators share a common set of properties, which are defined in the base class
 <h1 id="116008">Prado Validation Controls</h1>

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

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

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

+

 <p id="560340" class="block-content">

 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>

@@ -41,6 +43,8 @@ TRequiredFieldValidator ensures that the user enters some data in the specified
 

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

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

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

+

 <p id="560341" class="block-content">

 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>

@@ -65,6 +69,8 @@ Note, TRegularExpressionValidator only checks for nonempty user input. Use a TRe
 <com:RunBar PagePath="Controls.Samples.TRegularExpressionValidator.Home" />

 

 <h2 id="TEmailAddressValidator">TEmailAddressValidator</h2>

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

+

 <p id="560344" class="block-content">

 TEmailAddressValidator verifies that the user input is a valid email address. The validator uses a regular expression to check if the input is in a valid email address format. If <tt>CheckMXRecord</tt> is true, the validator will also check whether the MX record indicated by the email address is valid, provided <tt>checkdnsrr()</tt> is available in the installed PHP.

 </p>

@@ -75,6 +81,8 @@ Note, if the input being validated is empty, TEmailAddressValidator will not do
 

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

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

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

+

 <p id="560346" class="block-content">

 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>

@@ -94,6 +102,8 @@ Note, if the input being validated is empty, TEmailAddressValidator will not do
 

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

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

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

+

 <p id="560349" class="block-content">

 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>

@@ -106,6 +116,8 @@ TDataTypeValidator verifies if the input data is of specific type indicated by <
 

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

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

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

+

 <p id="560351" class="block-content">

 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>

@@ -124,6 +136,8 @@ are compared as strictly less than the <tt>MaxValue</tt> and/or strictly greater
 

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

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

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

+

 <p id="560353" class="block-content">

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

 </p>

@@ -148,6 +162,8 @@ function ValidationFunctionName(sender, parameter)
 

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

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

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

+

 <p id="560356" class="block-content">

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

 </p>