User Story #3715 (closed)
Web UI "app behavior" review
|Reported by:||wmoore||Owned by:||saloynton|
|Total Remaining Time:||0.0d||Estimated Remaining Time:||n.a.|
Should Web Client behave like the web or try to emulate an application?
Should we have right-click menus, double-click handling, shift-click etc?
Summary of my opinion:
- Web should use all right-click, double-click functionality etc in order to emulate Insight functionality as close as possible.
- No web functionality should rely on right-click, double-click to access it. I think this is already true for Insight?
- Web and Insight should attempt to have everything in the same place, layout etc.
- Gradually migrate functionality from Insight to web (prioritise most-used functions) BUT also review Insight at the same time, since it contains some stuff that we might want to clean up.
- Bevelled borders vv 'flat' UI has little effect on user's expectations. (if it *behaves* like an application (e.g. collapsible trees), users will expect application-like functionality).
Summary of Ola's opinion (hope I've got this right)
- Need to review various available web applications to asses their use of 'non-web' behavior (right-click, double-click etc)
- Bevelled borders and other UI features are important clues to users about how the UI will behave: "If it *looks* like the web it'll behave like web".