svn commit: r550704 - /incubator/xap/site/docs/xmodify/content/overview.html

[bb...@apache.org]

Author: bbuffone
Date: Mon Jun 25 23:16:10 2007
New Revision: 550704

URL: http://svn.apache.org/viewvc?view=rev&rev=550704
Log:
Added more content to the overview page.

Modified:
    incubator/xap/site/docs/xmodify/content/overview.html

Modified: incubator/xap/site/docs/xmodify/content/overview.html
URL: http://svn.apache.org/viewvc/incubator/xap/site/docs/xmodify/content/overview.html?view=diff&rev=550704&r1=550703&r2=550704
==============================================================================
--- incubator/xap/site/docs/xmodify/content/overview.html (original)
+++ incubator/xap/site/docs/xmodify/content/overview.html Mon Jun 25 23:16:10 2007
@@ -23,14 +23,29 @@
 							<!-- start: body of page -->
 <p><h2><span class="Title">xModify Overview</span></h2></p>
 
-<p>xModify can be used to create or update XML documents, XAL, and HTML declaratively and provides an alternative to using programmatic APIs.
-</p> 
-
+<p>Ajax changes web applications from stateless and page-based into stateful.  Developers use the XHR
+object to load data and content from the server and update the state of the page by changing the HTML document.  This is typical done
+by retrieving data in the form of XML or JSON. Once on the client, the developer will 
+looping over the data set using JavaScript and insert, replace or modify HTML DOM elements.  This can require lots of JavaScript
+even if the developer uses a library such as jQuery, MooTools, ... 
+<br><br>XAP has incorporated an XML syntax called xModify can be used to create or update XML, XAL, 
+and HTML elements declaratively.  This means that developers can 
+utilize server-side frameworks to create XML modify documents that an xModify Processor will use to update the HTML or 
+XAL document.  <br><br>
 
 <p><h2><span class="Title">xModify Workflow</span></h2></p>
 <p align="center">
 	<img src="../images/xModifyOverview.gif">
 </p>
+
+<b>Why is this Helpful?</b><br><br> Because instead of having to create JavaScript to update the UI for a particular dataset, the developer
+can use server-side functionality such as PHP, J2EE, Ruby, XSLT to create XML documents that can to the same thing.  This 
+typically will save code, time and increase the maintainablity of the application.  <br><br>
+The second reason this is helpful is that xModify puts the know-how to into a well defined XML layer, instead of either a 
+client-side or server-side library.  XML can be used in any server-side or client-side layer, making it more likely that knowledge of
+xModify leverage across projects.<br><br>
+</p> 
+
 
 <p><h2><span class="Title">Operations</span></h2></p>
 <p>