From xap-commits-return-1467-apmail-incubator-xap-commits-archive=incubator.apache.org@incubator.apache.org Wed Jun 27 15:39:38 2007 Return-Path: Delivered-To: apmail-incubator-xap-commits-archive@locus.apache.org Received: (qmail 25357 invoked from network); 27 Jun 2007 15:39:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2007 15:39:37 -0000 Received: (qmail 76010 invoked by uid 500); 27 Jun 2007 15:39:41 -0000 Delivered-To: apmail-incubator-xap-commits-archive@incubator.apache.org Received: (qmail 75990 invoked by uid 500); 27 Jun 2007 15:39:40 -0000 Mailing-List: contact xap-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: xap-dev@incubator.apache.org Delivered-To: mailing list xap-commits@incubator.apache.org Received: (qmail 75981 invoked by uid 99); 27 Jun 2007 15:39:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2007 08:39:40 -0700 X-ASF-Spam-Status: No, hits=-99.5 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO eris.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jun 2007 08:39:36 -0700 Received: by eris.apache.org (Postfix, from userid 65534) id B6E7B1A981A; Wed, 27 Jun 2007 08:39:16 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r551202 - /incubator/xap/site/index.html Date: Wed, 27 Jun 2007 15:39:16 -0000 To: xap-commits@incubator.apache.org From: bbuffone@apache.org X-Mailer: svnmailer-1.1.0 Message-Id: <20070627153916.B6E7B1A981A@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: bbuffone Date: Wed Jun 27 08:39:15 2007 New Revision: 551202 URL: http://svn.apache.org/viewvc?view=rev&rev=551202 Log: fixed spelling and grammar errors. Modified: incubator/xap/site/index.html Modified: incubator/xap/site/index.html URL: http://svn.apache.org/viewvc/incubator/xap/site/index.html?view=diff&rev=551202&r1=551201&r2=551202 ============================================================================== --- incubator/xap/site/index.html (original) +++ incubator/xap/site/index.html Wed Jun 27 08:39:15 2007 @@ -119,7 +119,7 @@ The Ajax Open Source Declarative Framework

XAP is an XML-based declarative framework for building, - deploying and maintaining rich, interactive Ajax powered web applications.  It aims to reduce + deploying and maintaining rich, interactive Ajax powered web applications.  XAP aims to reduce the need for scripting and help solve the development and maintenance challenges associated with large scale JavaScript programming.

@@ -141,13 +141,11 @@ </xal>

-

XAP provides a complete framework for building Ajax applications. Whether you're building - a large application with many screens or you simply want to enhance an existing website with Ajax. -

- The XAP project can help get your project done quicker and easier.

+

XAP is a complete framework for building Ajax applications. Whether you're building + a large application with many screens or you simply want to enhance an existing website with Ajax, the XAP project can help get your project done quicker and easier.

- Why is Declaritive important?
+ Why is Declarative important?

Markup languages provide several key benefits to application development:

  • Provide an abstraction and normization layer between the underlying implementation and the developer. @@ -156,18 +154,18 @@ worry what the underlying API calls are.

    • -
  • Markup languages provide a solid base to build tooling ontop off. +
  • Markup languages provide a solid base to build tooling on top of.

    How many visual tools are there for HTML? Plenty.
    - How many for JavaScript? No Many. + How many for JavaScript? Not many. -

    This is becuase makup is well defined and tools can easily read and write it. Even if a +

    This is because markup is well defined and tools can easily read and write it. Even if a developer changes it by hand, the markup still remains readable by a tool.

    • -
  • Markup languages are easier to understand and simpler to pick up then code. Would web application - development grown so quickly if developers had to use JavaScript to create all web applications? - Probably Not. +
  • Markup languages are easier to understand and learn than code. Would web application + development have grown so quickly if developers had to use JavaScript to create all web applications? + Probably not.

@@ -203,29 +201,29 @@ - Whats cool in XAP? + What's cool in XAP?
 xModify - > Makes it possible to use a - markup to to DOM modification agianst either the HTML document or the XAL UI document.

+ declarative markup to execute DOM modification against either the HTML document or the XAL UI document.

-

3 KB implementation
ontop of jQuery

+

3 KB implementation
on top of jQuery

Click the "Processors" link in the xModify documentation section.



 UI - > XAP has all the widgets that are needed to get started building large Ajax Applications: table, tree, tab, dialog, layout panels, splitter, form components, Google Maps, Yahoo Maps, Live Maps, ...

-  Marcos - > Developers can use macros to execute xModify operations via the XAP +  Macros - > Developers can use macros to execute xModify operations via the XAP JavaScript APIs or through the event handler expression language.

<button text="Login" onCommand= "macro:myMacro.execute()"/>

-  MCO - > Keep your business logic completely seperated from +  MCO - > Keep your business logic completely separated from the UI definition. This make code maintenance easier and development quicker. The XAP client will create the JavaScript POJOs which can be accessed from the UI markup via a simple expression language.

<button text="Login" onCommand= "mco:myEventCode.functionName()"/> @@ -251,7 +249,7 @@
- Copyright 2006 + Copyright 2006-2007 The Apache Software Foundation