Difference between revisions of "Diagram viewer control"
(First sav - NOT COMPLETED) |
m (add breadscrump) |
||
| Line 1: | Line 1: | ||
| + | [[New Report Design 2009]] => [[Diagram viewer control]] | ||
| + | |||
| + | |||
== Introduction == | == Introduction == | ||
In current implementation, there is no specific implementation for a ''DiagramViewer'' while it should. There are couple of places where diagram can be viewed but with separate implementation, just to name some: | In current implementation, there is no specific implementation for a ''DiagramViewer'' while it should. There are couple of places where diagram can be viewed but with separate implementation, just to name some: | ||
Revision as of 08:31, 30 July 2009
New Report Design 2009 => Diagram viewer control
Introduction
In current implementation, there is no specific implementation for a DiagramViewer while it should. There are couple of places where diagram can be viewed but with separate implementation, just to name some:
- Diagram viewer
- Report viewer
- Monitor
- Dashboard
- Tabulation result viewer
So, for the sake of consistency, I decided to make a DiagramViewer control that can be used all over places.
Design Decisions
- Use the model from Microsoft AJAX.NET that has been applied for resource-ex controls. See the instruction for implementation here
- The design must reuse the nice features of asynchronous processing that have been applied by Chuong and Dennis
- AjaxPro is used as a mean for calling server's code from client-side
- Crash message must be controlled by the control itself (no dump screen), instead user has the ability to enable/disable viewing of full error message
