Firefox:Download Manager:Scratch Pad: Difference between revisions

Comment: Suggestions for Download Manager Improvements
No edit summary
(Comment: Suggestions for Download Manager Improvements)
Line 6: Line 6:


One more important thing: Do NOT restart the download of a currently downloading entry if the user clicks a link and saves it _again_. For example, start downloading file A. Click on the link to download A again, save it, and your download will restart from 0%! This should be handled in a better way... (Maybe changing the target path of the currently downloading file?) --[[User:Caleb|Caleb]] 12:01, 6 Nov 2005 (PST)
One more important thing: Do NOT restart the download of a currently downloading entry if the user clicks a link and saves it _again_. For example, start downloading file A. Click on the link to download A again, save it, and your download will restart from 0%! This should be handled in a better way... (Maybe changing the target path of the currently downloading file?) --[[User:Caleb|Caleb]] 12:01, 6 Nov 2005 (PST)
=== Comments [[User:PGaries|Patrick Garies]] ===
Some features I think the download manager could use are:
* Allow the user to specify directories and criteria by which files should be put into these directories. For example, file of X type should go into X directory or files from X website should go in X directory. You could have options for either:
** automated download to the specified directory
** to have that directory be opened by default in the save file dialogue so that if there was an exception, the user could easily choose a different directory. This would be helpful to users that save a lot of files or have complex file organization systems
* Add a display for the entire source URL and entire destination directory; preferably they would be displayed in a manner that allowed copy and paste.
* Allow the download manager UI to be accessed via a tab instead of through a new window.
* Allow manual copy and pasting of URLs into the download manager. This allows users to download files that are normally viewed by the browser. Examples include files with the <tt>*.js</tt>, <tt>*.css</tt>, <tt>*.html</tt>, and <tt>*.txt</tt> extensions. It also allows  exception downloading of files that are normally set to be viewed by the browser through plug-ins without changing the actual download actions for the relevant file type. For example, I may normally want to render <tt>*.pdf</tt> or <tt>*.mid</tt> files in the browser but occassionally want to download them instead.
* Separate files that have been successfully downloaded into a separate area. This keeps the active download area clean and lessens the desire to want to constantly remove completed downloads to keep the download area clean since these have reserved a separate area; being able to go back and retrieve old download URLs or see what files have been downloaded can be quite useful but it's second to organization (for me anyway).
* Allow the user to set a maximum bandwidth consumption for downloads so the user can still browse on slower connections.
* Allowing the user to add a download progress meter or download speed meter (so they know how much bandwidth is being consumed) to the toolbar in the same manner as buttons and widgets could be helpful.
There's a whole bunch of extra stuff that could be added as well such as:
* anti-virus scanning (using existing AV software)
* <tt>*.zip</tt> integrity check (for file corruption)
* support for torrents
* acceleration
* mirror searches
* computer shut-down or disconnect on download completion
* download scheduling
* et cetera
Hope I did this right. First time posting here. ;)
2

edits