On 2012-11-30, at 18:15, stephane ducasse <[email protected]> wrote:
> camillo > > one of the problem that we have is that the refactoring stopped in the middle > because displayProgressFrom: minVal to: maxVal during: workBlock now works > with job and this is nice > but job requires but all the user of displayProgressFrom: minVal to: maxVal > during: workBlock > are using bar current: aNumber and not a value between 0 and 1.0. > > So this means that we will a lot of broken code. > Am I correct? right now Job works still with min/max/current so I still have to do the full transition. Ideally no code will be broken, since most people use progress bars via one of the public interfaces, either on String, Collections or directly on the UI Manager. => these will be the main places to change it. I think I can have a look at it today or tomorrow and finish the refactoring.
