Kiss: More support for different search engines

[ZerataX]

I would love to use https://searx.me as a search engine, but ideally you could just enter
https://searx.me/q=%s
where the search term is _%s_

[EnricoMonese]

Search engines can be added by adding their search url here
As for adding more search providers, they could simply be added there but at some point the list may get really long. But letting users add their own would also be kind of weird because they would have to also put in the search url. And probably less tech savy users don't even know what such a thing is

[saveman71]

Some people might argue that this launcher is for tech savvy users. Maybe we can introduce some kind of "I'm a tech savvy guy, show me more options" checkbox or something like that?

[ZerataX]

Or maybe something like the Lightning browser does:

This way there are still predefined search engines, so anybody not too tech savvy could still just use one of these, but for those that want more, it's hidden behind the custom option, not complicating the normal selection.

[Neamar]

Agreed.

Also, if we do it this way, we can remove the non-obvious search providers: I'd only keep Google, Bing and DDG. Everything else can be manually added

[Nemris]

Agreed. KISS, coupled with DDG's bangs feature, will be extremely powerful.

[EnricoMonese]

I was thinking about having a json file online from which the app would get the correct search URL for the engine that the user typed in. But that may get a bit large in terms of apk size. Maybe it's enough having a page in the documentation with a table of search engines and their urls and a link in the app to that page.
Something like this, from which the user would then copy the url and paste it in the app

| Name | Search URL |
|----------|--------|
| Google | https://encrypted.google.com/search?q= |
| DuckDuckGo | https://duckduckgo.com/?q= |
| ... | .... |

[Neamar]

KISS has no internet access (no permission for Internet), and I'd like to
keep it this way :)

On Mon, Dec 5, 2016 at 12:59 PM Enrico Monese [e-mail]
wrote:

I was thinking about having a json file online from which the app would
get the correct search URL for the engine that the user typed in. But that
may get a bit large in terms of apk size. Maybe it's enough having a page
in the documentation with a table of search engines and their urls and a
link in the app to that page.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Neamar/KISS/issues/553#issuecomment-264848047, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgxDF6ToDkIHnHZeuF9Vy-0rxKVM3Nwks5rFArOgaJpZM4K9BL9
.

[EnricoMonese]

Well what I though of would have needed a GET request, a JSON parser and some search to find the input in the json object. Even if there was internet access I don't think it would have been a good idea anyway.
What about the second idea? Opening links doesn't need permissions, I think (?)

[ntninja]

I have a different idea to contribute:
How about we register a new file type (say .kiss-addon) in Android that can then contain search engine information (and potentially also other stuff that we don't want to ship out-of-the-box in KISS) and offer several of those for download on the website. The search engine overview would then just contain an Add…-button that would take the user to the website.
Neither of this requires any permissions.

[EnricoMonese]

I also already though of something like that, but as I'm still a bit new to java I assumed it would have been too complicated. Anyway +1 from me

[Neamar]

Why not, sounds interesting. Happy to get this is if it's not too big.

On Mon, Dec 5, 2016 at 3:44 PM Enrico Monese [e-mail]
wrote:

I also already though of something like that, but as I'm still a bit new
to java I assumed it would have been too complicated. Anyway +1 from me

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Neamar/KISS/issues/553#issuecomment-264888141, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgxDMY0H-8JsKSMHJnBY30BG2XND4zGks5rFDFhgaJpZM4K9BL9
.

[saveman71]

I was thinking about a plugin architecture. I think it's possible to realize, what I have in mind is the same way tasker handles it. Plugins could be providers, with a configuration button that would take the user to their own activity. There, the plugin does absolutely everything it wants, internet access, add search engines to it own list, etc, etc.

I think it would allow KISS to go much farther because every user could search for a plugin that does what he wants or develop it himself, without diverging from the main repository.

Just my two cents ;)

[Nemris]

Makes me think about how Xposed handles its modules. Well, I was starting to think that we were going too far from the "Keep It Stupid Simple" paradigm, actually. Providing a base KISS which will only act as an app launcher, and then developing a series of modules for other features would be a huge improvement.

Kudos for the idea, even if I guess it would require a big rewrite of the app.

[Neamar]

+1 to that. Not sure how plug-ins works on Android however!

On Wed, Dec 7, 2016, 11:08 Death Mask Salesman [e-mail]
wrote:

Makes me think about how Xposed handles its modules. Well, I was starting
to think that we were going too far from the "Keep It Stupid Simple"
paradigm, actually. Providing a base KISS which will only act as an app
launcher, and then developing a series of modules for other features would
be a huge improvement.

Kudos for the idea, even if I guess it would require a big rewrite of the
app.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Neamar/KISS/issues/553#issuecomment-265420138, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgxDBl0_Y_jqNbrk7D13JfEsIp-LEtEks5rFpOygaJpZM4K9BL9
.

[saveman71]

Not sure as well, but I would be interested in working on it! I'm not sure
how we would discuss the implementation, though. IMO this is a thing that
that should be thoroughly discussed before any work is done to avoid
expensive refactoring and too much back and forth discussion if that makes
sense.

My guess is that plugins would be intent based? If that's the case it might
be a little slow for us...

[Neamar]

This has landed in beta.