Hi, At some point, in addition to bringing up terminology issues with other developers, I’ll go over the user guide (for the umpteenth time) and bring up parts that could lead to misunderstandings like our discussion on gestures versus commands, inclusion of touch commands and so on (all via GitHub; this reminds me: I need to purchase an updated version of Basic Training module to see if it is simpler than user guide we have). Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Sunday, February 17, 2019 11:15 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION Hi I am guessing the touch commands are the etc in the input gestures section. it does not mention touch at all only keyboard and braille but should be updated to say also touch. Gene nz On 17/02/2019 11:42 PM, marcio via Groups.Io wrote: Actually, I always found it too strange that this option was called "gestures", simply because, for me, it means what it would mean out of the computer/programming world.
That is, a gesture is a gesture, isn't it? So I'm thinking, well here we should have the touch commands, why are the keyboard ones here as well?
And I'm into geeky stuff, sometimes dare myself programming some small things. I hope I'm not the only one geek with this understanding of things! Em 17/02/2019 06:37, Brian's Mail list account via Groups.Io escreveu: I think the issue though is when you see the word Gesture, you may not understand it as anything but a physical motion, ie making a rude sign or whatever, Its not universally known by this name for interaction with anything but touch sscreens based on my unscientific study of half a dozen blind computer users!
A headinglike keyboard, mouse and touch gestures for NVDA might explain it better.
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Ian Westerland" <iwesterl@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, February 16, 2019 11:54 AM
Subject: Re: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION
Another way around the issue might be to define what the word means in
context so "gesture" could be used within the contextual definition.
Just a thought.
Ian Westerland
On 2/16/2019 10:51 PM, Brian's Mail list account via Groups.Io wrote:
Yes we need a whole new word or phrase.
How about user input schemes or something like that?
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Richard Bartholomew" <rlbart53@...>
To: <nvda@nvda.groups.io>
Sent: Saturday, February 16, 2019 10:16 AM
Subject: [nvda] CLARITY OF TERMINOLOGY AND DOCUMENTATION
Hi,
The underlying explanation of what input gestures are is excellent and
understandable; however, for me, the issue isn't semantics per se but if the
top-level description isn't immediately obvious to the end-user, it has
failed in some way. In this case, the word gesture implies touch screens
and, so, discouraged me from finding the time to delve into an area which I
thought wasn't relevant to me. A personal failing I admit but we all have
demands upon our time so if we can weed out what we think are unnecessary
diversions, it's often the pragmatic way to go!
I accept that this whole area is a minefield as you can please some of the
people, some of the time, etc, etc, etc!
Good luck!
Richard Bartholomew
|
