Improve Search #15406

New issue

Open

opened 2026-02-22 02:06:08 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 02:06:08 -05:00

Owner

Originally created by @Chaython on GitHub (Jan 21, 2024).

Suggestion

Instead of bringing up another prompt, to submit new plugins, why not just have a textbox entry on the search engine list?

Current list

Install new one brings up another prompt: local or weblink, weblink further changes the prompt to a text entry.

I propose, you can put a file picker, and text entry in the list.
Either, an empty entry or in the header...

Use case

Just makes it a little less cumbersome

Extra info/examples/attachments

Improve Search #258

Originally created by @Chaython on GitHub (Jan 21, 2024). ### Suggestion Instead of bringing up another prompt, to submit new plugins, why not just have a textbox entry on the search engine list? Current list ![image](https://github.com/qbittorrent/search-plugins/assets/6486343/b69dabf8-6525-4538-b9e8-716e2c95d0e4) Install new one brings up another prompt: local or weblink, weblink further changes the prompt to a text entry. ![image](https://github.com/qbittorrent/search-plugins/assets/6486343/c316261c-9740-4948-b70c-d97e9be63619) I propose, you can put a file picker, and text entry in the list. Either, an empty entry or in the header... ### Use case Just makes it a little less cumbersome ### Extra info/examples/attachments [Improve Search #258 ](https://github.com/qbittorrent/search-plugins/issues/258)

deekerman added the

Feature request

Search engine

labels

2026-02-22 02:06:08 -05:00

deekerman commented

2026-02-22 02:06:12 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**