Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323623 - [ipad] Improve touch-feedback
Summary: [ipad] Improve touch-feedback
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 332512
Blocks: 323032
  Show dependency tree
 
Reported: 2010-08-25 11:11 EDT by Tim Buschtoens CLA
Modified: 2012-03-02 05:02 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2010-08-25 11:11:03 EDT
When touching an widget the ipad seems not to react at times, either because the user missed or because it needs some time until the changes are recieved and rendered. But the user has no feedback for either of these cases. There are two non-exclusive ways to solve this:

1. Create a visual touch-feedback so the user sees where he has hit.
As small image or animation could be displayed after a touch for about a second on the coordinates of the touch.

2. Display a wait-animation when the applications is busy/blocked by a server-request. Usually the mouse-pointer is turned into a hour-glass or something, but since there is no pointer on the ipad, its not visible.
Comment 1 Tim Buschtoens CLA 2010-08-30 09:34:00 EDT
For (1) we could use the overlays disabled in Bug 323132 by re-enabling them for specific divs in the application. This could even be made themeable.
Comment 2 Tim Buschtoens CLA 2010-12-14 06:21:48 EST
Opend a seperate bug for issue 2, as its not ipad-specific: Bug 332512
Comment 3 Austin Riddle CLA 2011-04-18 15:15:13 EDT
One constraint on touch feedback is the fact that the user's finger is covering the place where the feedback will take place and they won't be able to see the feedback (unless it is sufficiently large) until they move their finger.
Comment 4 Tim Buschtoens CLA 2011-04-19 06:33:42 EDT
Some thoughts on this:

- The idea i had with the wait-animation is probably not going to work because the lack of responseiveness is mostly because the client is busy, not the server. Sine its not possible to predice how long the client will be blocked, there is no way to solve this imo.

- Yes, the size finger is a problem. There are multiple ways to attack that problem: 

1 - Make controls bigger than the finger and make theming have bright colors for pressed/hover state, so the state of the button is better visible. There is a reason why buttons on mobile apps are oftern either very big or very wide. This can already be done right now, but could also be solved in a generic way by creating a mobile theme.

2 - The already described image/dot/animation at the touched position. It would have to be continued to be displayed at the point where the touchend occured for about a second.

3 - Another idea i had is to use shadows to give a currently touched control a bright glow around the widget. This can currently not be done because button and most other widgets dont support shadows and because the is currently no support for spread in shadows.
Comment 5 Tim Buschtoens CLA 2012-02-29 05:21:37 EST
With the focus of RAP on mobile devices having changed to native clients, i
would close this bug as wontfix. Unless anyone objects i will close it in a few
days.