incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "XapProposal" by cwei
Date Tue, 02 May 2006 02:53:43 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by cwei:
http://wiki.apache.org/incubator/XapProposal

------------------------------------------------------------------------------
  April 2006, Coach Wei (cwei at nexaweb dot com)
  
  == PROJECT PROPOSAL ==
- XAP is to provide an XML-based declarative framework for building, deploying and maintaining
rich, interactive, Ajax-powered web applications, reducing the need to struggle with JavaScript
and DHTML, solving the development challenge as well as application maintenance challenges
associated with Ajax programming. 
- 
- A basic principal of XAP is to leverage existing Ajax toolkits such as Apache Kabuki and
Dojo, as well as W3C's standardization efforts in the Rich Client area. It aims to be pluggable
with various Ajax toolkits, lower development complexity, and provide feedback to W3C's working
groups.
+ XAP is to provide an XML-based declarative framework for building, deploying and maintaining
rich, interactive, Ajax-powered web applications. A basic
+ principal of XAP is to leverage existing Ajax projects such as Apache Kabuki
+ and Dojo, as well as other community efforts. It aims to be pluggable with
+ various Ajax toolkits, reduce the need of scripting and solve the development
+ challenge as well as application maintenance challenges associated with
+ Ajax programming.
  
  == 0. Rationale ==
  
@@ -18, +21 @@

  
  Although these toolkits ease development of Ajax-powered web applications, there are still
significant development and maintenance challenges, mainly associated with writing, debugging
and maintaining JavaScript code. In particular, some developers would prefer not to use JavaScript.
  
- There are many possible solutions to address these challenges and each approach can solve
the challenges to a different degree. On the one side, open source community has responded
with [http://incubator.apache.org/projects/kabuki.html Apache Kabuki] and Eclipse [http://www.eclipse.org/atf/
openAjax] projects. On the other side, W3C has started a working group (Web Application Formats)
aimed at creating a declarative format for applications and user interfaces as part of W3C's
Rich Web Client Activity. A higher level abstraction via a declarative format helps solve
the Ajax development challenges by reducing the need for scripting while providing a straightforward
way of building rich user interfaces, but also provides a mechanism to combine the above mentioned
community efforts together for greater benefits.
+ There are many possible solutions to address these challenges and each approach can solve
the challenges to a different degree. On the one side, open source community has responded
with [http://incubator.apache.org/projects/kabuki.html Apache Kabuki] and Eclipse [http://www.eclipse.org/atf/
openAjax] projects. On the other side, standard organizations have been working on standardizing
Ajax(XmlHttpRequest for example) and related browser behaviors. A higher level abstraction
via a declarative format helps solve the Ajax development challenges by reducing the need
for scripting while providing a straightforward way of building rich user interfaces, but
also provides a mechanism to combine the above mentioned community efforts together for greater
benefits.
  
- Building on these vibrant community efforts already underway, the proposed project is to
create an extensible software framework for building and deploying Ajax-powered rich internet
applications declaratively. The project is "pluggable" with client side Ajax toolkits such
as Kabuki, works with openAjax as well as supports W3C's declarative format effort. The mission
of this project is to encourage innovation around declarative Ajax development, build a community,
and provide feedback to W3C's Web Application Formats Working Group so that we can create
the appropriate standards
+ Building on these vibrant community efforts already underway, the proposed project is to
create an extensible software framework for building and
+ deploying Ajax-powered rich internet applications declaratively. The project
+ is "pluggable" with client side Ajax toolkits such as Kabuki, works with
+ openAjax as well as other Ajax initiatives. The mission of this project is to
+ encourage innovation around declarative Ajax development, build a community,
+ and provide an open source framework for building and deploying rich internet
+ applications independent of browsers and servers.
  
  This project seeks to provide
  
@@ -29, +38 @@

   * Declarative modification syntax for updating the user interface;
   * A "bridge" mechanism that allows easy plug-in of existing UI Ajax toolkits.
   * A framework that ties everything together; enabling asynchronous update and event handling;
- 
- In addition, further down the road, this proposal seeks to provide a reference implementation
of the W3C Web Application Formats working group specification that provides a declarative
format for applications and user interfaces.
  
  The architecture of this proposal embraces existing Ajax toolkits, such as Apache Kabuki
and Dojo. At the core of the architecture is the concept of "bridges" that allow declarative
tags to be connected to any toolkit and allow the toolkits to be easily interchanged. It also
supports "plugins", allowing tags to be easily added or extended to support custom widgets
and behavior.
  
@@ -57, +64 @@

  
  More than half of the initial committers are key members of Nexaweb's development, test,
and project management team. The rest are developers who have had significant experience with
the framework or the technologies it is built upon. Some of these committers are contributing
to this project on behalf of their employer, some of them are self-employed consultants, and
some of them are just contributing as individuals.
  
- Two of the initial committers are part of W3C's Web Application Format Working Group (Cliff
Schmidt and Coach Wei).
  
  === Alignment: ===
  
@@ -148, +154 @@

   * Robert Buffone
   * Cliff Schmidt
   * Coach Wei
+  * Michael Turyn
   * Peter Eacmen
   * Animesh Kumar
   * Jonathan Levin

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message