summaryrefslogtreecommitdiff
path: root/demos/quickstart/protected/pages/Fundamentals/Pages.page
diff options
context:
space:
mode:
authorFabio Bas <ctrlaltca@gmail.com>2014-01-12 21:33:46 +0100
committerFabio Bas <ctrlaltca@gmail.com>2014-08-23 12:34:07 +0200
commit1144e49b8e00fa75b1593e4637c9218d7d944b97 (patch)
tree363c96c164a76587a306319a871ecceefe5c0cb6 /demos/quickstart/protected/pages/Fundamentals/Pages.page
parent9733613002b664ec9cbdc6dec9d6fd57ee901f1e (diff)
Big quickstart doc overhaul, pt. 1
Diffstat (limited to 'demos/quickstart/protected/pages/Fundamentals/Pages.page')
-rwxr-xr-xdemos/quickstart/protected/pages/Fundamentals/Pages.page14
1 files changed, 13 insertions, 1 deletions
diff --git a/demos/quickstart/protected/pages/Fundamentals/Pages.page b/demos/quickstart/protected/pages/Fundamentals/Pages.page
index 19900937..0f3a8d9f 100755
--- a/demos/quickstart/protected/pages/Fundamentals/Pages.page
+++ b/demos/quickstart/protected/pages/Fundamentals/Pages.page
@@ -5,7 +5,7 @@
Pages are top-most controls that have no parent. The presentation of pages are directly displayed to end-users. Users access pages by sending page service requests.
</p>
<p id="130138" class="block-content">
-Each page must have a <a href="?page=Configurations.Templates1">template</a> file. The file name suffix must be <tt>.page</tt>. The file name (without suffix) is the page name. PRADO will try to locate a page class file under the directory containing the page template file. Such a page class file must have the same file name (suffixed with <tt>.php</tt>) as the template file. If the class file is not found, the page will take class <tt>TPage</tt>.
+Each page can have a <a href="?page=Configurations.Templates1">template</a> file. The file name suffix must be <tt>.page</tt>. The file name (without suffix) is the page name. PRADO will try to locate a page class file under the directory containing the page template file. Such a page class file must have the same file name (suffixed with <tt>.php</tt>) as the template file. If the class file is not found, the page will take class <tt>TPage</tt>.
</p>
<h2 id="902">PostBack</h2>
@@ -14,6 +14,18 @@ A form submission is called <i>postback</i> if the submission is made to the pag
</p>
+<h2>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/>
+A callback is handled as a normal postback but, instead of re-rendering the entire page, only the specific changes occured on the page gets sent back to the client and merged with the current browser page. A typical callback response consists of:
+<ol>
+ <li>one or more pieces of html code that will replace existing content on the page;</li>
+ <li>the javascript instructions needed to update the page;</li>
+ <li>some specific fields used by prado to mantain the pagestate and add the needed external resources (stylesheets, javascript files, etc..).</li>
+</ol>
+</p>
+
<h2 id="903">Page Lifecycles</h2>
<p id="130140" class="block-content">
Understanding the page lifecycles is crucial to grasp PRADO programming. Page lifecycles refer to the state transitions of a page when serving this page to end-users. They can be depicted in the following statechart,