From a5467e842316daf6a8a4345740f05a9731167ce1 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Sat, 23 Sep 2006 01:51:57 +0000
Subject: merge from 3.0 branch till 1435.
---
.../protected/pages/Configurations/UrlMapping.page | 75 +++++++++++++++
.../pages/GettingStarted/CommandLine.page | 107 +++++++++++++++++++++
.../protected/pages/GettingStarted/HelloWorld.page | 8 ++
3 files changed, 190 insertions(+)
create mode 100644 demos/quickstart/protected/pages/Configurations/UrlMapping.page
create mode 100644 demos/quickstart/protected/pages/GettingStarted/CommandLine.page
(limited to 'demos/quickstart/protected/pages')
diff --git a/demos/quickstart/protected/pages/Configurations/UrlMapping.page b/demos/quickstart/protected/pages/Configurations/UrlMapping.page
new file mode 100644
index 00000000..22cb866a
--- /dev/null
+++ b/demos/quickstart/protected/pages/Configurations/UrlMapping.page
@@ -0,0 +1,75 @@
+ Using the TUrlMapping module different URLs can be
+mapped into any existing Prado pages or services. This allows
+the application to use nice looking and friendly URLs.
+
+The TUrlMapping module allows aributary URL path to be mapped to a
+particular service and page class. This module must be configured
+before a service is initialized, thus this module should be configured
+globally in the application configuration
+file and before any services.
+ The mapping format is as follows.
+ The PageClass set the name of class that the matched URL will
+be requested.URL Mapping (Friendly URLs)
+
+
+In the above example, the pattern contains 3 parameters named "year", +"month" and "day". The pattern for these parameters are, +respectively, "\d{4}" (4 digits), "\d{2}" (2 digits) +and "\d+" (1 or more digits). +
+ +For example, an URL "http://example.com/index.php/articles/2006/07/21" will be matched +and valid. However, "http://example.com/index.php/articles/2006/07/hello" is not + valid since the "day" parameter pattern is not satisfied. + In the default TUrlMappingPattern class, the pattern is matched against the +path property of the URL only. For example, only the +"/index.php/articles/2006/07/21" portion of the URL is considered and the rest +is ignored. +
+ + +The parameter values are available through the standard Request +object. For example, $this->Request['year']. +
+ +The URL mapping are evaluated in order they are place and only the first mapping that matches + the URL will be used. Cascaded mapping can be achieved by placing the URL mappings + in particular order. For example, placing the most specific mappings first. +
+ + \ No newline at end of file diff --git a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page new file mode 100644 index 00000000..c2050246 --- /dev/null +++ b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page @@ -0,0 +1,107 @@ +The optional prado-cli.php PHP script file in the framework +directory provides command line tools to perform various tendious taks in Prado. +The prado-cli.php can be used to create Prado project skeletons, create +initial test fixtures, and access to an interactive PHP shell. +
++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. +
+ ++If you type php path/to/framework/prado-cli.php, you should see +the following information. Alternatively, if you are not on Windows, +you may try to change the prado-cli.php into an executable +and execute it as a script
+The <parameter> are required parameters and [optional] +are optional parameters.
+ +To create a Prado project skeleton, do the following:
++The interactive shell allows you to evaluate PHP statements from te command line. +The prado-cli.php script can be used to start the shell and load an existing +Prado project. For example, let us load the blog demo project. Assume that your +command line is in the prado distribution directory and you type. +
+
+
The three files that we need are explained as follows.
-- cgit v1.2.3