Support Forum

I am not a fan of "Move Up" / "Move to the top" positioning as it removes the finer precision that is currently there on large queues. It is a hard one to get right really. Okay. But then, may I suggest not actually filling the options for the drop-down boxes, before they are ac...

0.5 has support for gzip compression, which should give you faster page loads. How would zipping each page, on localhost, make the browser's generation of the DOM any faster? I start to receive the page after 70 milliseconds, and the browser finishes rendering it after ~ 5 seconds. Wouldn't gzippin...

With 150 entries, it takes 8 seconds to draw the table, because due to the design choice of giving the user the opportunity to move an entry to position X, and with having all options for entries filled in, 150 * 150 entries becomes 3 MiB. Without all the options, it's 150 KiB and takes 0.5 seconds ...

That's true; but delete is not the only action.

Say you can mark a number of entries, and then choose actions from a dropdown-box, such as "delete", "move to top", "move to bottom".

That'd be handy.

It's a bit of an improvement upon the old DOM-model, isn't it?

So especially, for the queue-view (and history), wouldn't it be an idea to consider using jQuery instead of the "refresh the entire page"-doctrine?

daniel_owen_uk wrote: I would say both, the ability to do select all, select none would be handy too.

Agree.
The way newzbin does it, with range and invert, is pretty handy.

Ok, so no reply so far. Maybe I threw too many ideas in there. Anyhow, looking at the 5.0 alpha 2, you've got: CREATE TABLE "history" (     "id" INTEGER PRIMARY KEY,     "completed" INTEGER NOT NULL,     "name" TEXT NOT NULL,     "nzb_name" TEXT NOT ...

Oh wow, I will definitiely look into this script.

I filed a Feature Request in relation to my idea for a similar script for music, here: http://forums.sabnzbd.org/index.php?topic=2019.0

With a preprocessing script, I could weed out both duplicate msgids from for example newzbin's RSS-feed for saved searches, and also previously downloaded msgids. To do this, I would need a database-backend, which I understand you will implement in 0.5.0 (sqlite3). I would use this primarily for dow...

Confirmed and closed.

Often a set of files in a download are quite ok, and one only need to check the first, smallest par to determine this.

It would be cool if we could avoid downloading pars 2 through 9999999999999.

Sometimes a newspost contains files where the download-parts are jumbled.
For example, part 10 comes after part 10000000000000000.

And it would be cool if we could download that before part 9999999999999999 without having to manually edit the nzb.