Ticket #122 (enhancement)
Opened 6 years ago
Last modified 4 years ago
AJAX support and Web client front-end standardization
Status: new
| Reported by: | johnsa | Assigned to: | johnsa |
|---|---|---|---|
| Priority: | major | Milestone: | Bedework 4.0 |
| Component: | web clients | Version: | |
| Keywords: | Cc: | ||
The many new features added in version 3.3 have led to an increased need to clean up the once-simple web client user interfaces. IDs and classes should be standardized, the xslt needs to be modularized for easier editing and maintenance -- also for easier adoption, customization, internationalization, and portlet development.
AJAX features will simplify the user interface substantially and will provide drag-and-drop capabilities for time-based grids (which we intend to add) and other components. Better in-context menuing and in-context help will also be facilitated by this approach. We will explore the numerous open-source ajax libraries to assist in this development. At the same time, our exisiting javascript libraries will be modernized and cleaned up.
====
Asynchronous requests need to be carefully considered for portal agnosticism. We may find a means of getting around the portlet spec for most portal implementations, but this needs to be understood. Also we need to understand in what way asynchronous requests work with or outside of our transaction scheme (and what's appropriate).
Regardless of asynchronous requests, we will use much more dhtml, contextual menus, and check the speed of our existing libraries (the current Dojo 0.4 library is slow loading) to improve the speed of our most important forms and UI components.
Change History
05/03/07 10:56:17: Modified by johnsa
- description changed.
07/20/07 00:10:21: Modified by douglm
- milestone changed from Bedework 3.4 to Bedework 4.0.
05/17/08 14:01:48: Modified by johnsa
05/17/08 14:02:48: Modified by johnsa
- description changed.
02/12/09 01:02:06: Modified by johnsa
As of version 3.5 we have begun adding asynchronous requests to improve aspects of the UI. This approach will be much more fully implemented in 4.0
Asynchronous requests need to be carefully considered for portal agnosticism. We may find a means of getting around the portlet spec for most portal implementations, but this needs to be understood. Also we need to understand in what way asynchronous requests work with or outside of our transaction scheme (and what's appropriate).
Regardless of asynchronous requests, we will use much more dhtml, contextual menus, and check the speed of our existing libraries (the current Dojo 0.4 library is slow loading) to improve the speed of our most important forms and UI components.