On 06 Dec 2015, at 21:34, Sven Van Caekenberghe <sven@stfx.eu> wrote:
There is still #do:displayingProgress:
There is Job.
In general, the collection API should not be concerned with GUI matters, does it ?
this. also including notifications âjust in case someone needs itâ will slowdown the system in general. as always: if want it, you can extend it in your programs. The API we propose is Job, so everybody can create their own âinformingâ versions.
We can't have equivalents of all collection methods for displaying progress, nor can it be a (semi-) global setting.
this too
If you look at how HTTPProgress is implemented/used, as a Notification, that might be a part of a solution, but I would not want to pay that performance price in the general API.
+42 Esteban
I think there is no 'free' or 'easy' solution.
On 06 Dec 2015, at 21:23, stepharo <stepharo@free.fr> wrote:
Probably because it was badly done.
Le 6/12/15 20:05, Hernán Morales Durand a écrit :
Hello everyone,
Is there a reason why #collect:displayingProgress: was removed or never included?
And as more general question, is there any pointer to automatically add progress bar to iterator messages?
For example doing:
SmalltalkImage setDisplayProgressTo: MyClass. SmalltalkImage setDisplayProgressTo: MyPackage.
and then having all enumeration messages sent in MyClass or MyPackage with a progress bar
collect: collect:as: collect:into: collect:thenDo: select: select:as: select:thenDo: select:thenCollect:as: ...
Hernán