Re: [Pharo-dev] displayingProgress on demand

Thanks Hernan. I love your attitude: - packaging and sharing Keep pushing Stef Le 9/12/15 07:03, Hernán Morales Durand a écrit : http://www.smalltalkhub.com/#!/~hernan/ProgressBarInstaller Public write access Cheers,

Re: [Pharo-dev] displayingProgress on demand

I would like to see this code injector too. Stef Le 7/12/15 18:43, Thierry Goubier a écrit : Hi Hernán, Le 07/12/2015 18:16, Hernán Morales Durand a écrit : Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe >: There is still

Re: [Pharo-dev] displayingProgress on demand

Hi Denis, 2015-12-08 9:58 GMT+01:00 Denis Kudriashov : > Few years ago I try another approach which was work in my test. > > Instead of code rewriting to make loop iteration announcing steps you can > track periodically (in background) process which progress you want to >

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 10:29 GMT+01:00 Denis Kudriashov : > > 2015-12-08 10:16 GMT+01:00 Thierry Goubier : > >> Wishfull thinking: >> >> you have a tradeoff when you do that, you interrupt running code and so >> changes timings and synchronisations, your scan

Re: [Pharo-dev] displayingProgress on demand

If this would work, that would make many people happy ! It would be basically make tracking progress a no-cost option. > On 08 Dec 2015, at 10:29, Denis Kudriashov wrote: > > > 2015-12-08 10:16 GMT+01:00 Thierry Goubier : > Wishfull thinking: >

Re: [Pharo-dev] displayingProgress on demand

Few years ago I try another approach which was work in my test. Instead of code rewriting to make loop iteration announcing steps you can track periodically (in background) process which progress you want to report. You can scan full call stack of it suspended context for loops and analyse it

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 13:53 GMT+01:00 Guillermo Polito : > Option 2: stack introspection > - this would not initially create a performance overhead if progress is > not used > - but there is the side effect of reifying the stack (that should be > measured) > Interesting how

Re: [Pharo-dev] displayingProgress on demand

Here is what I understand. Option 1: an aspect oriented solution where all usages of iterations get rewritten inside a scope to use progress - People showed examples using the RBTreeRewriter - I think that reflectivity should be also considered Option 2: stack introspection - this would

Re: [Pharo-dev] displayingProgress on demand

Could we have a synthesis of the discussion? It would be good to have a list of working solutions with pointers. Stef

Re: [Pharo-dev] displayingProgress on demand

2015-12-08 13:53 GMT+01:00 Guillermo Polito : > Here is what I understand. > > Option 1: an aspect oriented solution where all usages of iterations get > rewritten inside a scope to use progress > - People showed examples using the RBTreeRewriter > - I think that

Re: [Pharo-dev] displayingProgress on demand

I found code. It was work only in my test where I show progress of "(1 to: 1000) do: [:i | 1 seconds wait]". stack := executionProcess suspendedContext stack reversed. progressContext := stack detect: [:each | each receiver isKindOf: SequenceableCollection] ifNone: [nil]. progressContext

Re: [Pharo-dev] displayingProgress on demand

On 12/7/2015 5:27 PM, Hernán Morales Durand wrote: but now I am failing to see how to replace #collect: with #collect:thenDo: using the rewriter: http://ws.stfx.eu/MOWS947F000O You don't need to first search using the RBParseTreeSearcher. The RBParseTreeRewriter works with search patterns.

Re: [Pharo-dev] displayingProgress on demand

Hi John, Thank you for your feedback and help! I started a ProgressBarInstaller using your corrections. Unfortunately SmalltalkHub is not working for me right now but will check tomorrow and share the link. Best regards, Hernán 2015-12-08 13:56 GMT-03:00 John Brant

Re: [Pharo-dev] displayingProgress on demand

http://www.smalltalkhub.com/#!/~hernan/ProgressBarInstaller Public write access Cheers, Hernán 2015-12-08 20:40 GMT-03:00 Hernán Morales Durand : > Hi John, > > Thank you for your feedback and help! > > I started a ProgressBarInstaller using your corrections.

Re: [Pharo-dev] displayingProgress on demand

Hi To let you know finally I used the RewriteRuleBuilder http://myfuncoding.blogspot.cz/2015/02/video-presentation-of-rewrite-tool.html which generated the rule and installed the code (the only minor detail is that class methods are not browsed by the rule browser): [ : job | | index | index

Re: [Pharo-dev] displayingProgress on demand

Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe : > There is still #do:displayingProgress: > > There is Job. > > In general, the collection API should not be concerned with GUI matters, > does it ? > > Believe me when you're executing a large workflow processing 50Gb files

Re: [Pharo-dev] displayingProgress on demand

Hi Hernán, Le 07/12/2015 18:16, Hernán Morales Durand a écrit : Hi Sven 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe >: There is still #do:displayingProgress: There is Job. In general, the collection API should not be concerned with GUI

Re: [Pharo-dev] displayingProgress on demand

> On 06 Dec 2015, at 21:34, Sven Van Caekenberghe 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”

Re: [Pharo-dev] displayingProgress on demand

Hi Thierry 2015-12-07 14:43 GMT-03:00 Thierry Goubier : > Hi Hernán, > > Le 07/12/2015 18:16, Hernán Morales Durand a écrit : > >> Hi Sven >> >> 2015-12-06 17:34 GMT-03:00 Sven Van Caekenberghe > >: >> >> There is still

Re: [Pharo-dev] displayingProgress on demand

org> Subject: Re: [Pharo-dev] displayingProgress on demand Hi Thierry 2015-12-07 14:43 GMT-03:00 Thierry Goubier <thierry.goub...@gmail.com<mailto:thierry.goub...@gmail.com>>: Hi Hernán, Le 07/12/2015 18:16, Hernán Morales Durand a écrit : Hi Sven 2015-12-06 17:34 GMT-03:00 Sve

Re: [Pharo-dev] displayingProgress on demand

f *Hernán Morales Durand > *Sent:* Tuesday, December 8, 2015 12:28 AM > *To:* Pharo Development List <pharo-dev@lists.pharo.org> > *Subject:* Re: [Pharo-dev] displayingProgress on demand > > > > Hi Thierry > > > > 2015-12-07 14:43 GMT-03:00 Thierry Goubier <t

[Pharo-dev] displayingProgress on demand

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

Re: [Pharo-dev] displayingProgress on demand

There is still #do:displayingProgress: There is Job. In general, the collection API should not be concerned with GUI matters, does it ? We can't have equivalents of all collection methods for displaying progress, nor can it be a (semi-) global setting. If you look at how HTTPProgress is

Re: [Pharo-dev] displayingProgress on demand

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