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

Re: [Pharo-dev] PharoDays?

by Stephane Ducasse

Or 24-25 of May Or 31 - 1 June? On Wed, Feb 28, 2018 at 6:09 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi guys > > many people are asking when and where there will be PharoDays. > And we do not know. > We are looking for local organisers and else we do it at Lille. > Now what would be a good date? > > What about > 7-8 June? > > Stef

Feb. 28, 2018

[Pharo 7.0-dev] Build #632: 21443 add a rule to check for proper method protocol names

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

There is a new Pharo build available! The status of the build #632 was: SUCCESS. The Pull Request #985 was integrated: "21443 add a rule to check for proper method protocol names" Pull request url: https://github.com/pharo-project/pharo/pull/985 Issue Url: https://pharo.fogbugz.com/f/cases/21443 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 28, 2018

PharoDays?

by Stephane Ducasse

Hi guys many people are asking when and where there will be PharoDays. And we do not know. We are looking for local organisers and else we do it at Lille. Now what would be a good date? What about 7-8 June? Stef

Feb. 28, 2018

[Pharo 7.0-dev] Build #631: 21448-Integrate-Calypso-v0102

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

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

Feb. 28, 2018

Re: [Pharo-dev] [Request for comment] Hermes package

by Alexandre Bergel

Side question: What is Hermes? Alexandre > On Feb 28, 2018, at 1:42 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > ... to all participating authors of the Hermes package: > > PLEASE COMMENT YOUR CLASSES SO WE CAN CLEAN UP AND PREPARE A > POLISHED PHARO 7 RELEASE > > So many uncommented classes in there today... > > We can do better and we should. I dont ask for detailed documentation > but a single comment why the class is there or what it should care > about is often already enough. > > If you have time to write code then you also have the time to write > a simple class comment! > > So please do you homework (which is a general request to authors > of other packages as well) > > Bye > T. >

Feb. 28, 2018

Re: [Pharo-dev] Roassal2 / GToolkitExamples reloads Calypso

by Peter UhnÃ¡k

I ran into this issue too... and I don't know whether it is a feature or a bug of Metacello. The Calypso dependency (in GToolkitExamples) is not actually requested, but because Metacello sees that calypso packages are already in the system, it behaves as if you requested the dependency... Peter On Wed, Feb 28, 2018 at 1:33 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Everyone, > > While loading Roassal2 with: > > Metacello new > configuration: 'Roassal2'; > repository: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main'; > version: #bleedingEdge; > load. > > > I get the warning: > > You are about to load new versions of the following packages > that have unsaved changes in the image: > > Calypso-SystemQueries > > > Because BaselineOfGToolkitExamples>>baseline: includes: > > spec baseline: 'Calypso' with: [ > spec > repository: 'github://dionisiydk/Calypso'; > loads: #default ]. > > > I can look at this eventually, but it may take a while. > > OS: Ubuntu 16.04 > Image: Pharo 7.0 Build information: > Pharo-7.0+alpha.build.629.sha.a2e3cf13c5f1208d1ee6b3d48ef7dceb9bbb1349 > (32 Bit) > (downloaded today, 28 Feb 2018) > > > Thanks! > Alistair > >

Feb. 28, 2018

Roassal2 / GToolkitExamples reloads Calypso

by Alistair Grant

Hi Everyone, While loading Roassal2 with: Metacello new configuration: 'Roassal2'; repository: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main'; version: #bleedingEdge; load. I get the warning: You are about to load new versions of the following packages that have unsaved changes in the image: Calypso-SystemQueries Because BaselineOfGToolkitExamples>>baseline: includes: spec baseline: 'Calypso' with: [ spec repository: 'github://dionisiydk/Calypso'; loads: #default ]. I can look at this eventually, but it may take a while. OS: Ubuntu 16.04 Image: Pharo 7.0 Build information: Pharo-7.0+alpha.build.629.sha.a2e3cf13c5f1208d1ee6b3d48ef7dceb9bbb1349 (32 Bit) (downloaded today, 28 Feb 2018) Thanks! Alistair

Feb. 28, 2018

[Pharo 7.0-dev] Build #630: 21440 GLMUIThemeExtraIcons should use utilities protocol instead of utils

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

There is a new Pharo build available! The status of the build #630 was: SUCCESS. The Pull Request #984 was integrated: "21440 GLMUIThemeExtraIcons should use utilities protocol instead of utils" Pull request url: https://github.com/pharo-project/pharo/pull/984 Issue Url: https://pharo.fogbugz.com/f/cases/21440 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 28, 2018

[Pharo 7.0-dev] Build #629: 21439 Cleanup buildPackageTopic:

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

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

Feb. 28, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #628: 21431-Monticello-file-out-bug-during-bootstrap

by Alistair Grant

Hi Marcus, Thanks for the explanation. I've downloaded the image anyway and loaded it up with my normal working environment and everything seems to be fine. Thanks again, Alistair On 28 February 2018 at 11:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > It tries to run linux test 3 times and gives up. > > First try: workspace was not empty, zero-conf still does not like that â> abort > Second: Crash in text editor. Happens sometimes, very seldom > > SubscriptOutOfBounds: 0 > OrderedCollection(Object)>>errorSubscriptBounds: > OrderedCollection>>at: > OrderedCollection(SequenceableCollection)>>last > RubParagraph>>extent > RubTextFieldArea(RubAbstractTextArea)>>updateExtentFromParagraph > > Third: VM crash when executing testErrorCaughtAndDefferedIfExceptionSignaledAtStartupWhenStartupUiManagerActive > > > > >> On 28 Feb 2018, at 11:30, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> This looks like it was a network problem, nothing to do with the pull request. >> >> But let me know if I'm wrong. >> >> Thanks, >> Alistair >> >> >> On 28 February 2018 at 11:24, <ci-pharo-ci-jenkins2(a)inria.fr> wrote: >>> There is a new Pharo build available! >>> >>> The status of the build #628 was: FAILURE. >>> >>> The Pull Request #976 was integrated: "21431-Monticello-file-out-bug-during-bootstrap" >>> Pull request url: https://github.com/pharo-project/pharo/pull/976 >>> >>> Issue Url: https://pharo.fogbugz.com/f/cases/21431 >>> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >> > >

Feb. 28, 2018