On 1 June 2012 22:29, Esteban A. Maringolo <[email protected]> wrote: > You're right. But let's be real, how many progress-bar related actions do you > perform on a hourly based? > > I've been programming daily in smalltalk for the last 7+ years, and most of > the times progress bars show up when: > - Performing a long/deep search in the image (which I have to wait until it > finishes) > - Serializing a big object (+20s must be a BIG/heavy object graph) > - Deploying (nothing else should be done before it finishes) > - Downloading from a repository. > > And I don't do that more than once per day, if much. > > All the other progress bars are "app related" (like querying the database, > or similar). > > I can't figure more regular use cases of progress bar usage. > Igor have one, Chris has another. I added my two cents. :) >
Yes, i am talking about tasks, which we perform on a regular basis: - read file(s) from web/OS/whatever - compiling & installing new code etc irregular ones (like using a render farm to render special effects for new Holywood blockbuster) is out of scope. > The only one that could be sent to be background is when > uploading/downloading from a repository, and that's because most of the > times it is slow, even in comparison with other package management tools > (such as apt-get, npm, etc.), which in turn mode you in while working. > > Regards! > > > > > > > -- > View this message in context: > http://forum.world.st/What-i-would-like-to-have-instead-of-progress-bar-tp4632707p4632837.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.
