- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #461: 21110 Super tearDown need to be called as last message in tearDown ofâ¦
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #461 was: SUCCESS. The Pull Request #722 was integrated: "21110 Super tearDown need to be called as last message in tearDown ofâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/722 Issue Url: https://pharo.fogbugz.com/f/cases/21110 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #460: 21108 Super tearDown need to be called as last message in tearDown of RGMethodDefinitionTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #460 was: SUCCESS. The Pull Request #723 was integrated: "21108 Super tearDown need to be called as last message in tearDown of RGMethodDefinitionTest" Pull request url: https://github.com/pharo-project/pharo/pull/723 Issue Url: https://pharo.fogbugz.com/f/cases/21108 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #459: 21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #459 was: FAILURE. The Pull Request #724 was integrated: "21107 Super tearDown need to be called as last message in tearDown of RBRefactoringTest" Pull request url: https://github.com/pharo-project/pharo/pull/724 Issue Url: https://pharo.fogbugz.com/f/cases/21107 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #458: 20905-upToAll-for-ZnCharacterReadStream
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

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

1 0

[Pharo 7.0-dev] Build #457: 21121-Use-assertequals-in-TimespanTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

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

1 0

[Pharo 7.0-dev] Build #456: 20057-Autocomplete-crashes-for-trait-methods
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #456 was: SUCCESS. The Pull Request #707 was integrated: "20057-Autocomplete-crashes-for-trait-methods" Pull request url: https://github.com/pharo-project/pharo/pull/707 Issue Url: https://pharo.fogbugz.com/f/cases/20057 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #455: 21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 26, 2018

Jan. 26, 2018

There is a new Pharo build available! The status of the build #455 was: SUCCESS. The Pull Request #727 was integrated: "21104 Super tearDown need to be called as last message in tearDown of PNGReadWriterTest" Pull request url: https://github.com/pharo-project/pharo/pull/727 Issue Url: https://pharo.fogbugz.com/f/cases/21104 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo release moved to end of year
by Esteban Lorenzano Jan. 26, 2018

Jan. 26, 2018

Hi all, After some analysis of current condition of development, we decided to move the upcoming release to end of the year (and not May, as usual). The reason is that we are taking more time than expected to finish/polish a quantity of things that needs to be finish to call this a âsuccessful releaseâ to make us feel confortable with a release early this year. Thing isâ¦ we were very ambitious with this version, because a lot of small pieces get into position and we decided to act. Now, to deliver a good version, we need to finish them. For example, along with all the stabilisation phase we need to operate on P7 (an usual task for every version), we still need to finish this important changes: - fullblocks as default - vm 64bits: stabilise and add win64 - stateful traits - calypso (and nautilus removal) - iceberg: fix the UI We (the core team and the community) have a deep commitment with the progress of Pharo, and we will continue get things right to make the continue improvement a pleasant experience. Say that, expect new announcement of things finished and ready to test next weeks :) cheers! Esteban

6 6

Code Completion
by Myroslava Romaniuk Jan. 26, 2018

Jan. 26, 2018

Hi, I'm Myroslava Some of you might remember how last year I did GSoC and worked on Renraku / Quality Assistant with Yuriy. This year Stephane suggested several projects I could work on, and one of them is improving code completion in Pharo, in particular ecompletion. Could you recommend any resources that would help me better understand how it works? I'd also like to know what's the difference between ecompletion and ocompletion, and what's NOC and NEC completion, as it doesn't seem very clear to me so far? If any of you worked on it and can help me get started, I would really appreciate it. Thanks

3 2

[Ann] Calypso in progress: Spotter menu and settings
by Denis Kudriashov Jan. 25, 2018

Jan. 25, 2018

Hi, I just released new version of Calypso 0.8.11 which includes several fixes and new features. The most exiting feature is Spotter menu from Esteban https://youtu.be/RgqiSRFUAIk: "Spotter navigation" brings an easy way to access all available panels, > tabs and commands in selected browser. > Activation is usually cmd+/ (because is close to the arrows) Settings browser includes group for Calypso: - trait method visibility (enabled by default) - hierarchy order for variables (variable mode in full browser) - hierarchy order of method visibility classes (when expand first item in method groups pane) - shortcut for spotter menu. It is temporal solution until Commander will provide settings for all shortcuts in system. And few other improvements: - better status bar tool to change protocol and package - shortcut to change ineditor method protocol: $e meta , $t meta (editor + tag) - shortcut to change ineditor method package: $e meta, $p meta (editor + package) - inherited method group is replaced by all methods group with name "instance side" or "class side" depending on browser mode. It should make browser meta level more noticeable. Best regards, Denis

4 4