Re: Use case for indie UI events - manipulating a map

Hi Rick,

This is great! Doug set up a WIKI for us to add use cases for the group to
review. I have begun adding them. At the moment I have not set a priority
on mine. The current set I have started on pertained to UI widget
components we would need for ARIA in order to replace the use of a
keyboard.

http://www.w3.org/WAI/IndieUI/wiki/Use_Cases_and_Requirements

Could you add these to the list? One of the things I have not fully stated
which you appear to need to do to is establish a point of regard and that
is done. For example Rotating an object assumes either focus on the object
or the object being grabbed. I have a similar issue with say a tree UI
control where the tree or item in the tree must either be touched by a user
or have keyboard focus in order to be expanded. In your rotation use case
we need to have the user pointing to the object in some way or it has to
have keyboard focus before it can be notified to rotate via a gesture, etc.

Establishing the point of regard or point of input is important.

Could you add these to the use cases?

Rich


Rich Schwerdtfeger



From:	Rick Byers <rbyers@google.com>
To:	public-indie-ui@w3.org,
Date:	06/18/2012 09:45 PM
Subject:	Use case for indie UI events - manipulating a map



One use case I'd really like to see the Indie UI spec handle is
manipulating a 2D (or 3D) object like a map (think http://maps.google.com).
In particular:
      Panning the object to a precise location
            With a mouse this is triggered by click and drag
            With a touch screen this is triggered by touch and drag
            With keyboard or some assistive technology this could be
            triggered by arrow keys moving the map a fixed distance
            Panning is continuous so there shouldn't be an edge (eg. some
            absolute co-ordinate after which it's impossible to pan)
       Zooming the object in and out around a specific point
            With a mouse this could be triggered by the mouse wheel with
            the origin at the mouse cursor
            With a touch screen this could be triggered by a pinch gesture
            (with the origin being the midpoint between the two touch
            points)
            With a keyboard this could be triggered in steps by specific
            standard keys
      Rotating the object
      Lower-priority but also interesting is manipulating the object in 3D
      along all the axis
Thanks,
   Rick