|
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 / Cake PHP
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.