- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by StÃ©phane Ducasse

And I cleaned it removing broken options :) In essence this is a dsl built using functional programming style. Would be better to have an object :) On May 14, 2012, at 4:56 PM, Sean P. DeNigris wrote: > Holy crap, SystemProgressMorph's "instance creation" method doesn't return an > instance at all but a block. I really wish I understood this design decision > before I try to cut all this out. Yikes, check out > SystemProgressMorph>>label:min:max: > > label: shortDescription min: startMinValue max: startMaxValue > "Answer the block that updates the progress bar." > > "some fun stuff added (by kph) > > - bar value: #label. - tell me my current label. > - bar value: 'newLabel'. - enable changing the label from within the > workBlock > - bar value: #increment. - enable progress by one without keeping a counter > - bar value: #decrement. - go backwards (if you really have to, useful for > an abort, or rollback)! > > - bar value: newBigNum. - change the max on the fly - when you find there > is more to do. > - bar value: (bar value: #setMax) + 20 - change the max on the fly - when > you find there is more/less to do. > - bar value: (bar value: #setMin) - 20 - change the min on the fly - not > sure why you would want to. > " > | slot range barSize lastRefresh maxValue minValue bar| > maxValue := startMaxValue. > minValue := startMinValue. > ((range := maxValue - minValue) <= 0 or: [(slot := self nextSlotFor: > shortDescription) = 0]) > ifTrue: [^[:barVal| 0 ]]. > self recenter. > self openInWorld. > barSize := -1. "Enforces a inital draw of the morph" > lastRefresh := Time millisecondClockValue. > bar := bars at: slot. > ^[:barValArg | | barVal return newBarSize | > barVal := barValArg. > return := nil. > bar := bars at: slot. > "new fun stuff here" > barVal == #current ifTrue: [ return := barSize ]. > barVal == #label ifTrue:[ return := (labels at: slot) contents ]. > barVal == #setMax ifTrue: [ return := maxValue. maxValue := minValue ]. > barVal == #setMin ifTrue: [ return := minValue. minValue := maxValue ]. > barVal == #increment ifTrue: [return := barVal := barSize + 1]. > barVal == #decrement ifTrue: [ return := barVal := barSize - 1]. > (barVal isString and: [barVal isSymbol not]) ifTrue: [ > (labels at: slot) contents: barVal. > barVal := #refresh]. > barVal == #refresh ifTrue: [self currentWorld displayWorld. return := > true]. > (barVal == SmallInteger maxVal or: [ barVal == #finished ]) ifTrue: > [return := slot]. > return ifNil: [ > barVal > maxValue ifTrue: [return := maxValue := barVal]. > barVal < minValue ifTrue: [return := minValue := barVal]. > (barVal between: minValue and: maxValue) > ifTrue: [newBarSize := (barVal - minValue / range * BarWidth) truncated. > newBarSize = barSize > ifFalse: [barSize := newBarSize. > (Time millisecondsSince: lastRefresh) > 25 > ifTrue: [barVal := #refresh ]]]. > barVal == #refresh ifTrue: [ > ((bar valueOfProperty: #useStripes) ifNil: [false]) > ifTrue: [bar fillStyle origin: bar position - ((Time > millisecondClockValue // 50 \\ 30) @ 0)]. > bar barSize: barSize. > self currentWorld displayWorld. > lastRefresh := Time millisecondClockValue]]. > return] > > -- > View this message in context: http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 15, 2012

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by StÃ©phane Ducasse

On May 14, 2012, at 3:05 PM, Sean P. DeNigris wrote: > > Sean P. DeNigris wrote >> >> * String>>displayProgressAt:from:to:during: has "deprecated" in the >> comment, but is not in a deprecated category. The timestamp is 9/7/11 >> which puts it either 1.2 or early 1.3, but either way, it should be >> removed for 2.0, right? Yes >> There is only one sender in the image, which can >> easily be fixed to call #displayProgressFrom:to:during: >> > > Steph, this one's yours, do you know why it was deprecated and why it was > done in the comment instead of using deprecated:on:in:? Is wanting to place > a progress bar in a specific location not ever needed? If not, we should > remove it from all the UIManagers also, right? Because this is the responsibility of the domain to take decision on the UI placement. This is the UI manager or other that should take such decision. It also removes breaking layer and forcing people to query from the domain the current mouse position and most of the time people used Sensor hence violating again basic layering because in Morphic the mouse position should be queried by activeHand. > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 15, 2012

Re: [Pharo-project] Pharo is exploding

by Max Leske

A random thought: how about a stackexchange site for smalltalk? Most of the things disussed on the list could probably go there and the list would once again be a quiet place for core stuff only. We (or I) would have to propose a new site and we would need people from Pharo AND Squeak (and hopefully other dialects too) to come aboard to promote the site. The entire process of creation is explained here: http://area51.stackexchange.com/faq Cheers, Max On 15.05.2012, at 07:30, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 15 May 2012, at 04:43, Igor Stasenko wrote: > >> it was a time, when were able to track all activities around squeak, >> pharo and vm.. >> >> today the amount of updates, news and activities is just overwhelming.. >> >> a rusty locomotive, which once staying in backyard, repaired by Stef >> and Marcus and now goes faster and faster :) > > So true: I am happy and frustrated at the same time. So much is happening, I can't even follow all the stuff that falls into my own domain, let alone all the other interesting things. > > Sven > >

May 15, 2012

Re: [Pharo-project] Pharo is exploding

by Sven Van Caekenberghe

On 15 May 2012, at 04:43, Igor Stasenko wrote: > it was a time, when were able to track all activities around squeak, > pharo and vm.. > > today the amount of updates, news and activities is just overwhelming.. > > a rusty locomotive, which once staying in backyard, repaired by Stef > and Marcus and now goes faster and faster :) So true: I am happy and frustrated at the same time. So much is happening, I can't even follow all the stuff that falls into my own domain, let alone all the other interesting things. Sven

May 15, 2012

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by Sean P. DeNigris

I have a few questions about displaying progress... 1. What's the best way to do something like the following: I may be in the UI thread. I want to process a loop in a background thread, but block my current execution path, while still letting the world update. This is my use case... NewSystemProgressMorph>>show: aString from: startNumber to: endNumber during: aBlock | progressMorph | progressMorph := self addItemShowing: aString from: startNumber to: endNumber. self recenter. self openInWorld. [ [ progressMorph do: aBlock ] ensure: [ self close: progressMorph ] ] fork. [ progressMorph hasResult ] whileFalse: [ self currentWorld displayWorld. (Delay forMilliseconds: 20) wait ]. ^ progressMorph result I kept the #displayWorld from the old SystemProgressMorph, but it feels like a hack. I can't rely on stepping because I have to block until result is returned. "progressMorph do: aBlock" sets result, protected by a critical section of a Semaphore (I don't know if that's right/safe, just cobbled it together from the old implementation and a little googling). 2. what morphic messages from a non-UI thread have to be wrapped in addDeferredUIMessage:? #delete? repositioning a Morph? Is it any message sent to a morph, or only particular ones. 3. If anyone's using the following SystemProgressMorph functionality, please speak up. It seems overcomplicated and may disappear very soon :) value: newBigNum. - change the max on the fly - when you find there is more to do. bar value: (bar value: #setMax) + 20 - change the max on the fly - when you find there is more/less to do. bar value: (bar value: #setMin) - 20 - change the min on the fly - not sure why you would want to. -- View this message in context: http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 15, 2012

Re: [Pharo-project] Notify progress with Announcements instead of Exceptions

by Sean P. DeNigris

Sean P. DeNigris wrote > > Holy crap, SystemProgressMorph... As a first step, I cleaned out the system progress morph classes... Issue 5897: [ENH]: Clean SystemProgressMorph and friends Fix in inbox: SLICE-Issue-5897-ENH-Clean-SystemProgressMorph-and-friends-SeanDeNigris.1 * create NewSystemProgressMorph as a replacement for SystemProgressMorph * create SystemProgressItemMorph to capture all the behavior from the huge block in SystemProgressMorph>>label:min:max: * Rename SystemProgressBarMorph to ProgressBarMorph (there's nothing System-specific) and clean I'd like someone to review the code, especially the process/semaphore parts of NewSystemProgressMorph before I integrate these classes with the system via the UIManagers. I had to do "Compiler recompileAll" when I filed the classes in because the system was confused between SystemProgressBarMorph and ProgressBarMorph. I'm not sure why. -- View this message in context: http://forum.world.st/Notify-progress-with-Announcements-instead-of-Excepti… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 15, 2012

[Pharo-project] Pharo is exploding

by Igor Stasenko

it was a time, when were able to track all activities around squeak, pharo and vm.. today the amount of updates, news and activities is just overwhelming.. a rusty locomotive, which once staying in backyard, repaired by Stef and Marcus and now goes faster and faster :) -- Best regards, Igor Stasenko.

May 15, 2012

[Pharo-project] [ANN] Nagare - a new flexible logger for Smalltalk

by Masashi UMEZAWA

Hello all, I have recently developed a new logging library called Nagare. http://code.google.com/p/nagare-logger/ Nagare is designed to be simple and scalable. Contrary to other logging frameworks which provide rich set of log output methods (file, socket, DB, etc.), Nagare just connects to fluentd (http://fluentd.org) And Fluentd does the various log processing jobs. Features: - Simple log interfaces with reliable backend - Semi-structured logging (Not only String, you can store structured records in log) - Flexible - you can easily customise log-tags, log policy, etc. - Portable (runs on Squeak, Pharo, VisualWorks) Enjoy! -- [:masashi | ^umezawa]

May 15, 2012

Re: [Pharo-project] [squeak-dev] Fun with spock (NativeBoost FFI)

by Lawson English

I am trying to implement an asString method for gmp floats but I don't quite see how. Prototype for getting a string is: "Function: char * mpf_get_str (char *str, mp_exp_t *expptr, int base, size_t n_digits, mpf_t op)" where mp_exp_t *expptr is just a pointer to a long, and size_t is just a long. I don't get how to set up the primitive call and how to evoke it in the asString method. -- Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the (almost) complete and compleate beginner). https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all

May 15, 2012

Re: [Pharo-project] Semantic Versioning

by Dale Henrichs

I think you are referring to the the fact that there are ways to go through commits and remove sensitive data from them, however, unless I'm mistaken, the SHA of the commit gets changed when you modify it, so you may have "modified a commit" but you have done so by copying it to a new identity. The original commit with the origin SHA still exists and is accessible unless you take further steps to delete the specific commit, so in the end the commit _is_ immutable. Dale ----- Original Message ----- | From: "Douglas Brebner" <squeaklists(a)fang.demon.co.uk> | To: pharo-project(a)lists.gforge.inria.fr | Sent: Monday, May 14, 2012 3:07:00 PM | Subject: Re: [Pharo-project] Semantic Versioning | | On 14/05/2012 17:51, Dale Henrichs wrote: | | One of the appeals of git/github is that a git commit is immutable so | all of the artifacts in a commit are guaranteed. | Are you sure? It was my understanding that you can alter a git | commit. Not advisable, but possible. |

May 14, 2012