From 1c32172efb18e8d08ea483e2460813670ebfe1a5 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Sat, 30 Sep 2006 18:40:40 +0000
Subject: merge from 3.0 branch till 1451.

---
 .../quickstart/protected/pages/Advanced/Error.page |  6 ++--
 .../protected/pages/Advanced/MasterContent.page    |  2 +-
 .../protected/pages/Configurations/Templates1.page |  2 +-
 .../protected/pages/Configurations/UrlMapping.page | 41 +++++++++++++++-------
 .../pages/Controls/Samples/TDataGrid/Sample3.page  |  4 +--
 .../protected/pages/Controls/Validation.page       |  4 +--
 .../pages/GettingStarted/CommandLine.page          | 10 +++---
 7 files changed, 43 insertions(+), 26 deletions(-)

(limited to 'demos/quickstart/protected/pages')

diff --git a/demos/quickstart/protected/pages/Advanced/Error.page b/demos/quickstart/protected/pages/Advanced/Error.page
index a0765c10..9d2cf9ec 100644
--- a/demos/quickstart/protected/pages/Advanced/Error.page
+++ b/demos/quickstart/protected/pages/Advanced/Error.page
@@ -70,8 +70,8 @@ The naming convention for the template files used for all other exceptions is as
 <p>
 Again, if the preferred language is not found, PRADO will try to use <tt>exception.html</tt>, instead.
 </p>
-<p>
-CAUTION: When saving a template file, please make sure the file is saved using UTF-8 encoding. On Windows, you may use <tt>Notepad.exe</tt> to accomplish such saving.
-</p>
+<div class="note">
+<b class="tip">CAUTION:</b> When saving a template file, please make sure the file is saved using UTF-8 encoding. On Windows, you may use <tt>Notepad.exe</tt> to accomplish such saving.
+</div>
 
 </com:TContent>
\ No newline at end of file
diff --git a/demos/quickstart/protected/pages/Advanced/MasterContent.page b/demos/quickstart/protected/pages/Advanced/MasterContent.page
index b7bcc9bb..b0836393 100644
--- a/demos/quickstart/protected/pages/Advanced/MasterContent.page
+++ b/demos/quickstart/protected/pages/Advanced/MasterContent.page
@@ -40,7 +40,7 @@ Then, the contents are inserted into the master control according to the followi
 <img src=<%~ mastercontent.gif %> alt="Master and Content" />
 <img src=<%~ pcrelation.gif %> alt="Parent-child relationship between master and content" />
 
-<h2>Master vs. External Template</h2>
+<h2 id="6301">Master vs. External Template</h2>
 <p>
 Master is very similar to external templates which are introduced since version 3.0.5. A special <a href="?page=Configurations.Templates1">include tag</a> is used to include an external template file into a base template.
 </p>
diff --git a/demos/quickstart/protected/pages/Configurations/Templates1.page b/demos/quickstart/protected/pages/Configurations/Templates1.page
index 7acd92d0..958e27cf 100644
--- a/demos/quickstart/protected/pages/Configurations/Templates1.page
+++ b/demos/quickstart/protected/pages/Configurations/Templates1.page
@@ -85,7 +85,7 @@ Comments INVISIBLE to end-users
 Note, template comments (by &lt;!-- ... --!&gt;) cannot appear in a property value.
 </p>
 
-<h2>Include Tags</h2>
+<h2 id="1601">Include Tags</h2>
 <p>
 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 <tt>.tpl</tt>.
 </p>
diff --git a/demos/quickstart/protected/pages/Configurations/UrlMapping.page b/demos/quickstart/protected/pages/Configurations/UrlMapping.page
index dde6854f..ff6f09c7 100644
--- a/demos/quickstart/protected/pages/Configurations/UrlMapping.page
+++ b/demos/quickstart/protected/pages/Configurations/UrlMapping.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >
 
-<h1>URL Mapping (Friendly URLs)</h1>
+<h1 id="2101">URL Mapping (Friendly URLs)</h1>
 
 <com:DocLink ClassPath="System.Web.TUrlMapping" />
 
@@ -17,16 +17,25 @@ globally in the <a href="?page=Configurations.AppConfig">application configurati
 file and before any services.
 </p>
 
+<div class="info"><b class="tip">Info:</b>
+The <tt>TUrlMapping</tt> must be configured before the
+<a href="?page=Fundamentals.Modules">Request module</a> resolves the request.
+This usually means delcaring the <tt>TUrlMapping</tt> module before any
+<tt>&lt;services&gt;</tt> tag in the  <a href="?page=Configurations.AppConfig">application configuration</a>.
+Specifying the mappings in the per directory <tt>config.xml</tt> is not supported.
+</div>
+
 <p>The mapping format is as follows.
 <com:TTextHighlighter Language="xml" CssClass="source">
 <module id="friendly-url" class="System.Web.TUrlMapping">
-  <url serviceParameter="ClassName" pattern="regexp" parameters.id="regexp" />
+  <url serviceParameter="ClassName" pattern="pattern" parameters.id="subpattern" />
 </module>
 </com:TTextHighlighter>
 </p>
 
 <p>The <tt>ServiceParameter</tt> and <tt>ServiceID</tt>
- (the default ID is 'page') set the service parameter and service ID respectively.
+ (the default ID is 'page') set the service parameter and service ID, respectively, of
+ the <a href="?page=Fundamentals.Modules">Request module</a>.
  The service parameter for the <tt>TPageService</tt> service is the
  Page class name, e.g., for an URL "index.php?page=Home", "page" is the service ID and the service
  parameter is "Home". Other services may use the service parameter and ID differently.
@@ -42,15 +51,15 @@ and a right brace '<tt>}</tt>'. The pattens for each parameter can be set
 using <tt>Parameters</tt>attribute collection.
 For example,
 <com:TTextHighlighter Language="xml" CssClass="source">
-<url ServiceParameter="Pages.ShowArticles" pattern="articles/{year}/{month}/{day}"
+<url ServiceParameter="ArticleView" pattern="articles/{year}/{month}/{day}"
      parameters.year="\d{4}" parameters.month="\d{2}" parameters.day="\d+" />
 </com:TTextHighlighter>
 </p>
-The example is equivalent, using regular expression only, to
+The example is equivalent to the following regular expression (it uses the "named group" feature in regular expressions available in PHP):
 <com:TTextHighlighter Language="xml" CssClass="source">
-<url ServiceParmaeter="Pages.ShowArticles">
+<url ServiceParmaeter="ArticleView">
 <![CDATA[
-	articles/(?P<year>\d{4})/(?P<month>\d{2})/(?P<day>\d+)
+	/articles\/(?P<year>\d{4})\/(?P<month>\d{2})\/(?P<day>\d+)/u
 ]]>
 </url>
 </com:TTextHighlighter>
@@ -59,19 +68,27 @@ In the above example, the pattern contains 3 parameters named "<tt>year</tt>",
 "<tt>month</tt>" and "<tt>day</tt>". The pattern for these parameters are,
 respectively, "<tt>\d{4}</tt>" (4 digits), "<tt>\d{2}</tt>" (2 digits)
 and "<tt>\d+</tt>" (1 or more digits).
+Essentially, the <tt>Parameters</tt> attribute name and values are used
+ as substrings in replacing the placeholders in the <tt>Pattern</tt> string
+to form a complete regular expression string.
 </p>
 
-<p>For example, an URL "<tt>http://example.com/index.php/articles/2006/07/21</tt>" will be matched
+<div class="note"><b class="tip">Note:</b> If you intended to use the <tt>RegularExpression</tt>
+property you need to escape the slash in regular expressions.
+</div>
+
+<p>Following from the above pattern example,
+an URL "<tt>http://example.com/index.php/articles/2006/07/21</tt>" will be matched
 and valid.  However, "<tt>http://example.com/index.php/articles/2006/07/hello</tt>" is not
  valid since the "<tt>day</tt>" parameter pattern is not satisfied.
  In the default <tt>TUrlMappingPattern</tt> class, the pattern is matched against the
 <b>path</b> property of the URL only. For example, only the
-"<tt>/index.php/articles/2006/07/21</tt>" portion of the URL is considered and the rest
-is ignored.
+"<tt>/index.php/articles/2006/07/21</tt>" portion of the URL is considered.
  </p>
 
-
-<p>The parameter values are available through the standard <tt>Request</tt>
+<p>
+The mapped request URL is equivalent to <tt>index.php?page=ArticleView&amp;year=2006&amp;month=07&amp;day=21</tt>.
+The request parameter values are available through the standard <tt>Request</tt>
 object. For example, <tt>$this->Request['year']</tt>.
 </p>
 
diff --git a/demos/quickstart/protected/pages/Controls/Samples/TDataGrid/Sample3.page b/demos/quickstart/protected/pages/Controls/Samples/TDataGrid/Sample3.page
index 5fb19c6f..28b6288e 100644
--- a/demos/quickstart/protected/pages/Controls/Samples/TDataGrid/Sample3.page
+++ b/demos/quickstart/protected/pages/Controls/Samples/TDataGrid/Sample3.page
@@ -53,9 +53,9 @@
 	<com:TDropDownListColumn 
 		ID="RatingColumn"
 		HeaderText="Rating"
-		DataField="rating"
+		DataTextField="rating"
 		>
-		<prop:DataFormatString><img src="images/star%s.gif" alt="" /></prop:DataFormatString>
+		<prop:DataTextFormatString><img src="images/star%s.gif" alt="" /></prop:DataTextFormatString>
 		<com:TListItem Value="1" />
 		<com:TListItem Value="2" />
 		<com:TListItem Value="3" />
diff --git a/demos/quickstart/protected/pages/Controls/Validation.page b/demos/quickstart/protected/pages/Controls/Validation.page
index 119749db..2405fb45 100644
--- a/demos/quickstart/protected/pages/Controls/Validation.page
+++ b/demos/quickstart/protected/pages/Controls/Validation.page
@@ -151,7 +151,7 @@ The summary can be displayed as a list, a bulleted list, or a single paragraph b
 </p>
 <com:RunBar PagePath="Controls.Samples.TValidationSummary.Home" />
 
-<h2>Client and Server Side Conditional Validation</h2>
+<h2 id="5301">Client and Server Side Conditional Validation</h2>
 <p>
 	All validators contains the following events.
 	<ul>
@@ -180,7 +180,7 @@ function onErrorHandler(sender, parameter)
 Where <tt>sender</tt> is the current client-side validator and <tt>parameter</tt>
 is the control that invoked the validator.
 </p>
-<h3>Conditional Validation Example</h3>
+<h3 id="5302">Conditional Validation Example</h3>
 <p>
 The following example show the use of client-side and server side validator events. The example
 demonstrates conditional validation.
diff --git a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
index c2050246..cf204a40 100644
--- a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
+++ b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
@@ -1,18 +1,18 @@
 <com:TContent ID="body" >
-<h1>Command Line Tool</h1>
+<h1 id="501">Command Line Tool</h1>
 <p>The optional <tt>prado-cli.php</tt> PHP script file in the <tt>framework</tt>
 directory provides command line tools to perform various tendious taks in Prado.
 The <tt>prado-cli.php</tt> can be used to create Prado project skeletons, create
 initial test fixtures, and access to an interactive PHP shell.
 </p>
-<h2>Requirements</h2>
+<h2 id="502">Requirements</h2>
 <p>
 To use the command line tool, you need to use your command prompt, command console
 or terminal. In addition, PHP must be able to execute PHP scripts from
 the command line.
 </p>
 
-<h2>Usage</h2>
+<h2 id="503">Usage</h2>
 <p>
 If you type <tt>php path/to/framework/prado-cli.php</tt>, you should see
 the following information. Alternatively, if you are not on Windows, 
@@ -38,7 +38,7 @@ actions:
 <p>The <b>&lt;parameter&gt;</b> are required parameters and <b>[optional]</b>
 are optional parameters. </p>
 
-<h2>Creating a new Prado project skeleton</h2>
+<h2 id="504">Creating a new Prado project skeleton</h2>
 
 <p>To create a Prado project skeleton, do the following:</p>
 <ol>
@@ -49,7 +49,7 @@ are optional parameters. </p>
 	the test fixtures for the <tt>helloworld</tt> project.</li>
 </ol>
 
-<h2>Interactive Shell</h2>
+<h2 id="505">Interactive Shell</h2>
 <p>
 The interactive shell allows you to evaluate PHP statements from te command line.
 The <tt>prado-cli.php</tt> script can be used to start the shell and load an existing
-- 
cgit v1.2.3