June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] #assert:equals:

by Sean P. DeNigris

Camillo Bruni-3 wrote > > I hate to go and re-eavluate the code to see what was wrong during > comparison... > ...self assert: self someExpressionReturningFalse = self > someExpressionReturningTrue > how the heck do you know what went wrong? > Yes, that's exactly it! Camillo Bruni-3 wrote > > I don't like it particularly, it feels too java-ish, I prefer much more > the "shoulder" > framework written in bern. > self someExpressionReturningFalse should = self > someExpressionReturningTrue > +1! Re the framework, do you mean Phexample? I *really* like the matchers, like the one you mentioned above. Although I don't like the way tests build on each other. It's a great idea, but a failing given should cause the test to be skipped, which we don't have in Pharo (the best we can do is probably have it be an error, which is better than a failing test, but not by much) -- View this message in context: http://forum.world.st/assert-equals-tp4636050p4636136.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 22, 2012

[Pharo-project] Concatenation

by Torsten Bergmann

Try: 1. 'P' , 'haro' 2. #P , 'haro' 3. $P , 'haro' in Pharo, Squeak and Dolphin Number 3 crashes with an MNU in VW and SmalltalkMT Number 2 and 3 crash with an MNU Just wonder why ST's handle case 2 differently Bye T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

June 22, 2012

Re: [Pharo-project] Squeaksource down?

by Camillo Bruni

grazie mille! On 2012-06-22, at 13:11, Fabrizio Perin wrote: > Sueaksource is up again > > 2012/6/22 Fabrizio Perin <fabrizio.perin(a)gmail.com> > >> We are having problems with the server hosting squeaksource. >> >> It will be up again soon. >> >> Fabrizio >> >> 2012/6/22 phil(a)highoctane.be <phil(a)highoctane.be> >> >> Cannot reach it from here (lots of other sites are fine). >>> >>> Annoying for getting the configs loaded for a fresh image... (testing >>> 1.4 #441) >>> >>> Phil >>> >> >>

June 22, 2012

Re: [Pharo-project] Squeaksource down?

by Fabrizio Perin

Sueaksource is up again 2012/6/22 Fabrizio Perin <fabrizio.perin(a)gmail.com> > We are having problems with the server hosting squeaksource. > > It will be up again soon. > > Fabrizio > > 2012/6/22 phil(a)highoctane.be <phil(a)highoctane.be> > > Cannot reach it from here (lots of other sites are fine). >> >> Annoying for getting the configs loaded for a fresh image... (testing >> 1.4 #441) >> >> Phil >> > >

June 22, 2012

[Pharo-project] How to contribute to Pharo book

by Torsten Bergmann

Me wrote >How can we expect people to contribute to the collabroactive >book when the section on "how to contribute" is empty? > >http://book.pharo-project.org/book/Contribute/ContributeToPharoBook Whoever changed it today: thanks! Thx T. -- NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone! Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a

June 22, 2012

[Pharo-project] could metacello be hosted on ss3 or smalltalkhub or not load configurationOfHelp?

by Torsten Bergmann

Stef wrote: >because right now we cannot load configurations because it requires >configuration of Help and >squeaksource is done. >It would be good to have a small version of metacello just loading the bare >minimum. to Dale: Especially since "configuration of Help" is not required anymore. Help system is in Pharo and Squeak included. A "core" without help would be good Thx T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

June 22, 2012

Re: [Pharo-project] could metacello be hosted on ss3 or smalltalkhub or not load configurationOfHelp?

by Frank Shearar

If it's a question of availability, Metacello's canonical repository is actually here: http://seaside.gemstone.com/ss/metacello. This has as its latest version dkh.694. frank On 22 June 2012 08:35, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > because right now we cannot load configurations because it requires configuration of Help and > squeaksource is done. > It would be good to have a small version of metacello just loading the bare minimum. > > Stef

June 22, 2012

Re: [Pharo-project] New System Progress Bar

by Pavel Krivanek

http://code.google.com/p/pharo/issues/detail?id=6123 On Fri, Jun 22, 2012 at 11:27 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > It seems that the new progress bar doesn't work well with DummyUIManager, see > https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/job/Pharo%20Kernel%… > > -- Pavel > > On Thu, Jun 21, 2012 at 4:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> To help explain the changes, here's a snippet from the fix to "Issue 6099: >> Deprecate #value: for system progress (was red cross during updates)" >> (http://code.google.com/p/pharo/issues/detail?id=6099) The API (see >> SystemProgressItemMorph) is not set in stone, but it's already much less >> confusing than the old pseudo-class implementation. Ultimately, I'd like to >> move to announcements instead of exceptions to signal progress, and decouple >> the progress model/view - maybe just [un]registering the progress morph to >> enable/disable. >> >> The slice in the inbox for this issue should fix the "red cross during >> updates" problem... >> >> MOTIVATION: >> The old system progress worked like this (for example)... >> >> Â Â Â Â SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | >> Â Â Â Â Â Â Â Â 1 to: 100 do: [ :x | >> Â Â Â Â Â Â Â Â Â Â Â Â bar value: x. >> Â Â Â Â Â Â Â Â Â Â Â Â bar value: 'On iteration ', x asString. >> Â Â Â Â Â Â Â Â Â Â Â Â (Delay forMilliseconds: 20) wait "Just to slow it down so we can see >> what's going on" ] ]. >> >> * The work block ([ :bar | ... ] above) would accept one argument >> * That argument (:bar above) would be a block, that would act as a >> pseudo-class. Depending on what was passed to #value:, it would perform >> different functions. Two are illustrated above: >> Â - #value: aNumber; where aNumber is between the min and max of the >> progress range -> Set the bar's current progress mark to that position. For >> example, 'bar value: 50' above would show the operation half complete >> Â - #value: aString -> Set the label of the progress morph to aString >> >> This was very confusing, so we created a real class, >> SystemProgressItemMorph, which now gets passed to the work block, and has a >> real API. So, for example, the following becomes: >> >> Â Â Â Â SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | >> Â Â Â Â Â Â Â Â 1 to: 100 do: [ :x | >> Â Â Â Â Â Â Â Â Â Â Â Â bar current: x. >> Â Â Â Â Â Â Â Â Â Â Â Â bar label: 'On iteration ', x asString. >> Â Â Â Â Â Â Â Â Â Â Â Â (Delay forMilliseconds: 20) wait "Just to slow it down so we can see >> what's going on" ] ]. >> >> As you can see, '#value: newValue' has become '#current: newValue', and >> '#value: newLabel' has become '#label: newLabel'. >> >> One wrinkle is that some users were passing a nil-like block instead of the >> the pseudo-class to suppress the system progress bar. For example: >> Â Â Â Â informUserDuring: aBlock >> Â Â Â Â Â Â Â Â aBlock value: [:string | ]. >> >> Above, [:string | ] would now cause a DNU when sent, for example, #current:, >> which obviously blocks don't understand. So, these cases were changed like >> so: >> Â Â Â Â informUserDuring: aBlock >> Â Â Â Â Â Â Â Â aBlock value: DummySystemProgressItem new. >> >> Where DummySystemProgressItem simply ignores all messages without signaling >> an error >> >> -- >> View this message in context: http://forum.world.st/New-System-Progress-Bar-tp4635912.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>

June 22, 2012

Re: [Pharo-project] New System Progress Bar

by Pavel Krivanek

It seems that the new progress bar doesn't work well with DummyUIManager, see https://ci.lille.inria.fr/pharo/view/Pharo-Kernel%202.0/job/Pharo%20Kernel%… -- Pavel On Thu, Jun 21, 2012 at 4:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > To help explain the changes, here's a snippet from the fix to "Issue 6099: > Deprecate #value: for system progress (was red cross during updates)" > (http://code.google.com/p/pharo/issues/detail?id=6099) The API (see > SystemProgressItemMorph) is not set in stone, but it's already much less > confusing than the old pseudo-class implementation. Ultimately, I'd like to > move to announcements instead of exceptions to signal progress, and decouple > the progress model/view - maybe just [un]registering the progress morph to > enable/disable. > > The slice in the inbox for this issue should fix the "red cross during > updates" problem... > > MOTIVATION: > The old system progress worked like this (for example)... > > Â Â Â Â SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | > Â Â Â Â Â Â Â Â 1 to: 100 do: [ :x | > Â Â Â Â Â Â Â Â Â Â Â Â bar value: x. > Â Â Â Â Â Â Â Â Â Â Â Â bar value: 'On iteration ', x asString. > Â Â Â Â Â Â Â Â Â Â Â Â (Delay forMilliseconds: 20) wait "Just to slow it down so we can see > what's going on" ] ]. > > * The work block ([ :bar | ... ] above) would accept one argument > * That argument (:bar above) would be a block, that would act as a > pseudo-class. Depending on what was passed to #value:, it would perform > different functions. Two are illustrated above: > Â - #value: aNumber; where aNumber is between the min and max of the > progress range -> Set the bar's current progress mark to that position. For > example, 'bar value: 50' above would show the operation half complete > Â - #value: aString -> Set the label of the progress morph to aString > > This was very confusing, so we created a real class, > SystemProgressItemMorph, which now gets passed to the work block, and has a > real API. So, for example, the following becomes: > > Â Â Â Â SystemProgressMorph show: 'Doing...' from: 1 to: 100 during: [ :bar | > Â Â Â Â Â Â Â Â 1 to: 100 do: [ :x | > Â Â Â Â Â Â Â Â Â Â Â Â bar current: x. > Â Â Â Â Â Â Â Â Â Â Â Â bar label: 'On iteration ', x asString. > Â Â Â Â Â Â Â Â Â Â Â Â (Delay forMilliseconds: 20) wait "Just to slow it down so we can see > what's going on" ] ]. > > As you can see, '#value: newValue' has become '#current: newValue', and > '#value: newLabel' has become '#label: newLabel'. > > One wrinkle is that some users were passing a nil-like block instead of the > the pseudo-class to suppress the system progress bar. For example: > Â Â Â Â informUserDuring: aBlock > Â Â Â Â Â Â Â Â aBlock value: [:string | ]. > > Above, [:string | ] would now cause a DNU when sent, for example, #current:, > which obviously blocks don't understand. So, these cases were changed like > so: > Â Â Â Â informUserDuring: aBlock > Â Â Â Â Â Â Â Â aBlock value: DummySystemProgressItem new. > > Where DummySystemProgressItem simply ignores all messages without signaling > an error > > -- > View this message in context: http://forum.world.st/New-System-Progress-Bar-tp4635912.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 22, 2012

[Pharo-project] [update 2.0] #20153

by Esteban Lorenzano

20153 ----- Issue 6069: Test guard for 20132 http://code.google.com/p/pharo/issues/detail?id=6069 Issue 6041: smart characters behave wrong on deletion http://code.google.com/p/pharo/issues/detail?id=6041 Issue 5945: Nice packaging for Text stuff http://code.google.com/p/pharo/issues/detail?id=5945

June 22, 2012