Difference between revisions of "Ajax Client"
(→Alternative Architecure) |
|||
| Line 1: | Line 1: | ||
==Architecture== | ==Architecture== | ||
| − | Thick | + | |
| + | === Thick Javascript Client === | ||
| + | Rendering of UI will be done on the client side using advance javascript GUI framework like [http://dojotoolkit.org/ Dojo], [http://qooxdoo.org/ Qooxdoo] or [http://code.google.com/webtoolkit/ 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. | There should be minimum changes required on the current ADempiere core. | ||
| + | |||
| + | === Thin Javascript Client === | ||
| + | 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. | ||
| + | *[http://www.nextapp.com/platform/echo2/echo/ Echo2] | ||
| + | **Swing like API | ||
| + | **[http://www.nextapp.com/platform/echo2/echo/demo/ Online Demo] | ||
| + | *[http://www.eclipse.org/rap Eclipse RAP] | ||
| + | **Using the proven eclipse plugin architecture | ||
| + | **[http://rap.innoopract.com/rap?w4t_startup=default&w4t_scriptEnabled=false&w4t_ajaxEnabled=false&w4t_width=1024&w4t_height=768 Online Demo] | ||
| + | *[http://www.zkoss.org ZK] | ||
| + | **Swing like API | ||
| + | **[[Flash_Demo_of_Ajax_Client|POC started by the Posterita team]] | ||
| + | **[http://www.zkoss.org/zkdemo/userguide/ Online Demo] | ||
==Dynamic Data Format== | ==Dynamic Data Format== | ||
| Line 34: | Line 49: | ||
*[[User:Agramdass|Ashley G Ramdass]] (posterita) | *[[User:Agramdass|Ashley G Ramdass]] (posterita) | ||
* (pls add your name here - pros only) | * (pls add your name here - pros only) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category:Projects]] | [[Category:Projects]] | ||
Revision as of 00:52, 2 April 2007
Contents
Architecture
Thick Javascript Client
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.
Thin Javascript Client
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.
- Echo2
- Swing like API
- Online Demo
- Eclipse RAP
- Using the proven eclipse plugin architecture
- Online Demo
- ZK
- Swing like API
- POC started by the Posterita team
- Online Demo
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
- Ashley G Ramdass (posterita)
- (pls add your name here - pros only)
