Difference between revisions of "Talk:Design Team/Sugar Shell Touch Input"

From Sugar Labs
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
This is a rough brain dump of things to watch out for, will move this out onto other pages where appropriate:
 
This is a rough brain dump of things to watch out for, will move this out onto other pages where appropriate:
  
−
*Gestures
 
−
**Swipe left right on text input widget to move insertion point one character left or right
 
−
**Frame
 
−
***Swipe out over any edge to hide Frame
 
−
***Swipe in over any edge to reveal Frame
 
 
*Test UI at lower resolution
 
*Test UI at lower resolution
 
**Portrait will be used more than it currently once we have touch only HW
 
**Portrait will be used more than it currently once we have touch only HW
Line 14: Line 9:
 
**Hover/right click
 
**Hover/right click
 
**Clarify any primary button actions
 
**Clarify any primary button actions
−
*Frame reveal/hide
+
*Keyboard shortcut usage
−
*Hide cursor during touch screen use
+
**Need any replacements using extra buttons/gestures?
−
*Keyboard shortcuts
+
**Screen display backlight brightness/monochrome behaviour - probably best resolved with a brightness/display device icon & palette as per the volume device
−
**Replacements with buttons/gestures
+
**Hiding keyboard accelerator hints when booting touch only hardware?
−
**Hiding boardkey hints
 
 
*Right click
 
*Right click
 
**Touch and hold gesture
 
**Touch and hold gesture
 +
*Prelight effects are usually for reinforcing UI interaction during a cursor movement/hover. For touch, should it be used to indicate a widget is being held down, or remove prelight effect?
 
*Hover hints/tips
 
*Hover hints/tips
 
*Double tap interaction
 
*Double tap interaction
 
**Make much more accommodating to second tap inaccuracy  
 
**Make much more accommodating to second tap inaccuracy  
−
*Tune cursor touch point to just below top edge of contact point
+
*Tune cursor touch point to just below top edge of contact point (based on screen rotation)
−
*Maximise home view icon size
+
*Maximise home view icon size layout
 
*Widget size usability
 
*Widget size usability
 
**Button spacing
 
**Button spacing
Line 33: Line 28:
 
**8-10mm diameter hit targets
 
**8-10mm diameter hit targets
 
**Up/down menu overflow scroll widgets too short
 
**Up/down menu overflow scroll widgets too short
−
*Screen keyboard
 
−
**Multilingual and international text input
 
−
**Custom activity keys/button strips
 
−
**Trigger on text input entry
 
−
**Slide canvas to see insertion point a.k.a. caret tracking
 
−
**Cut/copy/paste
 
−
**Insertion point movement
 
−
***buttons?
 
−
***swipe gestures?
 
−
**Custom keyboards for different tasks
 
−
***web
 
−
***text
 
−
***emoticon
 
−
***numeric
 
−
**Predictive text?
 
−
***context sensitive?
 
−
***locale sensitive
 
−
**Uppercase font for children
 
−
**keyboard layout descriptions?
 
−
**3 rows vs 4 rows with large space bar?
 
−
**Interaction with frame UI
 
−
***Hide frame when invoked
 
−
***Hide/reveal when frame revealed or hidden
 
−
**Simplify keyboard svg icon
 
−
**Pan canvas to keep insertion point in view
 
−
**Landscape & portrait
 
 
*Remove primary action from Neighbourhood view AP/ad-hoc widgets
 
*Remove primary action from Neighbourhood view AP/ad-hoc widgets
 
*Double tap tuning to allow for errors in 2nd tap positioning
 
*Double tap tuning to allow for errors in 2nd tap positioning

Latest revision as of 21:11, 15 August 2012

Touch things to fix and keep an eye on

This is a rough brain dump of things to watch out for, will move this out onto other pages where appropriate:

  • Test UI at lower resolution
    • Portrait will be used more than it currently once we have touch only HW
    • Need to minimise toolbar overflows and improve touch experience when it does happen
  • Palette behaviours
    • Hover/right click
    • Clarify any primary button actions
  • Keyboard shortcut usage
    • Need any replacements using extra buttons/gestures?
    • Screen display backlight brightness/monochrome behaviour - probably best resolved with a brightness/display device icon & palette as per the volume device
    • Hiding keyboard accelerator hints when booting touch only hardware?
  • Right click
    • Touch and hold gesture
  • Prelight effects are usually for reinforcing UI interaction during a cursor movement/hover. For touch, should it be used to indicate a widget is being held down, or remove prelight effect?
  • Hover hints/tips
  • Double tap interaction
    • Make much more accommodating to second tap inaccuracy
  • Tune cursor touch point to just below top edge of contact point (based on screen rotation)
  • Maximise home view icon size layout
  • Widget size usability
    • Button spacing
    • Palette menu spacing
    • Size of hspan/vspan separator, gtk3 default looking a little better, GtkPaned
    • Check boxes to on/off slider GtkSwitch
    • 8-10mm diameter hit targets
    • Up/down menu overflow scroll widgets too short
  • Remove primary action from Neighbourhood view AP/ad-hoc widgets
  • Double tap tuning to allow for errors in 2nd tap positioning
  • Canvas drag scrolling
  • XO 1.75 hard edge bezel?
  • Screen rotation much more common/frequent on tablet format HW
    • Landscape
    • Portrait
      • Better for long form reading/writing
      • Better use of space with on screen keyboard
  • Text selection touch features
    • Touch friendly handles for adjusting selection
    • Drag scrolling vs. text selection interaction
      • Double tap and drag to initiate selection?
      • Touch and hold, then drag to initiate selection?
    • New pop-up palette?
      • Cut/copy/paste
      • Speak
      • Share with friend (would require a clipboard clipping share enhancement)
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Talk:Design_Team/Sugar_Shell_Touch_Input&oldid=82252"