From 2f29591dc5a20086ad2c0e4e3689f7c0b9ab7b02 Mon Sep 17 00:00:00 2001
From: xue <>
Date: Tue, 21 Feb 2006 19:32:36 +0000
Subject: Added DTD and XSD for app and page configurations.

---
 demos/quickstart/protected/pages/Configurations/AppConfig.page  | 3 +++
 demos/quickstart/protected/pages/Configurations/PageConfig.page | 5 +++++
 2 files changed, 8 insertions(+)

(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 8d998f85..f72ab876 100644
--- a/demos/quickstart/protected/pages/Configurations/AppConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/AppConfig.page
@@ -37,6 +37,9 @@ Note, if the <tt>value</tt> attribute is not specified, the whole parameter XML
 </li>
 </ul>
 <p>
+Complete specification of application configurations can be found in the <a href="<%~../../../../../framework/Specs/ApplicationConfiguration.dtd%>">DTD</a> and <a href="<%~../../../../../framework/Specs/ApplicationConfiguration.xsd%>">XSD</a> files.
+</p>
+<p>
 By default without explicit configuration, a PRADO application when running will load a few core modules, such as <tt>THttpRequest</tt>, <tt>THttpResponse</tt>, etc. It will also provide the <tt>TPageService</tt> 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>
 
diff --git a/demos/quickstart/protected/pages/Configurations/PageConfig.page b/demos/quickstart/protected/pages/Configurations/PageConfig.page
index bd8a7186..6f489987 100644
--- a/demos/quickstart/protected/pages/Configurations/PageConfig.page
+++ b/demos/quickstart/protected/pages/Configurations/PageConfig.page
@@ -9,6 +9,7 @@ When a user requests a page stored under <tt>&lt;BasePath&gt;/dir1/dir2</tt>, th
 </p>
 <p>
 The format of a page configuration file is as follows,
+</p>
 <com:TTextHighlighter Language="xml" CssClass="source">
 <configuration>
   <paths>
@@ -30,7 +31,11 @@ The format of a page configuration file is as follows,
   </parameters>
 </configuration>
 </com:TTextHighlighter>
+<p>
 The <tt>&lt;paths&gt;</tt>, <tt>&lt;modules&gt;</tt> and <tt>&lt;parameters&gt;</tt> are similar to those in an application configuration. The <tt>&lt;authorization&gt;</tt> 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 <tt>&lt;pages&gt;</tt> element specifies the initial values for the properties of pages. Each <tt>&lt;page&gt;</tt> element specifies the initial property values for a particular page identified by the <tt>id</tt> attribute. Initial property values given in the <tt>&lt;pages&gt;</tt> element apply to all pages in the current directory and all its subdirectories.
 </p>
+<p>
+Complete specification of page configurations can be found in the <a href="<%~../../../../../framework/Specs/PageConfiguration.dtd%>">DTD</a> and <a href="<%~../../../../../framework/Specs/PageConfiguration.xsd%>">XSD</a> files.
+</p>
 
 </com:TContent>
\ No newline at end of file
-- 
cgit v1.2.3