I don't think there is one, and here's my reasoning:
When you specify a web page to download, wget has no idea how big that web page is or how large the constituent components are. For it to have an overall progress bar like you describe, then it would need to query for the size of each component, calculate the total, and then turn around and start downloading them. It seems a bit inefficient (by creating excess net traffic) to make a connection, see how big the object is, close the connection, reconnect, download the file, and disconnect.
I hope that's clear. There may be other reasons why, but I think it's primarily an efficiency decision.
|