Front end engineering for searchable NZB queue!

[jm3]

I've been trying to add a search box to the queue in Plush,
like the History has. I haven't succeeded...

OK, I implemented the front-end UI changes to make the queue searchable! 🔍 Search box adjusts as the window resizes and matches the history search UI.

@shypike, you'll need to tweak _api_queue to accept a search string filter param like _api_history, but i'm hoping that's easy for you now that the UI work's done (easy for me).

Changes tested in Chrome, Firefox, and Safari. Please LMK if there's an official SABnzbd browser suite that changes get tested against.

[shypike]

Nice work! I have the matching Python code ready.
Just a few more requests/remarks.

When updating the "Search" box, the actual content of the queue only changes at the next refresh.
For people who use a slow refresh rate, this looks very confusing.
Is it possible to force a refresh of the queue when the return key is hit?
(This already works so for History Search.)

In History, the Purge command also uses the current "Search" field.
Can you pass the current queue "search" value as a parameter to the Queue Purge command as well?
(Queue Purge is the pull down menu at the right top side of the queue.)

I see you duplicated the $.plush.RefreshQueue() code in Plush.js.
That looks a bit awkward in the diffs. Can you remove the original procedure?

[shypike]

BTW: I have pushed the Python code, so it should be easier for you to test.

[jm3]

Is it possible to force a refresh of the queue when the return key is hit?

No problem, this and the Queue Purge param are both now complete in 6749202.
Also removed the duplicated RefreshQueue() stuff; still learning the codebase... 🐣

BTW: I have pushed the Python code, so it should be easier for you to test.

Thanks! It's working great. Excited to have this!

[shypike]

Good job, works as intended.
One final question. Can you rebase your branch to "develop"?
That way the git log looks cleaner.
I can use a patch of course, but I want to preserve your name in the log.

[jm3]

sure. do you want me to also rebase both dbe5700 and 6749202 into one commit?

[shypike]

Please do, nice to have it in one change-set.

[jm3]

OK, 200c3d8 is now one clean commit, and I rebased to develop!

[shypike]

Thank you for a very useful contribution.