- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #407: 20920 RPackageOrganizer should use packageClass instead of RPackage references
by ci-pharo-ci-jenkins2＠inria.fr Jan. 4, 2018

Jan. 4, 2018

There is a new Pharo build available! The status of the build #407 was: FAILURE. The Pull Request #648 was integrated: "20920 RPackageOrganizer should use packageClass instead of RPackage references" Pull request url: https://github.com/pharo-project/pharo/pull/648 Issue Url: https://pharo.fogbugz.com/f/cases/20920 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

How to restore image upgrade? was New Year Wishlist (2018) ?
by Nicolas Cellier Jan. 4, 2018

Jan. 4, 2018

2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > My four wishes, in no particular order: > - Better code completion > - Git in Pharo as easy as using Git for other languages > The recipe is easy: turn pharo into a file based edit-compile-run language and expunge those live object burden ;) Let me explain why it's not just trolling. Currently we have to download an image made by a bot. Pharo has gradually lost the power to upgrade the image (it's not new). If we recognize that an image acts like a workspace, and want to let the pull/branch switch/etc work again... IOW going from one point to any other in source code graph and experience the full power of git like any other language, that means, in a live IDE, at least solving those two problems: - changing the tools that are used to upgrade the image (Compiler, MethodDictionary, Array, etc...) - correctly initialize all the states (including stange loops) If pharo has not managed to solve this with a linear one way history (the regularly broken update image option), how do you think this is going to be solved in the more general case? I call this the universal boostrap problem. IMO the logical next step is to separate the IDE (the Inanimate Desintegrated Environment of any other language). Maybe we don't have to bend Pharo too much to git if it does not fit. The goal: as easy might be not that easy. - Bloc on Steroid > - Being able to interrupt any process and endless loop using Cmd-. > > Merry Christmas to all of you! > Alexandre > > > > > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > Hi everybody, > > > > This looks like a good moment of the year to ask all of you what would > you want to see in Pharo next year. > > Features, improvements, radical changes, etcâ¦. whatever you want. > > > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > > > So, letâs those wishes come! > > > > cheers, > > Esteban > > >

4 5

Replacement for deprected MultiByteFileStream?
by Bernhard Pieber Jan. 4, 2018

Jan. 4, 2018

I just saw that the FileStream hierarchy including MultiByteFileStream is deprecated. However, I can't find what file stream class should be used to read a UTF-8 encoded file instead. FileReference>>#readStreamDo: also uses MultiByteFileStream. Can someone please point me to the right code? Bernhard

7 15

about copyAllTo:
by Stephane Ducasse Jan. 3, 2018

Jan. 3, 2018

Hi I have the gut feeling that copyAllTo: is not really nice because unclear. The comments are unclear on the "flattening" It is unclear that it flattens the leaves or not. I mean A B x C D y z A copyAllTo: K do we get K B x C D y z or K x y z We got touched by such difference and the message name is not enough intention revealing. I would prefer a message copyAsSuchTo: copyLeavesTo: What do you think? Stef

1 0

[Pharo 7.0-dev] Build #406: 20911 Cleanup MCClassDefinitionTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

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

1 0

[Pharo 7.0-dev] Build #405: 20918 Super setUp need to be called in Collections-Tests
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

There is a new Pharo build available! The status of the build #405 was: SUCCESS. The Pull Request #642 was integrated: "20918 Super setUp need to be called in Collections-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/642 Issue Url: https://pharo.fogbugz.com/f/cases/20918 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #404: 20922-Update-Iceberg-to-v066
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

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

1 0

[Pharo 7.0-dev] Build #403: Categorize methods in MCMczInstallerTest
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

There is a new Pharo build available! The status of the build #403 was: FAILURE. The Pull Request #636 was integrated: "Categorize methods in MCMczInstallerTest" Pull request url: https://github.com/pharo-project/pharo/pull/636 Issue Url: https://pharo.fogbugz.com/f/cases/20910 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #402: 20917-Super-setUp-need-to-be-called-in-Debugger-Tests
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

There is a new Pharo build available! The status of the build #402 was: SUCCESS. The Pull Request #641 was integrated: " 20917-Super-setUp-need-to-be-called-in-Debugger-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/641 Issue Url: https://pharo.fogbugz.com/f/cases/20917 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #401: 20914-remove-remaining-halt
by ci-pharo-ci-jenkins2＠inria.fr Jan. 3, 2018

Jan. 3, 2018

There is a new Pharo build available! The status of the build #401 was: FAILURE. The Pull Request #639 was integrated: "20914-remove-remaining-halt" Pull request url: https://github.com/pharo-project/pharo/pull/639 Issue Url: https://pharo.fogbugz.com/f/cases/20914 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0