In relation to http://hbraun.info/2012/09/web-console-architecture-future-directions/
Possible approaches
- GWT Composition
Build time, lowest common denominator, based on building blocks but manual plumbing
- Plugin descriptiors
Abstract model, relies on fixed schema (DMR metadata+UI properties), fixed set of supported traits, can be consumed by many clients
- Runtime extensions
Applicable to both options above. Removes compile time dependecy.
Requirements, Ideas, Nice-to-Have
| Desc | Type |
|---|
| The UI must be able to dynamically render model elements based solely upon its predefined description (the description may (and probably often will) include UI-specific elements to give "hints" to the renderer; i.e. 0 lines of XHTML is better than 10) (note that AS8 descriptions are likely to be more robust and easier to produce than AS7) |
|
| The UI must provide (or work with) a mechanism by which multi-step tasks (so-called "wizards") can be defined and subsequently rendered for specific model element types, such that these operations may be automatically associated with their corresponding model elements (even better if the task metadata were reusable by other tools e.g. CLI) |
|
| Using these tools it should be possible to generate UIs on many platforms (GWT, Swing, iOS/Android, maybe JON, maybe third-party mgmt tools, ???) which all look, act, and "feel" as similar as possible |
|
| i18n |
|
| Authorisation & Authentication |
|
| 508 compliance |
|