Difference between revisions of "Design Team/Activity Touch Input"

From Sugar Labs
Jump to navigation Jump to search
Line 114: Line 114:
 
* Default to large blocks when used on a touch device to reduce obscuring effect of fingers & improve hit target. Perhaps extend the block shapes to have an otherwise blank  'gripper/ridged' area to the left or right
 
* Default to large blocks when used on a touch device to reduce obscuring effect of fingers & improve hit target. Perhaps extend the block shapes to have an otherwise blank  'gripper/ridged' area to the left or right
 
:''What is the purpose of the gripper? --Walter'''
 
:''What is the purpose of the gripper? --Walter'''
::''To allow a fat finger to easily drag a block about without obscuring its content and top edge for snapping onto other blocks''
+
::''To allow a fat finger to easily drag a block about without obscuring its content and top edge for snapping onto other blocks --Gary''
 
:::''Got it. It could be something that only appears on a touch-enabled machine (or when the XO is in tablet mode). I'll sketch something up. --Walter''
 
:::''Got it. It could be something that only appears on a touch-enabled machine (or when the XO is in tablet mode). I'll sketch something up. --Walter''
 
* Portrait orientation clips too many toolbar icons (expect portrait orientation to be used much more frequently on tablet devices)
 
* Portrait orientation clips too many toolbar icons (expect portrait orientation to be used much more frequently on tablet devices)
Line 125: Line 125:
 
* Tapping a block tile or stack does not auto run it
 
* Tapping a block tile or stack does not auto run it
 
:''What is the difference between a tap and a click? (I added some code for XO3 to try to disambiguate between a tap and a small drag used in repositioning a block... may need revisiting) --Walter''
 
:''What is the difference between a tap and a click? (I added some code for XO3 to try to disambiguate between a tap and a small drag used in repositioning a block... may need revisiting) --Walter''
::Not sure from an implementation perspective, just an observation of the current behaviour in TA, I can click a block/stack to auto run, but a tap and release (many careful attempts) of the same block/stack had no effect.
+
::''Not sure from an implementation perspective, just an observation of the current behaviour in TA, I can click a block/stack to auto run, but a tap and release (many careful attempts) of the same block/stack had no effect. --Gary''
  
 
==Typing Turtle==
 
==Typing Turtle==

Revision as of 14:09, 18 April 2012

Abacus

  • Show live dragging feedback of abacus beads, not just updating the canvas when you release.
Yeah. Easy enough. I was just lazy. --Walter
  • For the custom abacus toolbar, spin button widgets are too fiddly to use due to the very small inc/dec arrows (should try to solve in system wide theme or depreciate use of this widget in activities)
Some of these could be replaced by stretching or squeezing different parts of the abacus frame: to add more rods, upper or lower beads. I think for the numeric values, such as base and multiplication factor, I'll need some big buttons. --Walter
  • Show abacus type name on the main canvas
Also easy enough... stay tuned. --Walter

Browse

Calculate

  • Prevent auto expose of on screen keyboard for calculation entry widget and rely on canvas and toolbar buttons
  • Manual reveal of keyboard for some more advanced actions
  • Cursor left/right canvas buttons
  • Backspace canvas button
  • Scientific vs. Basic canvas display toggle (not essential but would improve touch experience)
    • Major toolbar reword/reduction
    • Most functions get canvas buttons in scientific mode
  • New implementation of help

Chat

Clock

Distance

Etoys

Finance

FotoToon

  • Save as Image should raise a confirmation alert to provide user feedback that a Journal entry was created
  • Resize widgets for all bubbles need to be much larger and visible
  • Bubble arrow (for spike or thought target) marker needs to be much larger and more visible

Get Books

  • Combo box for selecting the archive source should fully open rather than making the user scroll navigate to see the three entries

HelloWorld

Help

Image Viewer

Implode

Infoslicer

Jukebox

Labyrinth

  • Canvas zooming in/out with pinch gesture
  • Canvas scrolling when dragging canvas (replace current behaviour of creating a node of a specific size, rely on single tap to create a node)

Log

  • Log Collector palette should open on single touch / left click (currently uses hover loiter only)
  • Log Collector needs a better icon, a bug with glasses or a magnifying glass?
  • Copy tool button should only be active if a text selection is made
  • Vertical view split needs larger hit target UI (system wide theme solution needed)
  • List disclosure triangles are too small, allow touching anywhere in directory name text to open/close the node (might need a system theme solution for tree view)

Maze

Measure

Memorize

Moon

Paint

Physics

Pippy

Portfolio

Read

  • Vertical scrolling solution
  • Page turning swipe gesture for paginatable documents

Record

Ruler

Scratch

Speak

StopWatch

No major touch changes required

TamTamEdit

TamTamJam

TamTamMini

TamTamSynthLab

Terminal

  • Add warning confirmation alert strip to 'Become root' button to provide feedback
  • Will require a close to full feature on screen keyboard with modifiers and unusual characters
  • Update tab design as per Browse to provide larger hit targets
  • Drag scrolling
  • More accurate text selection (system wide solution needed for touch)
  • Drag scrolling through console history

Turtle Art

  • Canvas zooming in/out with pinch gesture
Right now, there is no canvas zooming at all... just block zooming. --Walter
  • Canvas scrolling when dragging canvas
Will add to v138 (See commit at [1]). --Walter
  • Default to large blocks when used on a touch device to reduce obscuring effect of fingers & improve hit target. Perhaps extend the block shapes to have an otherwise blank 'gripper/ridged' area to the left or right
What is the purpose of the gripper? --Walter'
To allow a fat finger to easily drag a block about without obscuring its content and top edge for snapping onto other blocks --Gary
Got it. It could be something that only appears on a touch-enabled machine (or when the XO is in tablet mode). I'll sketch something up. --Walter
  • Portrait orientation clips too many toolbar icons (expect portrait orientation to be used much more frequently on tablet devices)
As of v137, there is a scroll mechanism for clipped palettes... --Walter
  • Toolbar hover hints clobbering view of block palettes (due to touch activation leaving pointer over toolbar buttons )
These can be turned off and could be by default. --Walter
  • Allow escaping from full screen mode (see Read for improved behaviour)
  • All Save as/Export options should raise a confirmation alert to provide user feedback of Journal entry creation.
Will add to v138 (See commit at [2]). --Walter
  • Tapping a block tile or stack does not auto run it
What is the difference between a tap and a click? (I added some code for XO3 to try to disambiguate between a tap and a small drag used in repositioning a block... may need revisiting) --Walter
Not sure from an implementation perspective, just an observation of the current behaviour in TA, I can click a block/stack to auto run, but a tap and release (many careful attempts) of the same block/stack had no effect. --Gary

Typing Turtle

WikipediaEN/ES

Words

Write