Speech Input: General Implementation + Find Feature Completed #1346
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds general HTML5 speech input capability to ChronoZoom for browsers that are capable. Is safely ignored by browsers that are not capable. Also has option to enable/disable speech input in web config. Please note that this version defaults to disabled state in web.config for now since:
If you'd like to enable this on your personal copy of CZ to experiment (or demo) then this line should be added to your web.config:
Uses general HTML5 speech input capability to drive verbal searches of ChronoZoom (fully implemented) using the find verb in the format "find *". For example, from the home page of CZ (anon user) you can say "find fish" and the view will switch to the canvas of timelines and the first timeline/exhibit/content item with "fish" in it will be located and you'll be navigated to that item. You can then search for something else such as "find humanity", "find Roman history" or "find cosmos". If an item can't be found, e.g. "find manatees" then you're told "Unable to find manatees".
Including now so work is not lost for potential future use. There was a discussion about possible finishing up a verbal tour navigation feature. The next item/previous item verbage for tours is already captured and passed to the appropriate empty functions (stubbed.) All that would be required would be to add code to make sure that a tour window was up and if so, fire the next or previous buttons. This is quite trivial to implement.