Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upImplement download queueing #657
Comments
|
@nukeop I'd like to work on it. |
|
Ok, as this is a big feature, pick one of the things on the list first and let's iterate on it together. |
|
I'll start with |
|
I'm planning to store downloads as Plain array of download |
|
Ok, you can use |
it seems not possible to resume downloads over app restart, since we can also add pause and resume downloads feature which will resume downloads if possible or restarts(over app restarts) |
What we can do is store the status (completed/incomplete/error), and start over on restart, deleting the incomplete download first. |
|
should we auto start those downloads(Error/incomplete) or should we provide a resume retry icon so that user can retry them whenever he wants. |
|
Browsers wait for manual restart, so I think we should also follow that pattern. |
|
@nukeop I'm working on this |
|
Great, this will be a very useful next step. |
|
Hi, I would like to work on this with my partner @nfeygin if possible |
|
Ok, let me review this and I'll tell you what parts of this haven't been worked on yet. |
|
sure |
|
Hi nukeop, were you able to review the code? can you let me know asap so I can try working on this |
|
@nukeop can you also let me know how to open the app in developer mode |
|
Sorry, I forgot about this. The development process is explained here: https://github.com/nukeop/nuclear#development-process |
Currently, every track added to downloads immediately starts downloading. Downloads are therefore behaving inconsistently, are not saved over program restarts, and can fail randomly without properly notifying the user. The following improvements are proposed: