|
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 Client consumes Declarative XHTML UI from Joey CakePHP
Introduction
An aspect oriented design ( as a wish - not as in what we have now :) where CakePHP produces XHTML simplified data that is meaningful as a UI, but in fact the UI is to be used by the Dojo Joey client layer - you could name it a User Agent UI. As we move forward we are to have the CakePHP generated content to be as semantic as possible, but possibly to keep it as a 'old school' UI too, so it is usable as well. Keeping this simplified ( linked pages ) flow would give us a condition to automate tests / keep the interfaces in verbose mode, maybe to even use side tools to grab the tests results with a good reporting layout.
Dojo considerations in the scope of CakePHP n Joey
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.