Added (partial) website + misc updates for release

* recreated the prado website in demos/
* updated some docs to reflect the usage of jquery; removed guide to
prototype
 * updated composer
 * added task for apigen4 (theme still missing)

4 files changed, 17 insertions, 17 deletions

diff --git a/demos/quickstart/protected/pages/GettingStarted/CommandLine.page b/demos/quickstart/protected/pages/GettingStarted/CommandLine.page
index 3619d3d9..9e919212 100644
--- 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="18007">Creating Active Record Classes</h2>

+<p id="90001" 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="90002" 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_90016" Language="xml">

 <paths>

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

 </paths>

 </com:TTextHighlighter>

 

-<p>

+<p id="90003" 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="90004" 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/Upgrading32.page b/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page
index e2378ed5..7e630488 100644
--- a/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page
+++ b/demos/quickstart/protected/pages/GettingStarted/Upgrading32.page
@@ -1,6 +1,6 @@
 <com:TContent ID="body" >
 
-<h1>Upgrading from v3.2</h1>
+<h1 id="12003">Upgrading from v3.2</h1>
 
 <div class="block-content">
 <p class="block-content">
@@ -17,7 +17,7 @@ We summarize in the following the most significant changes in v3.3 to help devel
 </p>
 </div>
 
-<h2>Basic Prototype to jQuery javascript porting</h2>
+<h2 id="12004">Basic Prototype to jQuery javascript porting</h2>
 <p class="block-content">
 The number one rule on writing jQuery javascript code is to read the <a href="http://api.jquery.com/">jQuery documentation</a>. Porting code from Prototype to jQuery needs some effort: here's a basic lookup table to port existing code:
 </p>
@@ -168,7 +168,7 @@ The number one rule on writing jQuery javascript code is to read the <a href="ht
 	</tr>
 </table>
 
-<h2>PRADO specific code changes</h2>
+<h2 id="12005">PRADO specific code changes</h2>
 <p class="block-content">
 PRADO
 Porting prado to jQuery some method signatures has changed, or have been adapted:
@@ -207,7 +207,7 @@ Porting prado to jQuery some method signatures has changed, or have been adapted
 	</tr>
 </table>
 
-<h2>Specific controls changes</h2>
+<h2 id="12006">Specific controls changes</h2>
 <p class="block-content">
 Some Prado controls were based on specific extensions of the Prototype + Scriptaculous javascript framework, and they have been deprecated now that jQuery has become the primary js framework in PRADO.
 PRADO 3.3 introduces jQuery-based counterpart for these controls and encourage everyone to port their code to the new controls, but the old controls are still supposed to work with some minor annoyance:
diff --git a/demos/quickstart/protected/pages/GettingStarted/Wsat.page b/demos/quickstart/protected/pages/GettingStarted/Wsat.page
index 3d07e6f2..a76ca163 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="20008">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="20009">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_100018" 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="20010">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="20011">Active Record classes generation</h2>
     <p class="block-content">
         In order to generate AR classes you need to go to: http://localhost/divermania/index.php?wsat=TWsatGenerateAR 
         by clicking the proper links in the welcome page. Then you should see the following page: