Added dist-created ids for quickstart demo

7 files changed, 18 insertions, 18 deletions

diff --git a/demos/quickstart/protected/pages/ActiveControls/Introduction.page b/demos/quickstart/protected/pages/ActiveControls/Introduction.page
index edc0b5bc..7edb96d2 100755
--- a/demos/quickstart/protected/pages/ActiveControls/Introduction.page
+++ b/demos/quickstart/protected/pages/ActiveControls/Introduction.page
@@ -9,7 +9,7 @@ A classic webpage can only transfer data back to the server using an http postba
 A common solution to this problem is the use of AJAX (Asynchronous JavaScript and XML) callbacks. After the first full page load, the web application can make subsequents requests using javascript. The callback requests are asynchronous, so the user can continue to interact with the page while the response is loading. The response contains a list of changes that will be applied to the page "on the fly", like replacing existing elements with new content or add some css style to an existing element.

 </p>

 

-<h2>Interacting with a page on callback</h2>

+<h2 id="218012">Interacting with a page on callback</h2>

 

 <p class="block-content">

 PRADO has builtin support for AJAX callbacks in the form of <i>Active Controls</i>. These controls can trigger a callback request and have their properties (value, css style, attributes, ..) updated during a callback.

@@ -28,7 +28,7 @@ public function onClick($sender, $param)
 }

 </com:TTextHighlighter>

 

-<h1>Active Controls (AJAX enabled Controls)</h1>

+<h1 id="218011">Active Controls (AJAX enabled Controls)</h1>

 <p class="block-content">

 Active controls extends standard PRADO controls adding the ability to automatically update themselves on callbacks without the need of ad-hoc javascript calls. Active controls are reliant on a collection of javascript classes that gets added to the page automatically when needed.

 </p>

diff --git a/demos/quickstart/protected/pages/Controls/HtmlArea4.page b/demos/quickstart/protected/pages/Controls/HtmlArea4.page
index 1fa33424..f7092230 100755
--- a/demos/quickstart/protected/pages/Controls/HtmlArea4.page
+++ b/demos/quickstart/protected/pages/Controls/HtmlArea4.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >
 
-<h1>THtmlArea4</h1>
+<h1 id="84009">THtmlArea4</h1>
 <com:DocLink ClassPath="System.Web.UI.WebControls.THtmlArea4" />
 
 <p class="block-content">
diff --git a/demos/quickstart/protected/pages/Controls/Markdown.page b/demos/quickstart/protected/pages/Controls/Markdown.page
index d7cc00c6..2fea9fc2 100644
--- a/demos/quickstart/protected/pages/Controls/Markdown.page
+++ b/demos/quickstart/protected/pages/Controls/Markdown.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >
 
-<h1>TMarkdown</h1>
+<h1 id="106010">TMarkdown</h1>
 <com:DocLink ClassPath="System.Web.UI.WebControls.TMarkdown" />
 
 <p class="block-content">
diff --git a/demos/quickstart/protected/pages/Fundamentals/Pages.page b/demos/quickstart/protected/pages/Fundamentals/Pages.page
index 58f4f06d..d52dccf5 100755
--- a/demos/quickstart/protected/pages/Fundamentals/Pages.page
+++ b/demos/quickstart/protected/pages/Fundamentals/Pages.page
@@ -15,7 +15,7 @@ A form submission is called <i>postback</i> if the submission is made to the pag
 <tt>TPage</tt> has a <tt>IsPostBack</tt> property exposing whether the current request being handled is the first request for this page or the consequence of a postback.

 </p>

 

-<h2>CallBack</h2>

+<h2 id="32008">CallBack</h2>

 <p class="block-content">

 A <i>callback</i> is a special form submission that, instead of requiring a full page reload on the browser, gets executed in the background through an ajax call. So, a callback is considered a postback too, but not vice versa.

 <br/>

diff --git a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
index 018a493e..e3626bcc 100755
--- a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
+++ b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
@@ -110,22 +110,22 @@ PostRecord#1
 </com:TTextHighlighter>

 </p>

 

-<h2>Creating Active Record Classes</h2>

-<p>

+<h2 id="14007">Creating Active Record Classes</h2>

+<p id="70001" class="block-content">

 In the blog demo project, we need to create two <a href="?page=Database.ActiveRecord">Active Record</a> classes, <tt>UserRecord</tt> and <tt>PostRecord</tt>, to represent data records in the <tt>users</tt> and <tt>posts</tt> tables, respectively. Active Record classes must extend from the base class <tt>ActiveRecord</tt>, and must define property names that matches with the field names of the corresponding table.

 </p>

 

-<p>

+<p id="70002" class="block-content">

 To better organize our directories, we create a new directory <tt>protected/database</tt> to hold the class files. We also modify our application configuration by inserting the following lines. It is equivalent to adding the directory <tt>protected/database</tt> to PHP include_path, which allows us to use the classes without explicitly including them.

 </p>

 

-<com:TTextHighlighter CssClass="source" Language="xml">

+<com:TTextHighlighter CssClass="source block-content" id="code-70014" Language="xml">

 <paths>

   <using namespace="Application.database.*" />

 </paths>

 </com:TTextHighlighter>

 

-<p>

+<p id="70003" class="block-content">

 At the prompt, enter the following two commands to create <tt>UserRecord</tt> and <tt>PostRecord</tt> classes:

 </p>

 

@@ -135,7 +135,7 @@ At the prompt, enter the following two commands to create <tt>UserRecord</tt> an
 >> generate posts Application.database.PostRecord

 </com:TTextHighlighter>

 

-<p>

+<p id="70004" class="block-content">

 Here we used the <a href="?page=Fundamentals.Components1">namespace format</a> again to specify the classes to be created. The path <tt>Application.database.UserRecord</tt> indicates that we want the <tt>UserRecord</tt> class file to be <tt>protected/database/UserRecord.php</tt>.

 </p>

 

diff --git a/demos/quickstart/protected/pages/GettingStarted/Installation.page b/demos/quickstart/protected/pages/GettingStarted/Installation.page
index 956f53c2..f59eed70 100755
--- a/demos/quickstart/protected/pages/GettingStarted/Installation.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Installation.page
@@ -13,7 +13,7 @@ The minimum requirement by PRADO is that the Web server support PHP 5.3.3. PRADO
 PRADO can be installed as a standalone package or using <a href="http://getcomposer.org/">composer</a>

 </p>

 <div id="install-steps" class="block-content">

-<h3>Standalone package</h3>

+<h3 id="6001">Standalone package</h3>

 <ol>

 <li>Go to <a href="http://www.pradosoft.com/download/">pradosoft.com</a> to grab the latest version of PRADO.</li>

 <li>Unpack the PRADO release file to a Web-accessible directory.

@@ -28,7 +28,7 @@ If you encounter any problems with the demo applications, please use the PRADO r
 </p>

 

 <div id="install-steps" class="block-content">

-<h3>Composer install</h3>

+<h3 id="6002">Composer install</h3>

 <ol>

 <li>If you don't have installed composer already, install it globally:

 <com:TTextHighlighter CssClass="source block-content">

diff --git a/demos/quickstart/protected/pages/GettingStarted/Wsat.page b/demos/quickstart/protected/pages/GettingStarted/Wsat.page
index f9395aa0..6d7ddb37 100644
--- a/demos/quickstart/protected/pages/GettingStarted/Wsat.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Wsat.page
@@ -1,5 +1,5 @@
 <com:TContent ID="body">
-    <h1>Web Site Administration Tool</h1>
+    <h1 id="12003">Web Site Administration Tool</h1>
     <p class="block-content">
         Web Site Administration Tool (WSAT) is a development tool which allows you to perform several
         tedious tasks of a PRADO project in a GUI fashion. Its inspired in both Asp.Net - Web Site Administration Tool and Yii's Gii.
@@ -12,12 +12,12 @@
         </ul>
     </p>
 
-    <h2>Requirements</h2>
+    <h2 id="12004">Requirements</h2>
     <p class="block-content">
         To use WSAT, you need to add in your project configuration file: <tt>application.xml</tt>, 
         in the services section the wsat service like follows:
 
-<com:TTextHighlighter CssClass="source" Language="xml">
+<com:TTextHighlighter CssClass="source block-content" id="code-60007" Language="xml">
 <services> 
     ...
     <service id="wsat" class="System.Wsat.TWsatService" Password="my_secret_password" />
@@ -25,7 +25,7 @@
 </com:TTextHighlighter>
     </p>
 
-    <h2>Usage</h2>
+    <h2 id="12005">Usage</h2>
     <p class="block-content">
         Then you are ready to go to: http://localhost/yoursite/index.php?wsat=TWsatLogin and doing so you should see
         the following page:
@@ -36,7 +36,7 @@
         is part of a basic security system to avoid undesirable persons to use this tool.
     </p>
     
-    <h2>Active Record classes generation</h2>
+    <h2 id="12006">Active Record classes generation</h2>
     <p class="block-content">
         In order to generate AR classes you need to go to: http://localhost/yoursite/index.php?wsat=TWsatGenerateAR 
         by clicking the proper links in the welcome page. Then you should see the following page: