-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
various suggestions #39
Comments
Great suggestions! Since it was basically designed for me to use, all of the features are designed around how I use it. It's great to have feedback for more complex cases. I don't actually use multiple profiles often, so thank you for the report. Your first suggestion is definitely a bug, so that needs to be fixed. I am planing a fairly extensive code refactor coming up that would be a good opportunity to add some of these features that will require a change to underlying data structures (moving things per-profile). I suppose it's possible that just about everything could be made profile-specific. The colors are baked-in icons, so their use is limited to just what I package with the addon. Right now I just have grey, green, and orange, so it may be too limited to set per-profile, but what I could do is use green for NZBGet active profile and orange for SAB active profile? That's kind of what I had planned anyway. I can always add more images, but if I add 4 colors, then there's a chance someone will have a case where they need 5. I could add a badge showing the number of active downloads or a letter or two code for the active profile. I could also add a pop-over display element to supported one-click sites, just shooting from the hip. Notifications are half-implemented now. I have the base code and permissions for them, but what I had originally wanted - to notify on add, complete, and error states - was only possible if I also was doing some state bookkeeping on what was being downloaded, so I kind of abandoned it. If you think it'd be useful, I can add it with options for which to show. Of course, on a successful add, I could also change the color, badge, or the embedded icon on the site. The profile for omgwtfnzbs already does this, for instance. Adding paused is simple enough. I had planned to eventually add pause and go per-nzb at some point, but I tend to put things off until they are asked for. You can kind of do this now by pausing the server and adding, but that will pause anything in progress too. If you are using chrome, I can add you as a tester. I'm very happy to have help testing. |
HI @clutterskull
I am getting more and more familiar with Nzbunity and I now use it on a daily baisis.
As said before, a possibility to send and choose the server and label from the right click would be more appropriate but the way you designed you extension is very useful anyway.
I got a couple of suggestions/comments if you are opened to it.
First, from the popup, when we change the active profile, it doesn't change in the UI; You have to do it twice so that the UI changes.
In the settings, would it be possible to move the default category to the profile settings.
I have 2 servers, and the categories or the folder I want the downloads to go to, are different.
About the color change of the extension, that's the perfect use when you only have one server and it displays if it is downloading or not. When you have multiple servers, a better usage of the color change would be to display which server Nzbunity will send the nzb to.
Similarly, it is good to have notifications to quickly see whether it was successfully sent or not. Would it be possible to shorten the test so that it displays the profile, and the label? Just to make sure the nzb goes to the right place.
Finally, I'd like to be able to add nzbs as paused.
Ideally, it would be nice to have a default behouviour depending for each profile.
Also, it would be nice to overwrite the default behaviour in the popup
Thanks for reading down to here anyway.
I can't help as I don't code (sadly).
I am happy to beta test at least, if you need.
Nicoleoca
The text was updated successfully, but these errors were encountered: