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

Fwd: [ANN] Squeak trunk bundles now signed for macOS
by Sean P. DeNigris Nov. 7, 2017

Nov. 7, 2017

FYIâ¦ fniephaus wrote > Hi all, > > I'm glad to announce that the Squeak trunk bundles are now signed for > macOS. > You can find the latest build at [1]. I hope we can soon sign them for > Windows as well. > > The Apple signing certificate was sponsored by Squeak Deutschland e.V., > the > German Squeak association. > > Best, > Fabio > > [1] http://files.squeak.org/6.0alpha/Squeak6.0alpha-17456-32bit/ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Pharo 7.0-dev] Build #266: 20648-Provide-Bitmap-variant-of-Source-Code-fonts
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2017

Nov. 7, 2017

There is a new Pharo build available! The status of the build #266 was: FAILURE. The Pull Request #441 was integrated: "20648-Provide-Bitmap-variant-of-Source-Code-fonts" Pull request url: https://github.com/pharo-project/pharo/pull/441 Issue Url: https://pharo.fogbugz.com/f/cases/20648 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #265: 20648-Provide-Bitmap-variant-of-Source-Code-fonts
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2017

Nov. 7, 2017

There is a new Pharo build available! The status of the build #265 was: FAILURE. The Pull Request #441 was integrated: "20648-Provide-Bitmap-variant-of-Source-Code-fonts" Pull request url: https://github.com/pharo-project/pharo/pull/441 Issue Url: https://pharo.fogbugz.com/f/cases/20648 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

Re: [Pharo-dev] change weird String compare: method (was about SortFunctions)
by Nicolas Cellier Nov. 7, 2017

Nov. 7, 2017

2017-11-07 14:48 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-11-07 14:45 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> 2017-11-07 14:40 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmai >> l.com>: >> >>> >>> >>> 2017-11-07 14:20 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >>> >>>> I have new question. Why we really need threeWayCompareTo:? >>>> DefaultSortFunction can implement it using standard comparison methods. >>>> >>>> >>> But what would the DefaultSortFunction use? >>> 2 among the 3 selectors < = > ? >>> It's just that we might scan String twice when <=> would do it once, but >>> apart that is OK >>> >> >> Yes, you are right. >> And we already have VM based String compare: with strange logic returning >> 1, 2, 3. So we already can optimize current String>>threeWayCompareTo:. >> > > Maybe good idea to open ticket and modify image level methods to return > standard -1,0,1 values. > > We should have done that for long. But we want to avoid images to behave differentlly depending on VM version. Possibility 1: add a new primitive, marking the old as for backward compatibility, and modify image side with backward compatibility support (try new prim, if failure try old, if failure revert to Smalltalk code) Since this primitive is only for accelerating things and not strictly necessary, we don't need backward compatibility so: Possibility 2: add a new primitive, and modify image side (try new prim if failure then revert to Smalltalk code)

1 0

[Pharo 7.0-dev] Build #264: 20644-Load-Bitmap-DejaVu-fonts-from-data-files-instead-of-a-Fuel-file
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2017

Nov. 7, 2017

There is a new Pharo build available! The status of the build #264 was: SUCCESS. The Pull Request #439 was integrated: "20644-Load-Bitmap-DejaVu-fonts-from-data-files-instead-of-a-Fuel-file" Pull request url: https://github.com/pharo-project/pharo/pull/439 Issue Url: https://pharo.fogbugz.com/f/cases/20644 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Techtalk: Nov 21
by Marcus Denker Nov. 7, 2017

Nov. 7, 2017

Pharo TechTalk: Discord Demo - 21 Nov 2017, 5:00 PM - 7:00 PM (UTC+01:00) - https://association.pharo.org/event-2642665 The December tech talk will be the 19/12. We are still looking for a topic (if not, it will just be an open discussion). List of all events: https://association.pharo.org/events Marcus

1 0

[Pharo 7.0-dev] Build #263: Care on dirty package OpalTools
by ci-pharo-ci-jenkins2＠inria.fr Nov. 7, 2017

Nov. 7, 2017

There is a new Pharo build available! The status of the build #263 was: FAILURE. The Pull Request #437 was integrated: "Care on dirty package OpalTools" Pull request url: https://github.com/pharo-project/pharo/pull/437 Issue Url: https://pharo.fogbugz.com/f/cases/20642 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] browsing squeak .mcz from pharo (was about SortFunctions)
by Nicolas Cellier Nov. 6, 2017

Nov. 6, 2017

2017-11-06 18:39 GMT+01:00 Martin Dias <tinchodias(a)gmail.com>: > > > On Mon, Nov 6, 2017 at 10:20 AM, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> >> >> Pharo still has Monticello, so it could have worked (not sure how well >> without common ancestor) >> The extra difficulty here is that package delimitation does not match, >> SortFunction has been integrated into Collection in Squeak. >> > > Hi, punctually about this: > > >> Is extracting sources From .mcz and filtering in change list still >> possible? (Epicea?) >> > > Yes, in latest Pharo 6 and 7 you can file browse or drag&drop the > source.st inside the .mcz to either file-in or see the code. (But no, > it's not Epicea). > > Martin > > Thanks Martin. What is usefull is also ability to scan the diffs. Currently, having to go thru menu and open a dead diff window method after method is a no go.

1 0

SqueakSSL on Pharo 64bit/Win
by Raffaello Giulietti Nov. 6, 2017

Nov. 6, 2017

Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm distribution. I guess this has to do with problems in building it. Anybody knows where the difficulties lie? Greetings Raffaello

3 9

[Pharo 7.0-dev] Build #262: 20520 Package "OpalTools" should be "OpalCompiler-Tools"
by ci-pharo-ci-jenkins2＠inria.fr Nov. 6, 2017

Nov. 6, 2017

There is a new Pharo build available! The status of the build #262 was: SUCCESS. The Pull Request #436 was integrated: "20520 Package "OpalTools" should be "OpalCompiler-Tools"" Pull request url: https://github.com/pharo-project/pharo/pull/436 Issue Url: https://pharo.fogbugz.com/f/cases/20520 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0