Showing posts with label visit. Show all posts
Showing posts with label visit. Show all posts

Wednesday, July 21, 2010

Things to explore with Jake

Our current plan is that Jake will spend about a day with the computer science sub-team, split into two half-day sessions.  We want to make as good use of that time as possible.  Here is my current list of things we should explore while he is with us:
  • Feature scale and map detail: 
    We should vary the scale and complexity of the map display, to get a better idea of the level of how dense and detailed the display can be.  Our initial belief is that neither fine detail nor a large number of details can be effectively displayed through sound, so we should start with a very sparse display and gradually increase its complexity.  May may do that simply by changing the zoom level.   This may not be enough to distinguish the problem of feature scale, such as the amount of buffering needed around a river to follow it, from density of features, such as the number of rivers shown on a map, but it will be a start. 
  • Device:
    Nafisa has reconfigured the tablet to be an absolute pointing device, rather than a relative pointing device.   We will try the mouse-like puck and then pen again on the Wacom Intuos tablet.  Although we believe the finger-tracking Bamboo tablet is too small for our purposes, we will experiment a bit more with that as well, and try to observe whether there is a real difference between using the pen and using the fingers.
  • Sound selection:
    We won't have spatialized audio to try in August, but there are still several aspects of the sound design that we should informally experiment with, such as how and when to use mimetic sounds such as the sound of water for a river, and when to use speech. 
  • Verbal descriptions:
    We should try providing spoken descriptions of the overall map and the interface.  I am not sure what we should vary, but we should at least give Jake a chance to interact with a map that provides some textual summary information, and get some feedback from him on what kind of overall map description is useful to him.  
  • Hard and soft buttons:
    Nafisa is currently trying to determine whether we can program our own button behavior in Java, or whether we are limited to using the button objects provided through the ESRI developer interfaces.  If possible, we should try corner-based pop-up menus similar to those in Matt's interface mock-up.  We should also try using the hardware buttons on the Wacom Intuos tablet.  I expect that corner-based menus will be the best placement if we need to use the tablet surface, but that the "hard" buttons on the tablet could be even better.  In both cases, what we are trying to do is minimize taking up space when the menus are not in use, and making it very easy to "find" the menus without much memory load or fine control.  With a mouse, a corner is an ideal target because one can "slam" the pointer into a corner by moving further in both the x and y direction than is really necessary ... it can be fast because it doesn't have to be accurate.  The same principle should apply in finding the corner, as long as we make the edges easy to feel, and perhaps provide a physical barrier for the pen.  The hardware buttons may not be quite as easy to find, but it should be possible to locate them by sweeping with the non-dominant hand while keeping the stylus in the dominant hand  (and similarly if the puck or finger-tracking is used).  
This is an initial list, to be refined ... please comment with improvements, things that are missing, potential problems with these topics, etc.