diff options
| -rw-r--r-- | .gitattributes | 1 | ||||
| -rw-r--r-- | demos/quickstart/protected/pages/chap2/Configurations.page | 82 |
2 files changed, 83 insertions, 0 deletions
diff --git a/.gitattributes b/.gitattributes index 273f16ae..ca235386 100644 --- a/.gitattributes +++ b/.gitattributes @@ -25,6 +25,7 @@ demos/quickstart/protected/pages/chap1/AboutPrado.page -text demos/quickstart/protected/pages/chap1/Installation.page -text demos/quickstart/protected/pages/chap1/Introduction.page -text demos/quickstart/protected/pages/chap1/config.xml -text +demos/quickstart/protected/pages/chap2/Configurations.page -text demos/quickstart/protected/pages/chap2/Templates1.page -text demos/quickstart/protected/pages/chap2/Templates2.page -text demos/quickstart/protected/pages/chap2/Templates3.page -text diff --git a/demos/quickstart/protected/pages/chap2/Configurations.page b/demos/quickstart/protected/pages/chap2/Configurations.page new file mode 100644 index 00000000..75a3d0aa --- /dev/null +++ b/demos/quickstart/protected/pages/chap2/Configurations.page @@ -0,0 +1,82 @@ +<com:TContent ID="body" >
+<h1>Configurations</h1>
+<p>
+PRADO uses configurations to glue together components into pages and applications. There are <a href="#ac">application configurations</a>, <a href="#pfc">page folder configurations</a>, and <a href="?page=chap2.Templates1">templates</a>. Application and page folder configurations are optional if default values are used. Templates are mainly used by pages and template controls. They are optional, too.
+</p>
+<p>
+In this section, we focus on the application and page folder configurations. Templates are detailed in the next few sections.
+</p>
+
+<a name="ac" />
+<h2>Application Configurations</h2>
+<p>
+Application configurations are used to specify the global behavior of an application. This consists of specifying the paths, modules, services and parameters that will be used in an application.
+</p>
+<p>
+Application configurations are stored in an XML file which is passed as a parameter to the <code>TApplication</code> instance. The format of application configurations is shown in the following,
+<pre class="source">
+<application PropertyName="PropertyValue" ...>
+ <paths>
+ <alias id="AliasID" path="AliasPath" />
+ <using namespace="Namespace" />
+ </paths>
+ <modules>
+ <module id="ModuleID" class="ModuleClass" PropertyName="PropertyValue" ... />
+ </modules>
+ <services>
+ <service id="ServiceID" class="ServiceClass" PropertyName="PropertyValue" ... />
+ </services>
+ <parameters>
+ <parameter id="ParameterID" class="ParameterClass" PropertyName="PropertyValue" ... />
+ </parameters>
+</application>
+</pre>
+<ul>
+<li>The outermost element <code><application></code> corresponds to the <code>TApplication</code> instance. The <code>PropertyName="PropertyValue"</code> pairs specify the initial values for the properties of <code>TApplication</code>.</li>
+<li>The <code><paths></code> element contains the definition of path aliases and the PHP inclusion paths for the application. Each path alias is specified via an <code><alias></code> whose <code>path</code> attribute takes an absolute path or a path relative to the directory containing the application configuration file. The <code><using></code> 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: <code>System</code> and <code>Application</code>. The former refers to the PRADO framework root directory, and the latter refers to the directory containing the application configuration file.</li>
+<li>The <code><modules></code> element contains the configurations for a list of modules. Each module is specified by a <code><module></code> element. Each module is uniquely identified by the <code>id</code> attribute and is of type <code>class</code>. The <code>PropertyName="PropertyValue"</code> pairs specify the initial values for the properties of the module.</li>
+<li>The <code><services></code> element is similar to the <code><modules></code> element. It mainly specifies the services provided by the application.</li>
+<li>The <code><parameters></code> element contains a list of application-level parameters that are accessible from anywhere in the application. You may specify component-typed parameters like specifying modules, or you may specify string-typed parameters which take a simpler format as follows,
+<pre class="source">
+<parameter id="ParameterID">ParameterValue</parameter>
+</pre>
+</li>
+</ul>
+By default without explicit configuration, a PRADO application when running will load a few core modules, such as <code>THttpRequest</code>, <code>THttpResponse</code>, etc. It will also provide the <code>TPageService</code> 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.
+</p>
+
+<a name="pfc" />
+<h2>Page Folder Configurations</h2>
+<p>
+Page folder configurations are mainly used by <code>TPageService</code> to modify or append the application configuration. As the name indicates, a page folder configuration is associated with a directory storing some page files. It is stored as an XML file named <code>config.xml</code>.
+</p>
+<p>
+When a user requests a page stored under <code><BasePath>/dir1/dir2</code>, the <code>TPageService</code> will try to parse and load <code>config.xml</code> files under <code><BasePath>/dir1</code> and <code><BasePath>/dir1/dir2</code>. Paths, modules, and parameters specified in these configuration files will be appended or merged into the existing application configuration.
+</p>
+<p>
+The format of a page folder configuration file is as follows,
+<pre class="source">
+<configuration>
+ <paths>
+ <alias id="AliasID" path="AliasPath" />
+ <using namespace="Namespace" />
+ </paths>
+ <modules>
+ <module id="ModuleID" class="ModuleClass" PropertyName="PropertyValue" ... />
+ </modules>
+ <authorization>
+ <allow pages="PageID1,PageID2" users="User1,User2" roles="Role1,Role2" verb="post" />
+ <deny pages="PageID1,PageID2" users="User1,User2" roles="Role1,Role2" verb="post" />
+ </authorization>
+ <pages PropertyName="PropertyValue" ...>
+ <page id="PageID" PropertyName="PropertyValue" ... />
+ </pages>
+ <parameters>
+ <parameter id="ParameterID" class="ParameterClass" PropertyName="PropertyValue" ... />
+ </parameters>
+</configuration>
+</pre>
+The <code><paths></code>, <code><modules></code> and <code><parameters></code> are similar to those in an application configuration. The <code><authorization></code> specifies the authorization rules that apply to the current page directory and all its subdirectories. It will be explained in more detail in future sections. The <code><pages></code> element specifies the initial values for the properties of pages. Each <code><page></code> element specifies the initial property values for a particular page identified by the <code>id</code attribute. Initial property values given in the <code><pages></code> element apply to all pages in the current directory and all its subdirectories.
+</p>
+
+</com:TContent>
\ No newline at end of file |