Jump to content

Searchio! Auto-suggestion from search engines in different languages


Recommended Posts

Is there any way to make one of these searches the fallback search option in Alfred?

 

You could add any of the searches to the fallback search list (e.g. "Search Spanish Wikipedia for '<query>'"), but there's no way to get Alfred to call the search and show the returned suggestions in its fallback results.

Link to comment

Not until I've figured out if and how Alfred's killing scripts messes with Alfred-Workflow's caching code. I don't want the workflow generating loads of invalid query cache files because Alfred is killing the process in the middle of a cache write.

 

It's simple enough to wrap critical code so that signals are ignored till the code completes, but there's other stuff much higher up the TODO list.

Edited by deanishe
Link to comment
  • 4 months later...

Unfortunately, the Amazon sites all need to be hand-coded to get the right suggestions language, domain etc. I've added amazon.com.br in version 1.6.

 

Also added yandex.ru (Russian-language only).

 

Download from GitHub.

 

 

Now I have the same problem with eBay Search in Portuguese language. shop.ebay.pt domain does not exist.

Link to comment
On 6/23/2015 at 2:31 PM, deanishe said:

What is the domain for the Portuguese/Brazilian eBay?

 

I don't know if a Brazilian domain exists. If I browse ebay.com the website automatically detects my language and currency.

 

P.S.: I don't know if it's relevant but whether I enter ebay.com.br I am redirected to ebay.com.

Edited by xilopaint
Link to comment
On 6/24/2015 at 4:27 AM, deanishe said:

What happens when you use the workflow with ebay.com (i.e. in English)? Do you get English results or local ones?

 

If I change my system language to English I get results in Portuguese on ebay.com page also in Portuguese.

Edited by xilopaint
Link to comment

That's because the eBay API is returning results based on your location (IP address) regardless of your settings.

There's no need to change the system language. The whole point of this workflow is to enable you to use multiple languages at the same time. You just need to adjust the Script Filter to use a language other than your system one.

Adding --lang en to your eBay Script Filter should fix the issue.

Please see the documentation for details.

Edited by deanishe
Link to comment
  • 2 weeks later...

Thank you so much for making and sharing this. I love how versatile it is and seeing results in-line. Do you think it might be possible to add in the Google Play Store? More specifically, the App Store? Although, if possible, other people might like the ability to search through the others. Just a thought :)

 

Also, if you're feeling very generous and productive one day, I think it'd be awesome to have support for these sites as well:

Not expecting anything, just thought I'd throw my picks in here :)

Link to comment

Oh! How does one go about figuring that out? I have very limited knowledge in the field, so all that occurs to me when you say "suggestions API" is the feature, where a site comes up with suggestions, as you type. Like Wikipedia, and IMDb, as you mentioned. But I'm guessing there's something more to it, since Game of Thrones Wikia and A Wiki of Ice and Fire do give suggestions, when you search.

 

I'd want to know how to figure it out, so I don't make more suggestions, without checking if the sites are actual possibilities for you to implement.

Link to comment

Normally using Google. Search for "autosuggest API". Most of the current search engines were taken from Instantfox.

Both AWOIAF and Wikia are based on MediaWiki, so they have the necessary APIs.

I could see adding Wikia, but not most of the others.

I think the best solution would be to refactor the workflow to make user-defined engines possible (and easy).

Link to comment

Searchio is a really great workflow, but I wished you could force it to optionally search for the actual phrase you've entered (i.e., directly pass the entered terms to the appropriate search engine web page).

 

Most of the time, the suggested search results are very good, but I also regularly run into situations, where the suggested search terms differ from what I've actually entered. I noticed this especially with the Amazon search (and there especially with model numbers, which you often really don't want to get wrong if you are searching for a specific part), but it also happens to me with other engines such as DuckDuckGo (usually when you search for less common terms).

 

I tried defining Web Searches in Alfred with the same keywords as their counterparts in Searchio, so that I would always have a static "Search with Engine X" option among the results as a fallback. Unfortunately, that did not work very well either: Since I usually use the Searchio results, the Web Search entry is regularly pushed to the end of the list, so that I need to scroll down. Or worse: once in a while, the entry for the Web Search simply does not appear at all among the Searchio results.

 

In the 93% of situations where it works as expected, I'm absolutely thrilled to be able to use such a nice and sophisticated workflow that supports such a large number of search engines in such a convenient way. In 6% of the situations, however, I start to wonder if it would not be easier to just go back to the simple Web Searches that I used before I discovered Searchio. In the remaining 1% of situations, I do things like (unsuccessfully) looking into the Searchio code to see if I can easily make the necessary changes myself, or writing a very long forum post about it. ;)

 

After thinking a bit about this issue, I could imagine two ways how it could be addressed. The first option would be to implement that holding down a modifier key while hitting return would force Searchio to pass the entered search terms verbatim to the appropriate search engine. This would not visibly change how Searcho currently works, and instead just add additional functionality.

 

The second option would be to always include a static search for the entered search term as the first result that Searchio returns. The advantage of this approach would be that it would also address another issue: if you type really fast and hit return immediately afterwards, you often do a search for a pretty incorrect search phrase, because you hit return when the results list is still in the process of being built and sorted. The downside of this option would be that users who encounter neither issue (because they don't type too fast or don't often search for uncommon search terms) would always need to first hit arrow down once to get to the top search suggestion instead of being able to simply hit return. I guess injecting the static Web Search always as the second result could address this downside, if that were feasible.

 

For me personally, the second option would be the preferred solution, but the first option would also be a tremendous improvement.

 

Anyway, thank you very much for your time and attention, and, more importantly, for such a nice piece of software. :)

 

 

Link to comment

The default behaviour is to only show your query as a result if no other results are returned.

 

This can be altered, as detailed in the help file.

 

Enter searchio in Alfred (which will show the workflow's settings) and hit ENTER on the second item (Show query in results). That will always show your query as the top result.

 

Does that help?

Link to comment

That absolutely helps, thank you for the prompt reply.

 

While I do feel a bit stupid for not seeing that option myself, that feeling is overshadowed by the joy that the issue has already been solved without me knowing about it. :)

 

Again, thank you for all your great work!

Link to comment
  • 5 months later...
  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...