November 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Iceberg v1.3.1

by Cyril Ferlicot

On Mon, Nov 5, 2018 at 5:09 PM HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Hi Cyril, > > Does the update apply to Pharo 6.1? > Hi, The version will not be present by default in Pharo 6.1 because it cause too much changes to be in a minor release. (The last Iceberg release in Pharo 6.1 was the 0.6 or 0.7 I think). But it can be loaded via the script in the README. > Cheers, > > HernÃ¡n > -- Cyril Ferlicot https://ferlicot.fr

Nov. 6, 2018

Re: [Pharo-dev] [ANN] The STON Specification

by Julien

Hello, STON is able to serialise Pharoâs Floats, what do you mean by double ? Additionally, I recently asked Sven if t would be possible to store ScaledDecimals (I think it implements what you call ArbitraryPrecisionFloats) without loss of precision. Before, because STON extends JSON, it was storing all kind of numbers either as float or integer. Now, thanks to Sven, STON stores ScaledDecimals correctly (without loss of precision through serialisation as float, what was done before). But I do not know if this change is integrated in recent images yet. Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 6 nov. 2018 Ã 06:58, Shaping <shaping(a)uurda.org> a Ã©crit : > > (Having domain problems recently. Please excuse this posting if you have > seen it twice. I've not seen it appear yet on the list.) > > > Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? > > Shaping > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of > David T. Lewis > Sent: Wednesday, October 31, 2018 14:58 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] [ANN] The STON Specification > > This is very clear and well written. > > Dave > >> Hi, >> >> Since there can never be enough documentation I finally took some time >> to write a more formal description of STON as a data format. >> >> https://github.com/svenvc/ston/blob/master/ston-spec.md >> >> The idea is to let this stabilise a bit and to then update the two >> other documents describing STON, where necessary: >> >> https://github.com/svenvc/ston/blob/master/ston-paper.md >> >> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc >> cessfulBuild/artifact/book-result/STON/STON.html >> >> Also, the latest changes in STON have to make their way to the Pharo >> image as well. >> >> https://github.com/svenvc/ston >> >> All feedback is welcome. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> > > > > >

Nov. 6, 2018

Porting from VW to Pharo

by Shaping

Can someone point me to the best tools for porting from VW 7.10 to Pharo 7 64-bit (or maybe 6.1)? I'm not sure what to do about the namespaces. I realize that VW's namespace solution is just a good hack and that the true nature of the problem runs much deeper--but it does a good job of avoiding class-name collisions, which is mostly what I need it for, and I can control exactly how imports work. Any suggestions are welcome. Thanks. Shaping

Nov. 6, 2018

[ANN] The STON Specification

by Shaping

(Having domain problems recently. Please excuse this posting if you have seen it twice. I've not seen it appear yet on the list.) Can STON be extended to handle Doubles and ArbitraryPrecisionFloats? Shaping -----Original Message----- From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of David T. Lewis Sent: Wednesday, October 31, 2018 14:58 To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] [ANN] The STON Specification This is very clear and well written. Dave > Hi, > > Since there can never be enough documentation I finally took some time > to write a more formal description of STON as a data format. > > https://github.com/svenvc/ston/blob/master/ston-spec.md > > The idea is to let this stabilise a bit and to then update the two > other documents describing STON, where necessary: > > https://github.com/svenvc/ston/blob/master/ston-paper.md > > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuc > cessfulBuild/artifact/book-result/STON/STON.html > > Also, the latest changes in STON have to make their way to the Pharo > image as well. > > https://github.com/svenvc/ston > > All feedback is welcome. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Nov. 6, 2018

Zinc Websockets

by Shaping

Hi all. What is the easiest way to port Zinc Websockets to VW? Has this been done? Shaping

Nov. 6, 2018

Re: [Pharo-dev] Now this is fun ...

by Todd Blanchard

Based on his activity level - it is abandoned. Ask him nicely and I'd bet he would relinquish it. He can move his stuff to jpharo (which is great until we port the VM to Java like JRuby) or something. > On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > PR bomb... fork all his repos and issue gazillons of PRs. > > Or maybe ask Github for turning ownership to us. > > Phil > > On Mon, Nov 5, 2018, 17:19 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com> wrote: > :) > > I think nobody expects Pharo to be : https://github.com/pharo-project <https://github.com/pharo-project> > > but like these: > > https://github.com/perl <https://github.com/perl> -> The Perl Programming Language > https://github.com/ruby <https://github.com/ruby> -> The Ruby Programming Language > https://github.com/python <https://github.com/python> -> The Python Programming Language > > More fun: > > https://github.com/smalltalk <https://github.com/smalltalk> -> Mareike Hybsier > https://github.com/lisp <https://github.com/lisp> -> James Anderson > https://github.com/rust <https://github.com/rust> -> Shinichiro OGAWA > https://github.com/cpp <https://github.com/cpp> -> Stefan Herr > https://github.com/java <https://github.com/java> -> A product manager > > > > El lun., 5 nov. 2018 a las 12:44, Sven Van Caekenberghe > (<sven(a)stfx.eu <mailto:sven@stfx.eu>>) escribiÃ³: > > > > https://github.com/pharo <https://github.com/pharo> > > > > ;-) > > > > >

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by phil＠highoctane.be

On Mon, Nov 5, 2018, 18:55 James Foster <Smalltalk(a)jgfoster.net wrote: > > > On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > > > PR bomb... fork all his repos and issue gazillons of PRs. > > I hope this was in jest. > Sure. We already are mixing #pharo with Marseille and a video game... Phil > > > Or maybe ask Github for turning ownership to us. > > If he has been there for a while and that is his name, then we have no > grounds for taking it away. The transfer of ownership case is for a company > that holds a trademark and the other use is causing confusion. I donât > think anyone going to his site will be confused. > > > > > Phil > > James >

Nov. 5, 2018

[Pharo 7.0-dev] Build #1363: 22627-Integrate-Iceberg-131

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1363 was: SUCCESS. The Pull Request #1951 was integrated: "22627-Integrate-Iceberg-131" Pull request url: https://github.com/pharo-project/pharo/pull/1951 Issue Url: https://pharo.fogbugz.com/f/cases/22627 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 5, 2018

Re: [Pharo-dev] Now this is fun ...

by James Foster

> On Nov 5, 2018, at 9:07 AM, phil(a)highoctane.be wrote: > > PR bomb... fork all his repos and issue gazillons of PRs. I hope this was in jest. > Or maybe ask Github for turning ownership to us. If he has been there for a while and that is his name, then we have no grounds for taking it away. The transfer of ownership case is for a company that holds a trademark and the other use is causing confusion. I donât think anyone going to his site will be confused. > > Phil James

Nov. 5, 2018

Re: [Pharo-dev] [ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]

by Ben Coman

On Mon, 5 Nov 2018 at 22:17, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, 5 Nov 2018 at 20:02, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> Ben Coman <btc(a)openinworld.com> wrote: >> > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < >> > pharo-users(a)lists.pharo.org> wrote: >> > >> >> What is the current status of this? DelaySpinScheduler is default in my >> recent Pharo 7 images and makes my images unusable on Ubuntu 18.04LTS. >> > > The refactoring was enabled a month ago. DelaySemaphoreScheduler in the > refactored hierarchy was made default so that DelaySpinScheduler could > remain in place in the old hierarchy . > > https://github.com/pharo-project/pharo/blame/development/src/Kernel/Delay.c… > Working through this on Discord with Stefan, discovered that earlier <Store Settings> had recorded DelaySpinScheduler when it was active was asserting itself in every freshly created image. I guess a lot of people will be susceptible to this, particularly if like me they don't remember where those files are without googling for it. In this case could fix it by changing System > System Settings > System > Delay Scheduler = DelaySemaphoreScheduler and then in Settings clicking <Store Settings>. But maybe something else needs to be done to head off this trap for everyone else. cheers -ben

Nov. 5, 2018