June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 26 Jun 2014, at 00:11, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > fantastic piece of work Sven, thanks for doing that for the community > > Is now on Reddit too: > http://www.reddit.com/r/programming/comments/293is3/rediscovering_the_ux_of… > > Vote up guys! Thanks Sebastian, I got lots of referrals from reddit.com ! I will do a short follow up after a week or so with some statistics, because I think this is important as well.

June 26, 2014

Re: [Pharo-dev] [Pharo-users] [Tutorial] Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator

by Sven Van Caekenberghe

On 25 Jun 2014, at 23:23, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This really is beautiful! > > Doru Thanks; like I said, this last year we seem to have this friendly competition in trying to produce the best possible documentation. Everyone's contributions, combined, will eventually make a difference, I am sure. > On Wed, Jun 25, 2014 at 3:29 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I have written a new, extensive, long form, introductory article about Pharo. > > Rediscovering the UX of the legendary HP-35 Scientific Pocket Calculator > > A tutorial on Pharo, test and specification based immersive programming > > https://medium.com/@svenvc/rediscovering-the-ux-of-the-legendary-hp-35-scie… > > > It is a bit different because > > - it is based on a non-trivial example > - it uses a backdrop story unrelated to Pharo > - it uses several multimedia elements > - it is published on medium.com which is a general publishing platform > > The appendix describes several ways you can get the code. I think building both a Spec and Seaside UI from the same specification as well as reusing functional tests in different contexts is cool. Anyway, I hope you enjoy it. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

I added a SLICE to https://pharo.fogbugz.com/f/cases/13395/Add-SHA256-HashFunction that adds the comment On 26 Jun 2014, at 08:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 26 Jun 2014, at 08:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 26 Jun 2014, at 08:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> I have not yet downloaded a latest image and tried it myself, but I do not understand why >>> >>> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >>> >>> fails, it does not fail in my working image (see my file out). >>> >>> That is the only problem left, the renaming is not necessary if this problem can be fixed. >>> >> >> Nautilus does not run the tests that are inherited (we should fix that). >> >> If you use the Testrunner, the test fails. > > I know. > >> It can be fixed by adding a class comment. > > I never publish anything without a class comment, it was there in the file out, SHA256.st > > I will have a look at the 40 image myself.

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

On 26 Jun 2014, at 08:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 26 Jun 2014, at 08:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> I have not yet downloaded a latest image and tried it myself, but I do not understand why >> >> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >> >> fails, it does not fail in my working image (see my file out). >> >> That is the only problem left, the renaming is not necessary if this problem can be fixed. >> > > Nautilus does not run the tests that are inherited (we should fix that). > > If you use the Testrunner, the test fails. I know. > It can be fixed by adding a class comment. I never publish anything without a class comment, it was there in the file out, SHA256.st I will have a look at the 40 image myself.

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Marcus Denker

On 26 Jun 2014, at 08:20, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I have not yet downloaded a latest image and tried it myself, but I do not understand why > > https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… > > fails, it does not fail in my working image (see my file out). > > That is the only problem left, the renaming is not necessary if this problem can be fixed. > Nautilus does not run the tests that are inherited (we should fix that). If you use the Testrunner, the test fails. It can be fixed by adding a class comment. Marcus

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

I have not yet downloaded a latest image and tried it myself, but I do not understand why https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… fails, it does not fail in my working image (see my file out). That is the only problem left, the renaming is not necessary if this problem can be fixed. On 26 Jun 2014, at 08:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 26 Jun 2014, at 08:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> I reopened https://pharo.fogbugz.com/f/cases/13395/Add-SHA256-HashFunction >> > > Why? i fixed that already yesterday (by renaming the class so the default worksâ¦) > > Is it important to re-name it again and add the #classToBeTested? > >> On 26 Jun 2014, at 07:45, stepharo <stepharo(a)free.fr> wrote: >> >>> no problem open a bug entry. >>> >>> Stef >>> >>> On 25/6/14 10:37, Sven Van Caekenberghe wrote: >>>> On 25 Jun 2014, at 10:06, no-reply(a)ci.inria.fr wrote: >>>> >>>>> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >>>>> >>>>> 5 regressions found. >>>>> Tests.System.Hashing.SHA256Tests.testClassComment >>>>> Tests.System.Hashing.SHA256Tests.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses >>>>> Tests.System.Hashing.SHA256Tests.testNew >>>>> Tests.System.Hashing.SHA256Tests.testTraitExplicitRequirementMethodsMustBeImplementedInTheClassOrInASuperclass >>>>> Tests.System.Hashing.SHA256Tests.testUnCategorizedMethods >>>> I didn't see that SHA256Tests subclassed ClassTestCase (I copied it from SHA1Test), this needs to be added in protocol 'coverage' of SHA256Tests, instance side: >>>> >>>> classToBeTested >>>> ^ SHA256 >>>> >>>> Sorry about that. >>>> >>>> Sven >>>> >>> >>> >> >> > >

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Marcus Denker

On 26 Jun 2014, at 08:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I reopened https://pharo.fogbugz.com/f/cases/13395/Add-SHA256-HashFunction > Why? i fixed that already yesterday (by renaming the class so the default worksâ¦) Is it important to re-name it again and add the #classToBeTested? > On 26 Jun 2014, at 07:45, stepharo <stepharo(a)free.fr> wrote: > >> no problem open a bug entry. >> >> Stef >> >> On 25/6/14 10:37, Sven Van Caekenberghe wrote: >>> On 25 Jun 2014, at 10:06, no-reply(a)ci.inria.fr wrote: >>> >>>> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >>>> >>>> 5 regressions found. >>>> Tests.System.Hashing.SHA256Tests.testClassComment >>>> Tests.System.Hashing.SHA256Tests.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses >>>> Tests.System.Hashing.SHA256Tests.testNew >>>> Tests.System.Hashing.SHA256Tests.testTraitExplicitRequirementMethodsMustBeImplementedInTheClassOrInASuperclass >>>> Tests.System.Hashing.SHA256Tests.testUnCategorizedMethods >>> I didn't see that SHA256Tests subclassed ClassTestCase (I copied it from SHA1Test), this needs to be added in protocol 'coverage' of SHA256Tests, instance side: >>> >>> classToBeTested >>> ^ SHA256 >>> >>> Sorry about that. >>> >>> Sven >>> >> >> > >

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

I reopened https://pharo.fogbugz.com/f/cases/13395/Add-SHA256-HashFunction On 26 Jun 2014, at 07:45, stepharo <stepharo(a)free.fr> wrote: > no problem open a bug entry. > > Stef > > On 25/6/14 10:37, Sven Van Caekenberghe wrote: >> On 25 Jun 2014, at 10:06, no-reply(a)ci.inria.fr wrote: >> >>> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >>> >>> 5 regressions found. >>> Tests.System.Hashing.SHA256Tests.testClassComment >>> Tests.System.Hashing.SHA256Tests.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses >>> Tests.System.Hashing.SHA256Tests.testNew >>> Tests.System.Hashing.SHA256Tests.testTraitExplicitRequirementMethodsMustBeImplementedInTheClassOrInASuperclass >>> Tests.System.Hashing.SHA256Tests.testUnCategorizedMethods >> I didn't see that SHA256Tests subclassed ClassTestCase (I copied it from SHA1Test), this needs to be added in protocol 'coverage' of SHA256Tests, instance side: >> >> classToBeTested >> ^ SHA256 >> >> Sorry about that. >> >> Sven >> > >

June 26, 2014

Re: [Pharo-dev] evicted zombie process from run queue

by stepharo

Hi hernan Which image? What did you loaded? Can you reproduce it? > Can someone explain what does it mean or why it happens? > Is that a common scenario for you? > > I am measuring execution time for big matrices in CogVM 4.0.0. Image > is unresponsive. > > Cheers, > > HernÃ¡n >

June 26, 2014

Re: [Pharo-dev] [regression reporter]regression occurred

by stepharo

no problem open a bug entry. Stef On 25/6/14 10:37, Sven Van Caekenberghe wrote: > On 25 Jun 2014, at 10:06, no-reply(a)ci.inria.fr wrote: > >> https://ci.inria.fr/pharo/job/Pharo-4.0-Update-Step-2.1-Validation-M-Z/labe… >> >> 5 regressions found. >> Tests.System.Hashing.SHA256Tests.testClassComment >> Tests.System.Hashing.SHA256Tests.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses >> Tests.System.Hashing.SHA256Tests.testNew >> Tests.System.Hashing.SHA256Tests.testTraitExplicitRequirementMethodsMustBeImplementedInTheClassOrInASuperclass >> Tests.System.Hashing.SHA256Tests.testUnCategorizedMethods > I didn't see that SHA256Tests subclassed ClassTestCase (I copied it from SHA1Test), this needs to be added in protocol 'coverage' of SHA256Tests, instance side: > > classToBeTested > ^ SHA256 > > Sorry about that. > > Sven >

June 26, 2014