From 6baade86cc27d460dc780c016a6560deae48d247 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Thu, 26 Jan 2006 14:56:13 +0000
Subject: Makes quickstart tutorial pages xhtml compatible.
---
demos/quickstart/protected/pages/Configurations/AppConfig.page | 2 ++
demos/quickstart/protected/pages/Controls/List.page | 4 ++--
demos/quickstart/protected/pages/Fundamentals/Applications.page | 2 +-
3 files changed, 5 insertions(+), 3 deletions(-)
(limited to 'demos/quickstart/protected/pages')
diff --git a/demos/quickstart/protected/pages/Configurations/AppConfig.page b/demos/quickstart/protected/pages/Configurations/AppConfig.page
index 127f74a4..d40510ef 100644
--- a/demos/quickstart/protected/pages/Configurations/AppConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/AppConfig.page
@@ -23,6 +23,7 @@ Configuration for an application is stored in an XML file named application.
+
- The outermost element <application> corresponds to the TApplication instance. The PropertyName="PropertyValue" pairs specify the initial values for the properties of TApplication.
- The <paths> element contains the definition of path aliases and the PHP inclusion paths for the application. Each path alias is specified via an <alias> whose path attribute takes an absolute path or a path relative to the directory containing the application configuration file. The <using> element specifies a particular path (in terms of namespace) to be appended to the PHP include paths when the application runs. PRADO defines two default aliases: System and Application. The former refers to the PRADO framework root directory, and the latter refers to the directory containing the application configuration file.
@@ -34,6 +35,7 @@ Configuration for an application is stored in an XML file named application.
+
By default without explicit configuration, a PRADO application when running will load a few core modules, such as THttpRequest, THttpResponse, etc. It will also provide the TPageService as a default service. Configuration and usage of these modules and services are covered in individual sections of this tutorial. Note, if your application takes default settings for these modules and service, you do not need to provide an application configuration. However, if these modules or services are not sufficient, or you want to change their behavior by configuring their property values, you will need an application configuration.
diff --git a/demos/quickstart/protected/pages/Controls/List.page b/demos/quickstart/protected/pages/Controls/List.page
index 5f22e412..86de4c41 100644
--- a/demos/quickstart/protected/pages/Controls/List.page
+++ b/demos/quickstart/protected/pages/Controls/List.page
@@ -26,13 +26,13 @@ List controls covered in this section all inherit directly or indirectly from TListControl inherits from TDataBoundControl, these list controls also share a common operation known as databinding. The Items can be populated from preexisting data specified by DataSource or DataSourceID. A function call to dataBind() will cause the data population. For list controls, data can be specified in three kinds of format:
- - integer-indexed array : each array element value will be used as the value and text for a list item. For example
+
- integer-indexed array, TList or traversable : each array element value will be used as the value and text for a list item. For example
$listbox->DataSource=array('item 1','item 2','item 3');
$listbox->dataBind();
- - associative array : array keys will be used as list item values, and array values will be used as list item texts. For example
+
- associative array, TMap or traversable : array keys will be used as list item values, and array values will be used as list item texts. For example
$listbox->DataSource=array(
'key 1'=>'item 1',
diff --git a/demos/quickstart/protected/pages/Fundamentals/Applications.page b/demos/quickstart/protected/pages/Fundamentals/Applications.page
index b67debaa..b33b4f10 100644
--- a/demos/quickstart/protected/pages/Fundamentals/Applications.page
+++ b/demos/quickstart/protected/pages/Fundamentals/Applications.page
@@ -36,12 +36,12 @@ A product PRADO application usually needs more files. It may include an applicat
Application Deployment
Deploying a PRADO application mainly involves copying directories. For example, to deploy the above minimal application to another server, follow the following steps,
+
- Copy the content under wwwroot to a Web-accessible directory on the new server.
- Modify the entry script file index.php so that it includes correctly the prado.php file.
- Remove all content under assets and runtime directories and make sure both directories are writable by the Web server process.
-
Application Lifecycles
--
cgit v1.2.3