> Committed in r1418 and 1419.
>
> For those that are watching, Martin meant to say he was
> tackling the Checkout option, not commit.
Ooops !
My fault, of course checkout ...
> Martin, a few questions:
>
> 1) Do we still need the old Run method signature at all?
No I don't think so.
I thought you would know. According to my knowledge we can remove it.
> 2) If not, then we can just change the signature, if we do
> then how about
> runWithMonitor() as the new method name instead of runDirectly()?
I agree.
> 3) I see the progress messages, but my percentage stays at
> 9% until the end. Do we have any options here? Ideally, we
> could show a moderately accurate percentage, or at least one
> that increments. If not, could we just ditch that all
> together and just have the progress messages? I think a
> percentage that isn't moving is not a good idea.
Well, we for sure can increase the progress bar.
The question I was not able to asnwer was, what is "moderately accurate".
We know when a resource was checked-out, but we do not know how many
resources there are ...
It seems that the existing progress works for two things:
- when you're checking out several resources within one command
- to show progress of each checkout in the sense of it's 3 phases -
scrubProject 9%, checkout 82%, refreshProject 9%.
I don't have a sound proposal here.
If we can have some reasonable solutions it would be fine, because this
"steady progressbar" issue is also related
to many other operations like synchronize/update/switch etc ...
Martin
Received on Wed Jun 29 21:56:38 2005