Tue Feb 28, 2012 3:42 pm
Probably the most common progress indicator is the file download bar found in Web browsers. Download time should be easy to predict: All a computer needs to do is divide the total file size by the measure rate of download. But download speed is unpredictable, subject to the ebbs and flows of your connection, the busyness of the file's server, and the performance of your router.
The progress bar for an application installer, or setup file, is an order of magnitude more complicated than a download-progress bar. It must track hundreds of different operations, each of which is dependent on external factors such as computer speed, Internet connectivity, and user activity. Brad Myers, a professor at Carnegie Mellon's Human-Computer Interaction Institute, puts it thus: "There are many areas of computing where the system as a whole cannot predict how long [a task] will take, so progress bars don't move in a consistent way." Estimating how long it will take to install something as complex as a computer game borders on guesswork.
The result? App developers don't always bother to make their progress bars accurate. Instead, they use freely available off-the-shelf progress-bar code that tracks how many raw operations have been completed, granting no special weight to those that may take longer than others. In some situations, developers give up entirely on traditional, determinate progress bars, resorting to indeterminate progress bars, or throbbers, in user-interface parlance. These indicators look and move in ways that suggest progress—think spinning pinwheels—but really just repeat until the task is complete.
Tue Feb 28, 2012 3:59 pm
Tue Feb 28, 2012 4:15 pm
Tue Feb 28, 2012 4:22 pm
Senator Bedfellow wrote:It's the same principle that governs how time-outs work in basketball games. Each team is allotted 3 time-outs per half, until the last two minutes, when they are allotted 3,257 time-outs.
Tue Feb 28, 2012 4:25 pm
Tue Feb 28, 2012 4:26 pm
SeanF wrote:Stealing somebody's joke - what it would be like if your GPS operated like a computer progress bar.
"You will arrive at your destination in 15 minutes...300 years...2 seconds."
Tue Feb 28, 2012 4:31 pm
merriam-webster.com wrote:2
: something that obstructs or prevents passage, progress, or action
Tue Feb 28, 2012 4:49 pm
Tue Feb 28, 2012 5:45 pm
jlogajan wrote:Actually it's hard to achieve GPS unit estimated arrival times without breaking the speed limit, at least on my Garmin Nuvi.
Tue Feb 28, 2012 6:44 pm
jlogajan wrote:Actually it's hard to achieve GPS unit estimated arrival times without breaking the speed limit, at least on my Garmin Nuvi.
Tue Feb 28, 2012 6:54 pm
Tue Feb 28, 2012 7:25 pm
Gumlegs wrote:Senator Bedfellow wrote:It's the same principle that governs how time-outs work in basketball games. Each team is allotted 3 time-outs per half, until the last two minutes, when they are allotted 3,257 time-outs.
Hmmm. I stay as far from basketball as I can. Perhaps you've uncovered one of the reasons.
Tue Feb 28, 2012 7:39 pm
Tue Feb 28, 2012 11:50 pm
Caramelgal wrote:Good thing they raised all that extra $ for new servers.![]()
Wed Feb 29, 2012 12:26 am
SeanF wrote:Stealing somebody's joke - what it would be like if your GPS operated like a computer progress bar.
"You will arrive at your destination in 15 minutes...300 years...2 seconds."
Wed Feb 29, 2012 12:32 am
Wed Feb 29, 2012 1:07 am
Central Archivist wrote:Gumlegs wrote:Senator Bedfellow wrote:It's the same principle that governs how time-outs work in basketball games. Each team is allotted 3 time-outs per half, until the last two minutes, when they are allotted 3,257 time-outs.
Hmmm. I stay as far from basketball as I can. Perhaps you've uncovered one of the reasons.
That and ...
1) Double dribbling
2) Traveling
3) Shooting or passing without first dribbling
No wonder the players act like thugs. There are no rules left in the game.