The next option is a search on StackOverflow with the tag, followed by a Google search. You can download the extension - the keyword for this extension is extdocs, so type that followed by your search query - and see that the default suggestion is to search on the Opera Extensions documentation site. Var qString = '' + encodeURIComponent(text) so we will have to append a URL to it again. (thus not having an 'http' at the beginning of the string), which will result in the text not being converted to a URL User selects the suggested suggestion, If not, we will convert it to a proper URL, and point the user to the appropriate page, like so:Ĭ( So we will process the entered text at the point when the user has finally hit enter in the address bar, and see if it’s a proper URL or not. One thing to keep in mind is that when the user selects the default suggestion, it will by default not have a URL attached to it. because we used `setDefaultSuggestion`, First suggestion is already shown by default 'description': 'Do a Stack Overflow Search' 'description': 'Search Opera Extensions Documentation' 'content': '' + encodeURIComponent(text), The background page for our extensions would like so:Ĭ(
In the API, we have access to event handlers dealing with various stages of the user entering content (for example, when the user has started entering text, when the user has finished typing, when the text has changed, when the text entered is accepted, etc.)įor our example, we will use the onInputEntered event handler to take the user’s input and take the user to the search page. So let’s make an extension which takes the text and searches this site for content. One of the most common use cases for the chrome.omnibox API would be to take the text and search a certain website with it. Great! Now let’s go on and actually process the text to do something useful. We have used the manifest to define the keyword we’ll use. In the icons field, we specify what icon comes up in the address bar when your keyword is entered. In our case, we are using the keyword extdocs - so whenever the user enters extdocs, the extension kicks in, ready to process whatever text comes next. Inside this field, you need to define your keyword inside the keyword subfield. As you can note from the example, you need to use the omnibox field.
0 kommentar(er)
