You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2019. It is now read-only.
These directives to be enhanced with an attribute that enables speed-dial. Speed-dial displays a list of entries underneath the input box. These correspond to entries which have been selected already in some context. We assume they are a narrow superset of all the entries which continue to be accessible via the autocomplete method.
There are two broad uses for speed-dial. The first is in enabling rapid specification of common metadata. For example, when adding an a recording and specifying a language, the user has only ever specified a few languages, display them for clicking rather than rely on keyboard entry.
The second is in annotation region specific metadata where the user may optionally add speaker turns, tags and even languages (rarely, probably) to annotation regions.
Because of these two use cases, we will need to pass in the speed dial values via a speed-dial attribute. For the annotation UI, this data would come from the function defined in #118 and the model will need to be attached to the specific metadata of an annotation, for example: sessionObj.segment.metadata.language[annotationIndex]
These directives to be enhanced with an attribute that enables speed-dial. Speed-dial displays a list of entries underneath the input box. These correspond to entries which have been selected already in some context. We assume they are a narrow superset of all the entries which continue to be accessible via the autocomplete method.
There are two broad uses for speed-dial. The first is in enabling rapid specification of common metadata. For example, when adding an a recording and specifying a language, the user has only ever specified a few languages, display them for clicking rather than rely on keyboard entry.
The second is in annotation region specific metadata where the user may optionally add speaker turns, tags and even languages (rarely, probably) to annotation regions.
Because of these two use cases, we will need to pass in the speed dial values via a speed-dial attribute. For the annotation UI, this data would come from the function defined in #118 and the model will need to be attached to the specific metadata of an annotation, for example: sessionObj.segment.metadata.language[annotationIndex]