dojo ui help

[Daphne Ogle]

I looked around in the help docs of some of the applications on my  
computer and am not finding a direct reference for this kind of  
interaction.

I do think 'selected' semantically works well for the menu items  
leading up to the final highlighted hover (argh -- how do you talk  
about semantics without using them :)).  The user has really selected  
each one in order to get to the next fly out (or whatever menu type  
is used).  I also think it's OK to refer to different kinds of  
objects being selected (alignment button and text items in a menu).   
The difficulty seems to be in differentiating between the way these 2  
kinds of selections might be visually treated.  Or I may be missing  
something here.  Perhaps there isn't a one word answer -- How about  
something along the lines of:   Menu items are highlighted when  
selected and Buttons are depressed when selected?

A card sorting activity with users (of the document being created)  
could be really useful here.  Taking standard semantic language into  
account if it exists is of course still very important but the card  
sorting would help in understanding how your users think about these  
activities and states.

-Daphne

On Jul 10, 2007, at 8:17 PM, David Bolter wrote:

> Colin,
>
> Thanks for your reply, it was right on topic, and thanks for checking
> the Apple docs. This is a bit of a mucky one I think.
>
> I've spent a bit of time away from dojo and am not sure but I think  
> Bill
> is struggling with how to capture the semantics of highlighted in
> perhaps a style-agnostic term. It might be futile :)
>
> I've seen, and experienced first hand, confusion over the various  
> states
> that different toolkits have... stuff like armed, active, selected,
> checked, enabled, pressed, on...
>
> The aria state documentation is quite descriptive... but I'm not  
> seeing
> anything that fits say a highlighted parent menu item. I'm not sure a
> semantically meaningful term for this is a good idea or not... but  
> worth
> exploring. If a menu-item is selected/armed/active/highlighted we  
> might
> contort our minds to think of that as a temporary live region and the
> related parent menu item as 'relevant' but I really don't want to  
> go there.
>
> I think *maybe* menu items that open submenus should have a selected
> state if a user has selected them. Tomorrow I may disagree with  
> myself.
> It does seem to diverge a bit from the typical use of the selected  
> state.
>
> cheers,
> D
>
> Colin Clark wrote:
>> Hi David,
>>
>> So, in this case, the thing you're suggested Fluid can help with is
>> Bill's question about what highlight/hover state should be called? Or
>> am I confused?
>>
>> I did a quick read through the Apple Human Interface Guidelines, just
>> as an example of where this terminology might be mentioned, and  
>> didn't
>> find any reference to it.
>>
>> How about calling it "highlighted"? :)
>>
>> Does anyone else know if there is established terminology for this
>> behaviour menus?
>>
>> Colin
>>
>> David Bolter wrote:
>>> This is an example of the kind of thing I hope the FLUID ui gurus  
>>> can
>>> help with if possible:
>>>
>>> http://dojotoolkit.org/forum/developer-forums/dijit-development/ 
>>> toolbars-menus-and-selection
>>>
>>>
>>> I understand it may be too early to commit to a toolkit; and to
>>> commit resources to a toolkit.
>>>
>>> cheers,
>>> D
>>> _______________________________________________
>>> fluid-work mailing list
>>> fluid-work at fluidproject.org
>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>
>
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
cell (510)847-0308



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20070711/a756c4ca/attachment.htm>