Re: [WICD Core 1.0] 6.3.1 Focus Navigation

Hello Jeff,

section "6.3 Focus Navigation" in WICD Core is informative. The CDF  
group decided against mandating one particular method of focus  
navigation in WICD 1.0. We believe, that a handset devices, with a 4  
way joystick input device, should indeed implement a flat, two  
dimensional focus navigation (one that would not be based on a linear  
focus ring). We are trying to offer one possible solution in section  
6.3.1. This is a role model, which is based on an implementation of  
one particular vendor in the group.

However, the group came to the conclusion, that an informative  
section is the best we can do. Many in the group believe that UI is,  
at least in part, out of scope for WICD to specify in detail, and  
that implementors need some freedom in this area. I, personally,  
would have wished for a bit more. For handset devices, a more  
*predictable* focus navigation model would be worth a lot.

The WICD Mobile TestSuite will most likely contain the following test  
case:
http://www.w3.org/2004/CDF/Group/TestSuite/WICD_CDR_WP1/buttons/2d- 
nav.xhtml
(You have to make your desktop browser window really narrow for this  
to make sense.)

I hope this describes the situation and explains why the question you  
are bringing up are not fully answered in the document.

Kind regards,
Timur

On 30. Jan 2006, at 19:58, Jeff Schiller wrote:

>
> Sorry I believe I am one day late in my comments.  I hope they will
> still be considered.
>
> I had several questions on Section 6.3.1:
>
> 1) 6.3.1 - How do you determine the starting focus point (would it be
> the upper-left of Rejoice or the center)?  Why is the starting point
> at the bottom-left corner of the "R"?
>
> 2) 6.3.1 - In phase 1, "At first, focusable objects are searched from
> the direction of navigation.".  Please describe this search.  Is it a
> binary space search (i.e. if moving in +ve y-direction, is it EVERY
> focusable element that has any portion of itself with a y-coordinate
> greater than or equal to the y-coordinate of the current focus point)?
>
> 3) 6.3.1 - All focusable entities in your example seem to be
> symmetrical, are you considering arbitrarily shaped entities like many
> "skinned" applications provide these days?   What about "nested"
> entities?
>
> 4) 6.3.1 - does navigating the "focus point" put the focus point
> somewhere in the center of the entity or does it stop at the edge?
> Consider elements that are not necessarily symmetrical...
>
> 5) 6.3.1 - Consider http://www.codedread.com/images/gui.png.  For the
> example on the left, what about when there are two candidates that are
> equal in terms of distance function?  Which lower block does the UA
> choose?  Does it matter?  For the example on the right, if you start
> at one of the corner buttons, how do you ever navigate to the middle
> ring or smaller square?  Is 8-way navigation required?  NOTE that I
> don't necessarily expect you to solve all issues caused by
> inaccessible GUIs like those two examples, just want to ensure you are
> thinking of them.
>
> Thanks,
> Jeff Schiller
>

Received on Tuesday, 31 January 2006 22:11:02 UTC