2
edits
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
* 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. | * 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 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 | * 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 occasionally 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). | * 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. | * Allow the user to set a maximum bandwidth consumption for downloads so the user can still browse on slower connections. | ||
| Line 60: | Line 60: | ||
* '''Download helper:''' a couple of options for using a download helper can be added to about:config (enable/disable, location of exe file, and method of passing the url parameter) so people can add a third option to downloading files dialog that uses their favorite download tool. | * '''Download helper:''' a couple of options for using a download helper can be added to about:config (enable/disable, location of exe file, and method of passing the url parameter) so people can add a third option to downloading files dialog that uses their favorite download tool. | ||
=== Comment [[User:Nontitle|Nontitle]] === | |||
I have read through these suggestions, and it seems that most of these can be achieved through firefox add-ons. We should probably leave the more advanced features to add-ons and add only the simpler ones. For example, the "Download URL" suggested by Patrick sounds like something that should be added, as it would be quite simple in nature to insert. Also, I think adding in the shutdown after download option should be left to an add-on, because not all operating systems shut down the same way. | |||
edits