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

Re: [Pharo-dev] Blame support P7

by Nicolas Cellier

2018-01-12 21:23 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > Donât you think having Author and timestamps is important? > Glad to see Pharo Community waking up :) I felt a bit alone since I complained about that in last November ('about SortFunctions' thread) > > Am 12.01.2018 um 10:26 schrieb Stephane Ducasse <stepharo.self(a)gmail.com > >: > > > > Hi torsten > > > > we have a super long list of *important* fixes and enhancements to do. > > > > Stef > > > >> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> > wrote: > >> Not having timestamps/authors in Pharo 7 due to git and missing blame > support > >> (see [1]) has other bad side effects: > >> > >> > >> - it clobbers all method stamps in an MCZ package [1] if you use > Monticello > >> which can lead easily to trouble/lamenting > >> > >> - it is not possible to fileout a changeset [2] in the ChangeSorter > >> > >> Was there any further discussion/decision for P7 on solving this > >> or adding blame support? > >> > >> Thx > >> T. > >> > >> > >> [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html > >> [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018- > January/026350.html > >> [3] https://pharo.fogbugz.com/f/cases/20951/ > >> > >

Jan. 12, 2018

[Pharo 7.0-dev] Build #423: SUCCESS

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

There is a new Pharo build available! The status of the build #423 was: SUCCESS. Could not extract further issue information from commit message: https://pharo.fogbugz.com/f/cases/20913/ Ok now the cascades are not introduced. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

Re: [Pharo-dev] Blame support P7

by Norbert Hartl

Donât you think having Author and timestamps is important? > Am 12.01.2018 um 10:26 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hi torsten > > we have a super long list of *important* fixes and enhancements to do. > > Stef > >> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >> Not having timestamps/authors in Pharo 7 due to git and missing blame support >> (see [1]) has other bad side effects: >> >> >> - it clobbers all method stamps in an MCZ package [1] if you use Monticello >> which can lead easily to trouble/lamenting >> >> - it is not possible to fileout a changeset [2] in the ChangeSorter >> >> Was there any further discussion/decision for P7 on solving this >> or adding blame support? >> >> Thx >> T. >> >> >> [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html >> [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html >> [3] https://pharo.fogbugz.com/f/cases/20951/ >>

Jan. 12, 2018

ZnClient issue: ZdcPlugin Missing

by Photon

Hello, I was just following along this book: and it told me to get some data via ZnClient like this, I tried them both with a dot inbetween and independantly like in the picture below. Does someone got an idea what`s wrong? <http://forum.world.st/file/t371759/ZnClient_issue.png> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 12, 2018

[Pharo 7.0-dev] Build #422: 20949 Use category "utilities" instead of "utils" in TheManifestBuilder

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

There is a new Pharo build available! The status of the build #422 was: SUCCESS. The Pull Request #665 was integrated: "20949 Use category "utilities" instead of "utils" in TheManifestBuilder" Pull request url: https://github.com/pharo-project/pharo/pull/665 Issue Url: https://pharo.fogbugz.com/f/cases/20949 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

[Pharo 7.0-dev] Build #421: Add Shift class builder, Tonel and other improvements to Welcome changeLog

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

There is a new Pharo build available! The status of the build #421 was: SUCCESS. The Pull Request #668 was integrated: "Add Shift class builder, Tonel and other improvements to Welcome changeLog" Pull request url: https://github.com/pharo-project/pharo/pull/668 Issue Url: https://pharo.fogbugz.com/f/cases/20955 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

[ANN] Dates Pharo Sprints 2018 till June

by Marcus Denker

Hi, For Pharo sprints for the next months, we suggest these dates: Jan 26 Feb 23 Mar 30 Apr 20 Mai 25 Jun 29 I have added the first one already to the events page: https://association.pharo.org/events <https://association.pharo.org/events> the others will be added later. Marcus

Jan. 12, 2018

[Pharo 7.0-dev] Build #420: Updated Fuel to 2.2.0 with the 64 bit adaptations

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

There is a new Pharo build available! The status of the build #420 was: SUCCESS. The Pull Request #654 was integrated: "Updated Fuel to 2.2.0 with the 64 bit adaptations" Pull request url: https://github.com/pharo-project/pharo/pull/654 Issue Url: https://pharo.fogbugz.com/f/cases/20120 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

[Pharo 7.0-dev] Build #419: 20947-NautilusRefactoring-package-should-not-depends-on-Nautilus-package

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

There is a new Pharo build available! The status of the build #419 was: SUCCESS. The Pull Request #663 was integrated: "20947-NautilusRefactoring-package-should-not-depends-on-Nautilus-package" Pull request url: https://github.com/pharo-project/pharo/pull/663 Issue Url: https://pharo.fogbugz.com/f/cases/20947 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 12, 2018

Re: [Pharo-dev] Hello, Im and a litle confused. Can you help me get started please?

by Stephane Ducasse

Since the syntax of pharo is heavly based on messages, it is important for you to spot them. Stef On Thu, Jan 11, 2018 at 1:58 PM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > Hi, > > >> Le 11 janv. 2018 Ã 11:35, Photon <nico-braun(a)live.de> a Ã©crit : >> >> oh yes I allready started with the book as I decided that it looked the most >> usefull and complete of the available material online. I did not know that >> you wrote it. TDD is a fun topic aswell. >> I have a little question tho. Am I supossed to know all the answers in >> Chapter 3 challenges? Should I redo chapter 1-2 untill I know all the >> answers? > > I think you should be able to answer most questions of the chapter 3 before going further. > Be able to identify messages, literals and evaluating basic expressions is really important. If you only miss a few answers, it is not a big deal. They will come with experience. > My advice would be to not only re-read the book but use Pharo playground / inspector in the same time to try the examples and find out similar ones. > > Regards, > Christophe

Jan. 12, 2018