- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] WhatsUp from: 2013-11-18 until: 2013-11-30

by Alexandre Bergel

> ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS - Pharo sprint, which has produced many fixes in Pharo - Working on geographical maps in Roassal. Screenshots available on https://www.facebook.com/ObjectProfile/photos_stream - Working on processing SVG path in Roassal - Pushing Roassal on Amber. > ### What's next, until 2013-11-30 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - Working on a revision of Deep into Pharo - Together with Pablo and Ricardo we will push Roassal on Amber - Working on integrating Athens better in Roassal Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 18, 2013

Re: [Pharo-dev] WhatsUp from: 2013-11-18 until: 2013-11-30

by Tudor Girba

I think this is an important synchronization mechanism, and we should try to keep it going. It takes only a couple of minutes to write down what you have done. ### Here's what I've been up to since the last WhatsUp: - Consolidated Moose 5.0 (it's now working fully in Pharo 3.0) - Cleaned the Moose issue tracker - Looked into the problem related to SpecDebugger requiring Spec inspector. Unfortunately, the problem is still not solved. A little story is described here: http://www.humane-assessment.com/blog/debugging-the-debugger-with-the-inspe… - Reviewed and improved GTDebugger (with Andrei) - Installed GTInspector and GTDebugger as default tools in the Moose image (with Andrei). A preview screenshot is available here: https://www.dropbox.com/s/hzxg82nzz163gb1/2013-11-15%2019.20.42%20-%20gtdeb… ### What's next, until 2013-11-30 (*): - Work on the GTDebugger to make it even sexier - Build a simple overview visualization for software systems - Translate the Moose book into Pillar Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Nov. 18, 2013

Minor corrections to class comment of Number class

by kilon alios

in #smalltalkhub few minutes ago ----------- Hallite : Small bug report: "This mechanism is extensible to any new number classes that one might wish to add to Squeak." in the Number class in Pharo Smalltalk. Halite :Why does Pharo call itself Squeak? Halite : Yet another small bug report: "Care is also taken to evaluate the sine between -90Â° and 90Â°, this will avoid #degreesToRadians and i386 FPU sine fonction to accumulate round off errors due to approximate representation of pi." fonction? -------- I opened a bug report and added the fix info here https://pharo.fogbugz.com/f/cases/12196/Minor-mistakes-in-class-comment-of-…

Nov. 18, 2013

Re: [Pharo-dev] Transcript and ScaledDecimal Issue

by Sven Van Caekenberghe

On 18 Nov 2013, at 17:26, phil(a)highoctane.be wrote: > Sure but still, why isn't store: in the Transcript for these? As they are in the other classes I am not sure the #storeOn: mechanism is still very relevant, it is a very simple form of serialization. There are multiple alternatives today (Fuel, JSON, STON, â¦). Another point is that what people call âthe Stream APIâ is very/too wide, hindering composition, wrapping and alternative implementations - hence Xtreams. Adding the missing #store: would not be much work, but would it ever be used for real ? > On Mon, Nov 18, 2013 at 5:19 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You could try using #storeString as in > > Transcript show: (1 / 2) asScaledDecimal storeString > > Sven > > On 18 Nov 2013, at 17:09, phil(a)highoctane.be wrote: > > > I was playing with ScaledDecimal when doing experiments with numbers in Pharo. > > > > Now, ScaledDecimal says in its comment: > > > > "Note that a ScaledDecimal does not printOn: exactly, however it will storeOn: exactly because the full precision fraction is kept in memory." > > > > This happens to be right when inspecting the expressions. > > > > Now, I tried to do the following: > > > > x := 2 asScaledDecimal. > > y := 1 asScaledDecimal. > > > > z := (y / x). > > > > z storeOn: Transcript. > > > > And z storeOn: Transcript fails miserably. > > > > This is due to storeOn: doing: > > > > storeOn: aStream > > "ScaledDecimal sometimes have more digits than they print (potentially an infinity). > > In this case, do not use printOn: because it would loose some extra digits" > > > > self shouldBePrintedAsLiteral > > ifTrue: [self printOn: aStream] > > ifFalse: [aStream > > nextPut: $(; > > store: numerator; > > nextPut: $/; > > store: denominator; > > nextPut: $s; > > store: scale; > > nextPut: $)] > > > > And store: doesn't exists in the ThreadSafeTranscript which happens to be no stream at all. > > > > Try this out: > > > > x := 2 asScaledDecimal. > > y := 1 asScaledDecimal. > > > > z := (y / x). > > > > "works" > > 5.0 storeOn: Transcript. > > Transcript flush. > > > > "works" > > (1/2) storeOn: Transcript. > > Transcript flush. > > > > "fails" > > z storeOn: Transcript. > > Transcript flush. > > > > "works" > > s := (String new: 30). > > st := s writeStream. > > z storeOn: st. > > Transcript > > show: 'storeOn: ', st contents; > > cr; > > show: z. > > > > Kind of annoying to do while explaining to kids. > > > > The ThreadSafe transcript looks like to be subclassed from Object and being no real stream at all. > > > > Why is it so? > > > > Phil > > > > > > > > >

Nov. 18, 2013

Re: [Pharo-dev] SuperCollider on Pharo [was: realtime]

by kilon alios

Good to hear you got the results you wanted. So you abandoned pharo as an idea ? On Mon, Nov 18, 2013 at 7:00 PM, Paul Davidowitz <pdavidow(a)fastmail.fm>wrote: > I would just like to mention that I have achieved great audio results > directly in the (Chrome) browser using HTML5 audio and javascript. > > - Paul > >

Nov. 18, 2013

Re: [Pharo-dev] [Esug-list] SmalltalkHub downtime next tuesday (25th november 2013)

by kilon alios

Thank you Nicolas for your efforts bringing us Smalltalkhub and Amber, I really love both :) And maybe one day I can help you make smalltalkhub a bit better, I am still fresh with pharo but the more time passes the more confident and capable I become to make valuable contributions . On Mon, Nov 18, 2013 at 4:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nevertheless, it is still appreciated :) > > Cheers, > Doru > > > On Mon, Nov 18, 2013 at 3:49 PM, Nicolas Petton <petton.nicolas(a)gmail.com>wrote: > >> Small correction: next tuesday will be the 26th, not the 25th :) >> >> Nico >> >> Tudor Girba writes: >> >> > Thank you for your effort! This is much appreciated. >> > >> > Cheers, >> > Doru >> > >> > >> > On Mon, Nov 18, 2013 at 3:45 PM, Nicolas Petton < >> petton.nicolas(a)gmail.com>wrote: >> > >> >> Hi! >> >> >> >> Smalltalkhub will be down next tuesday (25th november 2013) at 2pm. One >> >> hour >> >> downtime is expected. >> >> >> >> I will perform an upgrade of SmalltalkHub next tuesday and move the >> >> service to a new server at Inria. Many bug fixes as well as stability >> >> improvements are planned for this upgrade. >> >> >> >> Cheers, >> >> Nico >> >> >> >> _______________________________________________ >> >> Esug-list mailing list >> >> Esug-list(a)lists.esug.org >> >> http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org >> >> >> >> >> -- >> Nicolas Petton >> http://nicolas-petton.fr >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 18, 2013

Re: [Pharo-dev] SuperCollider on Pharo [was: realtime]

by Paul Davidowitz

I would just like to mention that I have achieved great audio results directly in the (Chrome) browser using HTML5 audio and javascript. - Paul

Nov. 18, 2013

Re: [Pharo-dev] Transcript and ScaledDecimal Issue

by phil＠highoctane.be

Sure but still, why isn't store: in the Transcript for these? As they are in the other classes On Mon, Nov 18, 2013 at 5:19 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > You could try using #storeString as in > > Transcript show: (1 / 2) asScaledDecimal storeString > > Sven > > On 18 Nov 2013, at 17:09, phil(a)highoctane.be wrote: > > > I was playing with ScaledDecimal when doing experiments with numbers in > Pharo. > > > > Now, ScaledDecimal says in its comment: > > > > "Note that a ScaledDecimal does not printOn: exactly, however it will > storeOn: exactly because the full precision fraction is kept in memory." > > > > This happens to be right when inspecting the expressions. > > > > Now, I tried to do the following: > > > > x := 2 asScaledDecimal. > > y := 1 asScaledDecimal. > > > > z := (y / x). > > > > z storeOn: Transcript. > > > > And z storeOn: Transcript fails miserably. > > > > This is due to storeOn: doing: > > > > storeOn: aStream > > "ScaledDecimal sometimes have more digits than they print > (potentially an infinity). > > In this case, do not use printOn: because it would loose some > extra digits" > > > > self shouldBePrintedAsLiteral > > ifTrue: [self printOn: aStream] > > ifFalse: [aStream > > nextPut: $(; > > store: numerator; > > nextPut: $/; > > store: denominator; > > nextPut: $s; > > store: scale; > > nextPut: $)] > > > > And store: doesn't exists in the ThreadSafeTranscript which happens to > be no stream at all. > > > > Try this out: > > > > x := 2 asScaledDecimal. > > y := 1 asScaledDecimal. > > > > z := (y / x). > > > > "works" > > 5.0 storeOn: Transcript. > > Transcript flush. > > > > "works" > > (1/2) storeOn: Transcript. > > Transcript flush. > > > > "fails" > > z storeOn: Transcript. > > Transcript flush. > > > > "works" > > s := (String new: 30). > > st := s writeStream. > > z storeOn: st. > > Transcript > > show: 'storeOn: ', st contents; > > cr; > > show: z. > > > > Kind of annoying to do while explaining to kids. > > > > The ThreadSafe transcript looks like to be subclassed from Object and > being no real stream at all. > > > > Why is it so? > > > > Phil > > > > > > > > >

Nov. 18, 2013

Re: [Pharo-dev] Transcript and ScaledDecimal Issue

by Sven Van Caekenberghe

You could try using #storeString as in Transcript show: (1 / 2) asScaledDecimal storeString Sven On 18 Nov 2013, at 17:09, phil(a)highoctane.be wrote: > I was playing with ScaledDecimal when doing experiments with numbers in Pharo. > > Now, ScaledDecimal says in its comment: > > "Note that a ScaledDecimal does not printOn: exactly, however it will storeOn: exactly because the full precision fraction is kept in memory." > > This happens to be right when inspecting the expressions. > > Now, I tried to do the following: > > x := 2 asScaledDecimal. > y := 1 asScaledDecimal. > > z := (y / x). > > z storeOn: Transcript. > > And z storeOn: Transcript fails miserably. > > This is due to storeOn: doing: > > storeOn: aStream > "ScaledDecimal sometimes have more digits than they print (potentially an infinity). > In this case, do not use printOn: because it would loose some extra digits" > > self shouldBePrintedAsLiteral > ifTrue: [self printOn: aStream] > ifFalse: [aStream > nextPut: $(; > store: numerator; > nextPut: $/; > store: denominator; > nextPut: $s; > store: scale; > nextPut: $)] > > And store: doesn't exists in the ThreadSafeTranscript which happens to be no stream at all. > > Try this out: > > x := 2 asScaledDecimal. > y := 1 asScaledDecimal. > > z := (y / x). > > "works" > 5.0 storeOn: Transcript. > Transcript flush. > > "works" > (1/2) storeOn: Transcript. > Transcript flush. > > "fails" > z storeOn: Transcript. > Transcript flush. > > "works" > s := (String new: 30). > st := s writeStream. > z storeOn: st. > Transcript > show: 'storeOn: ', st contents; > cr; > show: z. > > Kind of annoying to do while explaining to kids. > > The ThreadSafe transcript looks like to be subclassed from Object and being no real stream at all. > > Why is it so? > > Phil > > >

Nov. 18, 2013

Transcript and ScaledDecimal Issue

by phil＠highoctane.be

I was playing with ScaledDecimal when doing experiments with numbers in Pharo. Now, ScaledDecimal says in its comment: "Note that a ScaledDecimal does not printOn: exactly, however it will storeOn: exactly because the full precision fraction is kept in memory." This happens to be right when inspecting the expressions. Now, I tried to do the following: x := 2 asScaledDecimal. y := 1 asScaledDecimal. z := (y / x). z storeOn: Transcript. And z storeOn: Transcript fails miserably. This is due to storeOn: doing: storeOn: aStream "ScaledDecimal sometimes have more digits than they print (potentially an infinity). In this case, do not use printOn: because it would loose some extra digits" self shouldBePrintedAsLiteral ifTrue: [self printOn: aStream] ifFalse: [aStream nextPut: $(; store: numerator; nextPut: $/; store: denominator; nextPut: $s; store: scale; nextPut: $)] And store: doesn't exists in the ThreadSafeTranscript which happens to be no stream at all. Try this out: x := 2 asScaledDecimal. y := 1 asScaledDecimal. z := (y / x). "works" 5.0 storeOn: Transcript. Transcript flush. "works" (1/2) storeOn: Transcript. Transcript flush. "fails" z storeOn: Transcript. Transcript flush. "works" s := (String new: 30). st := s writeStream. z storeOn: st. Transcript show: 'storeOn: ', st contents; cr; show: z. Kind of annoying to do while explaining to kids. The ThreadSafe transcript looks like to be subclassed from Object and being no real stream at all. Why is it so? Phil

Nov. 18, 2013