A painting of me

This is what happens when you let developers create a UI. ⇒

   29 November 2006, mid-afternoon

It's a GUI for the wget command. I would like to think I have more sense then this.

This is a post from my link log: If you click the title of this post you will be taken the web page I am discussing.

Perma-Link  

Comments

  1. That gui seems to be missing the options

    • to let you download from urls listed in a file (and force input to be treated as html, and prepend a url to all urls in the file)
    • adjust the timeouts for the process, connections, dns lookups, and file reads
    • wait x seconds between requests
    • force the use of a proxy or not
    • force ipv4 or ipv6
    • set a username/password for ftp gets
    • no host directories
    • add a download prefix
    • set an http user/pass
    • ignore content length header on responses
    • adjust the header of the request
    • set the http-referrer for the request
    • turn on and off persistent connections
    • use cookies
    • load cookies from a file
    • save cookeis to a file
    • send POST data
    • use HTTPS
    • all the ftp options
    • convert links for recursive retrieval
    • get page requites (though this might be the default for this gui)
    • follow relative links

    Though, one has to wonder why anybody would even need a gui for wget. You’re just taking a highly configurable tool and enumerating its options. Of course you’re going to get a mish mash soup of options on a big dialogue screen.

Don't be shy, you can comment too!

 
Some things to keep in mind: You can style comments using Textile. In particular, *text* will get turned into text and _text_ will get turned into text. You can post a link using the command "linktext":link, so something like "google":http://www.google.com will get turned in to google. I may erase off-topic comments, or edit poorly formatted comments; I do this very rarely.