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

Re: [Pharo-dev] Monetary package

by Chris Cunningham

First, is FixedDecimal used in the Money package? I didn't see is referenced there, so I'm curious where it came from. There is a definite different between ScaledDecimal and FixedDecimal. ScaledDecimal (unless it's been changed recently) keeps the full precision of the original number. FixedDecimal (and Money, from my short perusal of it), do not - they make sure that the displayed value is exactly what the internal value is. As an example, check out the following: x := ((1/3) asScaledDecimal: 2). x ==> 0.33s2 x = (1/3) ==> true ((33/100) asScaledDecimal: 2) ==> 0.33s2 x = ((33/100) asScaledDecimal: 2) ==> false (!) x + x ==> 0.67s2 (!) In general, the last 2 statements are NOT what you want when dealing with Money - if you have an amount, it is a definite amount, and not an approximate amount. (With the possible exceptions of interim results - but for those, you probably need strict control over exactly how precise the interim results are - which isn't readily available in ScaleDecimal). This is the main reason I built the FixedDecimal package on SqueakSource. There, the above statements show: x := ((1/3) asFixedDecimal: 2). x ==> 0.33 x = (1/3) ==> true ((33/100) asFixedDecimal: 2) ==> 0.33 x = ((33/100) asFixedDecimal: 2) ==> true x + x ==> 0.66 >From my perspecive, ScaledDecimal is great when you want to keep as much precision as possible, but need to SHOW less precision. It reminds me of science, where you have this measurement that is way more precise than you can really measure, so you 'scale' it back to a precision that is reliable. -Chris On Tue, Jun 11, 2013 at 1:21 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > I wondered the same. Can someone explain? > > > On Tue, Jun 11, 2013 at 3:17 AM, Denis Kudriashov <dionisiydk(a)gmail.com>wrote: > >> What the difference from scaled decimal or fixed decimal? >> >> On video I not see any currency concept. >> In past I used Units package to model money. It is very convinient to >> calculate currency exchange operations. >> What the advantage of Money package? >> >> Best regards, >> Denis >> >> >> 2013/6/10 Torsten Bergmann <astares(a)gmx.de> >> >>> Do we have a "money" package for Pharo available? >>> >>> >>> http://www.jarober.com/blog/blogView?showComments=true&title=ST+4U+396%3A+M… >>> >>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com >

June 11, 2013

Re: [Pharo-dev] [ANN]: Magritte for Morphic (alpha)

by StÃ©phane Ducasse

This is good that you work on it. Thanks for the videos. We should add it to the Pharo blog! Because we will push soon the new classBuilder and soon we will get first class instance variable and we will have a much simpler magritte, spec â¦. Stef On Jun 11, 2013, at 11:18 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Tired of writing the same UI boilerplate over and over? I mean, basically an > object has fields, which have certain properties relevant to the UI. If we > could just capture that info once in the right place, a basic UI should > almost fall out on its own. Magritte could be the answers to our lazy > utopian dreams. The thing is that the Morphic implementation as fallen > behind what can be done in Seaside... until now. I took a first pass at > bringing Morphic up to date here. It doesn't seem like it will be too hard > to have reasonably useful functionality. > > Here's a short screencast showing the improvements: > http://vimeo.com/68166920 > Magritte is an awesome framework to automate common UI tasks. Describe your > object's field once, get views everywhere. Everywhere most commonly refers > to both the web, via Seaside, and desktop via Morphic. But the Morphic > implementation had fallen behind due to disuse. Now, some steps have been > taken to bring the Morphic functionality up to date with that of Seaside. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-Magritte-for-Morphic-alpha-tp4692877.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by StÃ©phane Ducasse

gather: sucks as a name. flatCollect: is much better so do not remove it. On Jun 11, 2013, at 4:53 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > If they are not different so a better way would be replace #flatenCollect: by #gather: > but anyway, moose people should decide and commit the change since i am not a moose developer. > > > 2013/6/11 Marcus Denker <marcus.denker(a)inria.fr> > > On Jun 11, 2013, at 4:24 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > > > On 11 June 2013 14:18, Sebastian Tleye <stleye(a)gmail.com> wrote: > >> Hello, > >> > >> Fixing some bugs in Traits we realized that it would be good idea to use > >> CollectionsExtensions package (it has some useful functions), also it would > >> be great to include CollectionsExtensions in Pharo 3.0. > > > > Is this the HPI library? I seem to recall TraitClasses [1] using it. > > CollectionExtension is from Moose. > > the Trait based Stream refactoring was done some years ago but has not been used > or maintained. > > Marcus >

June 11, 2013

Re: [Pharo-dev] Modification on CollectionsExtensions

by StÃ©phane Ducasse

Yes please go ahead. Stef On Jun 11, 2013, at 4:49 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > I don't know, i should see the implementation, i just want to remove the dependency between CollectionsExtensions and Nile and one way to do it is modifying #flatCollect: implementation. > > if they are the same #flatCollect: could be remove safely replaced. > > > 2013/6/11 Camille Teruel <camille.teruel(a)gmail.com> > > On 11 juin 2013, at 15:18, Sebastian Tleye wrote: > > > Hello, > > > > Fixing some bugs in Traits we realized that it would be good idea to use CollectionsExtensions package (it has some useful functions), also it would be great to include CollectionsExtensions in Pharo 3.0. > > > > One "problem" we found is that CollectionsExtensions is depending on a Nile Package (that's not a desired feature). > > In the method Collection>>flatCollect: there is a line refering to a nile function "nsWriteStream". > > How this #flatCollect: is different from #gather: anyway? > > > > > If i change "nsWriteStream" for "writeStream" the dependency disapears. > > > > I also run all the tests and they are working, so i was wondering if it would be possible to commit the change. > > > > Thanks. > > >

June 11, 2013

Re: [Pharo-dev] [squeak-dev] Re: ModTalk

by StÃ©phane Ducasse

On Jun 11, 2013, at 7:44 PM, Chris Muller <asqueaker(a)gmail.com> wrote: > Well, if "doing" includes traveling across the world, getting up on a > stage and talking about and promoting it, then I'd say all of them. > Besides that, I have no idea what they're doing with their time. :) do not dream Stef

June 11, 2013

[ANN]: Magritte for Morphic (alpha)

by Sean P. DeNigris

Tired of writing the same UI boilerplate over and over? I mean, basically an object has fields, which have certain properties relevant to the UI. If we could just capture that info once in the right place, a basic UI should almost fall out on its own. Magritte could be the answers to our lazy utopian dreams. The thing is that the Morphic implementation as fallen behind what can be done in Seaside... until now. I took a first pass at bringing Morphic up to date here. It doesn't seem like it will be too hard to have reasonably useful functionality. Here's a short screencast showing the improvements: http://vimeo.com/68166920 Magritte is an awesome framework to automate common UI tasks. Describe your object's field once, get views everywhere. Everywhere most commonly refers to both the web, via Seaside, and desktop via Morphic. But the Morphic implementation had fallen behind due to disuse. Now, some steps have been taken to bring the Morphic functionality up to date with that of Seaside. ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Magritte-for-Morphic-alpha-tp4692877.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 11, 2013

[update 3.0] #30195

by Marcus Denker

30195 ----- 10285 RecentMessageList class>>startup: is not needed https://pharo.fogbugz.com/f/cases/10285 10758 Two categories in Setting: debugging and Debugging https://pharo.fogbugz.com/f/cases/10758 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.3… http://smalltalkhub.com/mc/Pharo/Pharo30/main/RecentSubmissions-MarcusDenke…

June 11, 2013

Re: [Pharo-dev] Monetary package

by Mariano Martinez Peck

I wondered the same. Can someone explain? On Tue, Jun 11, 2013 at 3:17 AM, Denis Kudriashov <dionisiydk(a)gmail.com>wrote: > What the difference from scaled decimal or fixed decimal? > > On video I not see any currency concept. > In past I used Units package to model money. It is very convinient to > calculate currency exchange operations. > What the advantage of Money package? > > Best regards, > Denis > > > 2013/6/10 Torsten Bergmann <astares(a)gmx.de> > >> Do we have a "money" package for Pharo available? >> >> >> http://www.jarober.com/blog/blogView?showComments=true&title=ST+4U+396%3A+M… >> >> >> > -- Mariano http://marianopeck.wordpress.com

June 11, 2013

[BUG]: Extension Methods Missing from Packages

by Sean P. DeNigris

This is a nasty one. It may lead to lost code, without warning or notification. Applies to latest 2.0 and 3.0: 1. In Nautilus, in any class outside Announcements-Core, add protocol '*announcements-core-subcategory' 2. Open MCWrokingCopyBrowser. You will see that Announcements-Core is dirty 3. Click the "Changes" button It will say that there are no changes, and the package will be unmarked as dirty. This is because 'announcements-core-subcategory' was created as a separate RPackage and stole the extension method. For 3.0, https://pharo.fogbugz.com/f/cases/10887/Compound-Extension-Methods-Unpackag… > Fix in inbox: > SLICE-Issue-10887-Compound-Extension-Methods-Unpackaged-SeanDeNigris.1 > > Case 10887: Compound Extension Methods Unpackaged > > * Fix RPackageOrganizer>>checkPackageExistsOrRegister:, which is sent when > a class organization changes, to see if extension methods have been added > * Add test which fails before fix and passes after For 2.0, https://pharo.fogbugz.com/f/cases/10888/Backport-2-0-Compound-Extension-Met… > Fix in inbox: > SLICE-Issue-10888-Backport-20-Compound-Extension-Methods-Unpackaged-SeanDeNigris.1 ----- Cheers, Sean -- View this message in context: http://forum.world.st/BUG-Extension-Methods-Missing-from-Packages-tp4692842… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 11, 2013

Re: [Pharo-dev] IconicListItem>>text:icon: recently changed with bug

by Benjamin

#image: it is :) Ben On Jun 11, 2013, at 8:35 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > It looks like a bug got introduced recently in the Polymorph package. > The following code does not work: > > text: aText icon: form > > ^ self new > morph: aText asMorph; > icon: (AlphaImageMorph new form: form); > yourself > > > #form: is not implemented in AlphaImageMorph. It looks like #image: > must be sent instead. > > What do you think? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

June 11, 2013