random thought of the day - a progress bar for tree transforms ?

[Robey Pointer]

On 14 Feb 2006, at 8:57, Aaron Bentley wrote:

> John A Meinel wrote:
>> I'm thinking that if it is a fixed number of iterations, just do the
>> progress as 14 steps, and skip ones you don't use.
>> But it might be nicer to have an idea how many files you are  
>> checking,
>> and iterate over that instead.
>
> On the plus side, we all seem to agree that nested progress bars would
> be nice.  On the minus side, no one's actually done it yet...

I played with nested progress bars this morning, but didn't like the  
way they looked.  My kinda half-baked idea was that child progress  
bars would just operate a spinner inside the parent, like this:

[=====/          ] copy  109/8743

Subdividing the parent would be useless, since in my experience, the  
parent is usually iterating over thousands of items.  But the spinner  
coming and going just looked confusing.  Anyone got better ideas?

robey