Difference between revisions of "Ajax Client"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Alternative Architecure)
(Team Members)
Line 32: Line 32:
 
==Team Members==
 
==Team Members==
 
* (pls add your name here - pros only)
 
* (pls add your name here - pros only)
 +
 +
Ashley G Ramdass (posterita)
  
 
==Alternative Architecure==
 
==Alternative Architecure==

Revision as of 06:04, 18 March 2007

Architecture

Thick javascript client base on the existing Swing client architecture. Rendering of UI will be done on the client side using advance javascript GUI framework like Dojo, Qooxdoo or GWT. The server-side is exposed to the javascript client as RESTian or JSON-RPC endpoint to served and process dynamic data. The primary motivation of this approach is to produce richer, more performant UI experience than the Thin Client. There should be minimum changes required on the current ADempiere core.

Dynamic Data Format

JSON instead of XML is use as it produces more compact representation , it is blazingly fast to parse on a client — essentially simple JavaScript eval() would do, and it is very simple to parse on a server too.

Transport

  • XMLHttp
The XMLHttp transport is the default transport. It works well in most cases, but it cannot transfer files.
  • IFrame
The IFrame I/O transport is useful because it can upload files to the server.

Proof Of Concept

A prototype should be build as a POC. The prototype should demonstrate the following features:

  • Login
  • Tree Menu
  • Opening of window
  • Preview of report

Please find a demo of posterita POC for the ajax client. posterita ajax client Implemented by: Ashley Ramdass

Schedule

Current plan is to build a POC and demonstrate at the ADempiere Europe Conference this May.

Resource

Team Members

  • (pls add your name here - pros only)

Ashley G Ramdass (posterita)

Alternative Architecure

Another alternative is a server side model where the application code is mainly running on the serverside and smartly refreshing the client by using AJAX. This could be the easier path as more code from the current Swing client can be reused.