[Bugs] #3706 design UNSP: Design impicaltions for onscreen keyboards (OSK)

[Sugar Labs Bugs]

#3706: Design impicaltions for onscreen keyboards (OSK)
------------------------------------------+---------------------------------
    Reporter:  cjl                        |          Owner:  garycmartin                
        Type:  task                       |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  design                     |        Version:  Unspecified                
    Severity:  Unspecified                |       Keywords:                             
Distribution:  Unspecified                |   Status_field:  Unconfirmed                
------------------------------------------+---------------------------------
 OLPC has expressed it's current preference for Maliit as the on-screen
 keyboard (OSK) for XO tablets and touch screen devices.

 http://lists.laptop.org/pipermail/devel/2012-May/035057.html

 This seems like a reasonable technical choice, but there are design
 implications of an OSK without regard to the underlying technology that
 need to be thought through.

 I raised some of this in the later discussion on #3698, but I think it
 deserves it's own long-term ticket with a focus on the design choices that
 may need to be made and investigated in the context of Maliit (in
 particular) to determine how OSK may introduce new design considerations
 for Sugar UI.


 Examples:

 1) How much screen real estate is needed for usable OSK.

 2) How well can this be made to mimic existing OLPC keyboard options and
 the special keys implemented there.

 3) Hardware keyboards often display multiple characters on a single key
 which are accessible by using key modifiers like alt-gr, how will this
 work with an OSK?

 4) Are keyboard shortcuts like Alt + some latin letter character truly
 feasible in Sugar activities if the OSK is not going to display the Latin
 character with the native script?

 5) OLPC is not the only touchscreen hardware we will want to support, how
 general a solution is Maliit going to be for Sugar?  This came up in the
 context fo recent list discussions about running on Sugar on iPad and
 iPhone platforms as just one alternate example.

 6) How can OSKs be made to serve vision-impaired users.

 7) Will there be haptic feedback capabilities?

 8) add your own question . . . .

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/3706>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system