Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #3715 (closed)

Opened 9 years ago

Closed 8 years ago

Web UI "app behavior" review

Reported by: wmoore Owned by: saloynton
Priority: major Milestone: Usability Backlog
Component: General Keywords: n.a.
Cc: atarkowska Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: 0.0d Estimated Remaining Time: n.a.

Description

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".


Change History (3)

comment:1 Changed 9 years ago by agilo

  • Status changed from new to accepted

Updated status, related task in progress

comment:2 Changed 8 years ago by saloynton

  • Milestone changed from OMERO-Beta4.3 to Usability

comment:3 Changed 8 years ago by wmoore

  • Resolution set to fixed
  • Status changed from accepted to closed

Closing this since I think we have decided the web client can have App-like behaviour (double-click, right-click etc).

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.103804 sec.)

We're Hiring!