Labs/Joey/clients/ajaxy/functional

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Design Overview

• working on this now! - mgalli

AJAX Layer Over Declarative XHTML UI

Aspect approach where CakePHP produces XHTML simplified data as the representation of the UI. In a way it is like elimating the HTML view aspect of it, or to model it so that it is very semantic and provided for the UI toolkit layer. The UI toolkit layer uses this view ( User Agent Interface - UAI ) and creates the actual UI ( user interface ).

Then have the client side AJAX toolkit to model the declarative markup to create the end-user visual interface.

Dojo Considerations in the scope of Joey UI Flows

ContentPane

Ref http://dojotoolkit.org/node/55

• Ability to fetch dynamic content and apply it to the current document;
• Good for accessing additional interfaces in the Joey flow;
• Good for Next Previous buttons in a range list of dynamic retrieved elements;
• Pluses - comes with built in "Loading.. " state signal;
• Pluses - cache function , we may be able to store Previous panes in the list content
• Pluses - executeScripts true - can execute scripts loaded with the content.

Dojo Forms

http://dojotoolkit.org/node/59

• Form Bind - maps the traditional form to an XMLHTTPRequest. With this model, we can keep a FORM data in the client, and use it to create the transaction in the XHR channel. Would keep compability and probably would help us to keep the idea of an XHTML simplified + FORMS from CakePHP.

Dojo Events Connect

http://dojotoolkit.org/node/134

* Additional on Events http://dojotoolkit.org/node/88
* Dojo Events are general, for event flow control and an observation mechanism. Can be also used to listen to actual DOM UI events.

Dojo Undo

* In the Dojo package, check tests/undo for the iframe history control information.

Considerations for the Joey Web Client

• Back and Forward via Iframe history
• Strings binding via JSON or dynamic load of content panel ( or declarative strings markups delivered to the client from the CakePHP )

Architectural Goals

• To keep a simplified old school XHTML interface so that the Web site can be tested and also used from a testing user agent perspective.
• To allow multiple variations and User Interface intepretations to the end-user UI, for example a future version of the application to have a stack of options and possibly layered user interface wrappers - for example a a mode to add accessibility customizations, for example zoom control, color manipulation to the theme, and more.
• Be completible with multiple AJAX client toolkits, and keep this compatibility layer via XHTML core User Interface layer - also referenced here as the semantic layer.
• Log execution of a test case end-user flow, via dumping all the XHTML responses and REST queries.