diff options
author | Andy Stadler <> | 2009-04-21 11:54:45 -0700 |
---|---|---|
committer | The Android Open Source Project <initial-contribution@android.com> | 2009-04-21 11:54:45 -0700 |
commit | 4c156ec6ec9adcb407189ee57e0c205039b60148 (patch) | |
tree | da258cba9482fab13b473082dda72bc52625a337 /core/java | |
parent | df2a463b01fe5222e377828225ca6710d5c14743 (diff) | |
download | frameworks_base-4c156ec6ec9adcb407189ee57e0c205039b60148.zip frameworks_base-4c156ec6ec9adcb407189ee57e0c205039b60148.tar.gz frameworks_base-4c156ec6ec9adcb407189ee57e0c205039b60148.tar.bz2 |
AI 147168: am: CL 147163 Copy documentation for the various search-by-voice flags that
were already listed in attrs.xml into SearchManager.java. Add
a (brief - no time for more) description about how to add search
by voice to apps.
JAVADOC ONLY - should be safe change for cupcake sdk.
Original author: stadler
Merged from: //branches/cupcake/...
Automated import of CL 147168
Diffstat (limited to 'core/java')
-rw-r--r-- | core/java/android/app/SearchManager.java | 82 |
1 files changed, 80 insertions, 2 deletions
diff --git a/core/java/android/app/SearchManager.java b/core/java/android/app/SearchManager.java index c1d66f4..ecdd3f8 100644 --- a/core/java/android/app/SearchManager.java +++ b/core/java/android/app/SearchManager.java @@ -807,7 +807,7 @@ import android.view.KeyEvent; * this way would be if you wish to partition it into separate sections with different search * behaviors; Otherwise this configuration is not recommended. * - * <p><b>Additional Metadata for search suggestions.</b> If you have defined a content provider + * <p><b>Additional metadata for search suggestions.</b> If you have defined a content provider * to generate search suggestions, you'll need to publish it to the system, and you'll need to * provide a bit of additional XML metadata in order to configure communications with it. * @@ -880,7 +880,7 @@ import android.view.KeyEvent; * </tbody> * </table> * - * <p><b>Additional Metadata for search action keys.</b> For each action key that you would like to + * <p><b>Additional metadata for search action keys.</b> For each action key that you would like to * define, you'll need to add an additional element defining that key, and using the attributes * discussed in <a href="#ActionKeys">Action Keys</a>. A simple example is shown here: * @@ -956,6 +956,84 @@ import android.view.KeyEvent; * </tbody> * </table> * + * <p><b>Additional metadata for enabling voice search.</b> To enable voice search for your + * activity, you can add fields to the metadata that enable and configure voice search. When + * enabled (and available on the device), a voice search button will be displayed in the + * Search UI. Clicking this button will launch a voice search activity. When the user has + * finished speaking, the voice search phrase will be transcribed into text and presented to the + * searchable activity as if it were a typed query. + * + * <p>Elements of search metadata that support voice search: + * <table border="2" width="85%" align="center" frame="hsides" rules="rows"> + * + * <thead> + * <tr><th>Attribute</th> <th>Description</th> <th>Required?</th></tr> + * </thead> + * + * <tr><th>android:voiceSearchMode</th> + * <td>If provided and non-zero, enables voice search. (Voice search may not be + * provided by the device, in which case these flags will have no effect.) The + * following mode bits are defined: + * <table border="2" align="center" frame="hsides" rules="rows"> + * <tbody> + * <tr><th>showVoiceSearchButton</th> + * <td>If set, display a voice search button. This only takes effect if voice + * search is available on the device. If set, then launchWebSearch or + * launchRecognizer must also be set.</td> + * </tr> + * <tr><th>launchWebSearch</th> + * <td>If set, the voice search button will take the user directly to a + * built-in voice web search activity. Most applications will not use this + * flag, as it will take the user away from the activity in which search + * was invoked.</td> + * </tr> + * <tr><th>launchRecognizer</th> + * <td>If set, the voice search button will take the user directly to a + * built-in voice recording activity. This activity will prompt the user + * to speak, transcribe the spoken text, and forward the resulting query + * text to the searchable activity, just as if the user had typed it into + * the search UI and clicked the search button.</td> + * </tr> + * </tbody> + * </table></td> + * <td align="center">No</td> + * </tr> + * + * <tr><th>android:voiceLanguageModel</th> + * <td>If provided, this specifies the language model that should be used by the voice + * recognition system. + * See {@link android.speech.RecognizerIntent#EXTRA_LANGUAGE_MODEL} + * for more information. If not provided, the default value + * {@link android.speech.RecognizerIntent#LANGUAGE_MODEL_FREE_FORM} will be used.</td> + * <td align="center">No</td> + * </tr> + * + * <tr><th>android:voicePromptText</th> + * <td>If provided, this specifies a prompt that will be displayed during voice input. + * (If not provided, a default prompt will be displayed.)</td> + * <td align="center">No</td> + * </tr> + * + * <tr><th>android:voiceLanguage</th> + * <td>If provided, this specifies the spoken language to be expected. This is only + * needed if it is different from the current value of + * {@link java.util.Locale#getDefault()}. + * </td> + * <td align="center">No</td> + * </tr> + * + * <tr><th>android:voiceMaxResults</th> + * <td>If provided, enforces the maximum number of results to return, including the "best" + * result which will always be provided as the SEARCH intent's primary query. Must be + * one or greater. Use {@link android.speech.RecognizerIntent#EXTRA_RESULTS} + * to get the results from the intent. If not provided, the recognizer will choose + * how many results to return.</td> + * <td align="center">No</td> + * </tr> + * + * </tbody> + * </table> + * * <a name="PassingSearchContext"></a> * <h3>Passing Search Context</h3> * |