https://docs.google.com/document/d/1ouVFq4w-i0rchNHtTAG_JoRwHfYm9mN2MkxFBct1JSI/edit
Custom Interactions
https://docs.google.com/document/d/13QWLthBoEU6xuJQ4UrYOwuvJp0a42Z70JRjAsjtv1m4/edit?usp=sharing
Kim: good to have examples when we are talking about it
Jake: hard to draw the line –
what are custom gestures. Also placement and timing
... custom gestures – two different kinds of gestures, Drag and
one with the intermediate point. If we plot that to what we
want to solve and we don't want to make it too complicated by
saying you need to know all your gestures – Apple iOS android
and whatever. Or even the question about why area. If we
approach it from another angle and say that If you use a
standard gesture or key or interaction – when you use a regular
swipe left, etc.
If there are more possibilities than just the one regular swipe left, other types of swipes left, you have to provide help
Jake: so we want to cover the ones where there are more than one left swipes available, or more than one gestures or keys that work together, like going left and going up instead of only left or only up for only double tap. So the moment it gets complicated by combining two, and it doesn't matter if it's too gestures combining three or four or two actions beneath the gesture or three or four, at that moment you have to provide help
https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6?usp=sharing
RESOURCE FROM jAKE https://drive.google.com/drive/folders/1Q9md2AvmeTgvsT9GB62BsGvCaalDGtE6
Jake: we could create a standard
list – Example above page 5, 6, etc. If it's a standard
gesture
... good, but if you have to combine or if there's not a clue –
feedback for what happened, you need to explain
... these are the gestures, if there is no official hand like
an arrow right or down and suddenly there's an action beneath
it then you need to explain it. If there's more than one action
then you still need to explain it because there are more then
one actions possible, and if it's combining gestures you also
need to provide help. And this is the list of gestures, list of
default keystrokes etc.
... so combining two keys makes it custom as well
... if we go directly to why area and the question – are those
custom interactions if they just work in the same way with the
default arrow and you don't have to combine them, no, but the
moment you have to hold one key together with another then yes
you have to provide help
... but I'd like to do with the keyboard is if you can interact
with the arrow and, fine, and Maybe the escape key, but
everything else is a custom one, including Key shortcuts, need
to be documented.
... so everything else has to be documented – so that seems
like an easy one
... so in that case it's about whether it works with the tab or
arrows in that case you're covered
... so it kicks in when you need to press two keys
... arrow, tab and one key combination to open an instruction
file
... I think we need to make a list of gestures. Single tap,
double tap, swipe four directions, flick– we need to agree on
the set as we did with input purpose
... and then combining any of them need help. And then If you
have a single gesture with Affordance – feedback, fine, but if
you have a single gesture without a clue of what will happen
you also need help.
example Netflix – if you only see two movies and you have no idea that there's a third if you swipe left right, you also need to provide something – feedback or instructions
Kim: feedback is instruction – this is a good way to put it
Jake: if you have feedback it's very clear, so you don't need instructions. The moment you don't make it very clear or start combining stuff or put More interactions beyond one simple gesture then you need to start expanding yourself – provide instructions Because there are too many unknowns
<scribe> ACTION: Jake to write up this point including suggested basic gesture and basic keys lists and add to the bottom of the custom interactions SC document for discussion next time.
<trackbot> Created ACTION-79 - Write up this point including suggested basic gesture and basic keys lists and add to the bottom of the custom interactions sc document for discussion next time. [on Jake Abma - due 2019-11-14].
It would also be good to find examples where feedback works well to make that point easy to picture
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Kim, Jake Present: Kim Jake WARNING: Fewer than 3 people found for Present list! No ScribeNick specified. Guessing ScribeNick: Kim Inferring Scribes: Kim WARNING: No "Topic:" lines found. Found Date: 07 Nov 2019 People with action items: jake WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]