- Pharo-dev - lists.pharo.org

learning about ClassTestCase

by Ben Coman

I bumped into ClassTestCase for the first time, with class comment... "This class is intended for unit tests of individual classes and their metaclasses. It provides methods to determine the coverage of the unit tests. Subclasses are expected to re-implement: #classesToBeTested and #selectorsToBeIgnored. They should also implement to confirm that all methods have been tested. #testCoverage super testCoverage. " A few questions to improve my knowledge of how to use this... a. there are no implementors of #classesToBeTested but several of #classToBeTested. I presume the class comment is wrong? b. there are no implementors of #testCoverage, so I presume I can ignore that? (and I've no example to work from) c. ClassTestCase is subclassed 73 times, but #selectorsToBeIgnored is only implemented 9 times. So this seems not critical? But btw, every of those at least ignores #printOn:. I'm curious why? These are tagged "private", but is that a good reason not to test it? My purpose was to add a new class MagnitudeTest for a new new method to Magnitude in response to the recent #min:max: discussion. cheers -ben

April 22, 2018

Re: [Pharo-dev] what is demote?

by Stephane Ducasse

Excellent! Thanks! :) On Sat, Apr 21, 2018 at 7:57 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > CyrilFerlicot wrote >> It's probably to change a package of the form "MyPackage-Something" to a >> package "MyPackage" with a "Something" tag. > > Yes, breakpoint triggered from Calypso "Demote to package with tag" context > menu. > > Maybe the message name could be improved tooâ¦ #demoteToTagInPackageNamed:? > Also, maybe there should be a guard if `aString = self name`? > > https://github.com/pharo-project/pharo/pull/1240 > > I don't want to be accused of talking without action ;-) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

April 21, 2018

Re: [Pharo-dev] what is demote?

by Sean P. DeNigris

CyrilFerlicot wrote > It's probably to change a package of the form "MyPackage-Something" to a > package "MyPackage" with a "Something" tag. Yes, breakpoint triggered from Calypso "Demote to package with tag" context menu. Maybe the message name could be improved tooâ¦ #demoteToTagInPackageNamed:? Also, maybe there should be a guard if `aString = self name`? https://github.com/pharo-project/pharo/pull/1240 I don't want to be accused of talking without action ;-) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 21, 2018

Re: [Pharo-dev] How to build current VM

by Cyril Ferlicot

On sam. 21 avr. 2018 at 16:30, phideaux <jcasler(a)cdix.org> wrote: > I am trying to build a Pharo VM on Linux using the opensmalltalk vm git. I > just want to make sure I can reproduce the current system before > tinkering. > > I cloned the git and built the linux64x64/pharocog threaded vm (using > ./msm). The build runs fine but the vm produced when started with a current > (6.1) image says (in debug log) "vm too old for image" I have verified that > the vm level of the source in the git is the same as the latest vm > downloadable from files.pharo..org (VMMaker.oscog-eem.2361). What > additional > parameters do I need to produce a vm that matches the current latest/stable > that is 6.0/61 compatible? > Hello, Your VM is missing some metadatas. To get them execute ./scripts/updateSCCSVersions Then recompile the VM. Note that your compiled VM will still work. > Thanks in advance. > Jay+ > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > -- Cyril Ferlicot https://ferlicot.fr

April 21, 2018

How to build current VM

by phideaux

I am trying to build a Pharo VM on Linux using the opensmalltalk vm git. I just want to make sure I can reproduce the current system before tinkering. I cloned the git and built the linux64x64/pharocog threaded vm (using ./msm). The build runs fine but the vm produced when started with a current (6.1) image says (in debug log) "vm too old for image" I have verified that the vm level of the source in the git is the same as the latest vm downloadable from files.pharo..org (VMMaker.oscog-eem.2361). What additional parameters do I need to produce a vm that matches the current latest/stable that is 6.0/61 compatible? Thanks in advance. Jay+ -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 21, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Stephane Ducasse

Torsten Sometimes you should relax. Because if you remember I pushed the catalog (in fact I love it and we need a much more powerful one) and I even improved it. I made it better to automatically add MC repositories. Of course Thierry is exagerating. Now we should fix or remove it. Simple no? Now you can rant in your corner thinking that I'm asshole. This is ok for me. Stef On Sat, Apr 21, 2018 at 3:06 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Even there is no learning from the past - it's deja vu all over again... > > >> Gesendet: Freitag, 20. April 2018 um 08:53 Uhr >> Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] Do we kill the catalog? >> >> Hi torsten >> >> the wise shows the moon, the idiot sees his finger. >> >> Stef >> >> >> On Thu, Apr 19, 2018 at 10:38 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >> > Now today you had loading trouble with Smacc from Catalog ... and now directly want to >> > kill catalog. Wow! >> > >> > Sometimes I have the impression that our community tries to reinvent itself each day >> > doing it differently (but not only better) instead of extending, improving and supporting >> > what we have have done before. Which sometimes is good ... but not always. >> > >> > Thx >> > T. >> > >> >> Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr >> >> Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> >> Betreff: [Pharo-dev] Do we kill the catalog? >> >> >> >> Hi guys >> >> >> >> What do we do with it? >> >> What alternatives? >> >> >> >> Stef >> >> >> >> >> > >> >> >

April 21, 2018

Re: [Pharo-dev] Spotter search in Catalog ?

by Stephane Ducasse

You see I coded in aeroport and train all yesterday. So if we could detect that the network is not available then it would be a game changer. On Sat, Apr 21, 2018 at 1:04 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 21 Apr 2018, at 10:37, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Guys just to tell my experience last week in Algeria. >> Students were super motivated. Some even did the mooc before I came. >> And we got some of them playing with Bloc and others. >> Now none of the students or teachers at university got internet. Oh >> yes they have it on their mobile phone. > > And that makes us look silly to the rest of the dev world. > I know it is a conflict. > I've got an idea/POC on how to solve this, but I did not yet come around to making it clean for inclusion in Pharo. > >> Stef >> >> >> >> >> >> >> >> >> On Sat, Apr 21, 2018 at 10:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> There is a "Display catalog projects in Spotterâ setting. It is unselected by default because people with slow internet connection had issues with it. >>> >>> Cheers, >>> Doru >>> >>> >>>> On Apr 21, 2018, at 9:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Hi, >>>> >>>> Do we have a Spotter extension/plugin that searches in the Catalog (meta data, descriptions) ? >>>> >>>> I though that would be really cool and help in discovering packages/frameworks. >>>> >>>> Sven >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> âThe smaller and more pervasive the hardware becomes, the more physical the software gets." >>> >>> >> > >

April 21, 2018

Re: [Pharo-dev] Do we kill the catalog?

by Torsten Bergmann

Even there is no learning from the past - it's deja vu all over again... > Gesendet: Freitag, 20. April 2018 um 08:53 Uhr > Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Do we kill the catalog? > > Hi torsten > > the wise shows the moon, the idiot sees his finger. > > Stef > > > On Thu, Apr 19, 2018 at 10:38 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Now today you had loading trouble with Smacc from Catalog ... and now directly want to > > kill catalog. Wow! > > > > Sometimes I have the impression that our community tries to reinvent itself each day > > doing it differently (but not only better) instead of extending, improving and supporting > > what we have have done before. Which sometimes is good ... but not always. > > > > Thx > > T. > > > >> Gesendet: Donnerstag, 19. April 2018 um 08:42 Uhr > >> Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> > >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > >> Betreff: [Pharo-dev] Do we kill the catalog? > >> > >> Hi guys > >> > >> What do we do with it? > >> What alternatives? > >> > >> Stef > >> > >> > > > >

April 21, 2018

Re: [Pharo-dev] Spotter search in Catalog ?

by Sven Van Caekenberghe

> On 21 Apr 2018, at 10:37, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Guys just to tell my experience last week in Algeria. > Students were super motivated. Some even did the mooc before I came. > And we got some of them playing with Bloc and others. > Now none of the students or teachers at university got internet. Oh > yes they have it on their mobile phone. And that makes us look silly to the rest of the dev world. I know it is a conflict. I've got an idea/POC on how to solve this, but I did not yet come around to making it clean for inclusion in Pharo. > Stef > > > > > > > > > On Sat, Apr 21, 2018 at 10:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> Hi, >> >> There is a "Display catalog projects in Spotterâ setting. It is unselected by default because people with slow internet connection had issues with it. >> >> Cheers, >> Doru >> >> >>> On Apr 21, 2018, at 9:10 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi, >>> >>> Do we have a Spotter extension/plugin that searches in the Catalog (meta data, descriptions) ? >>> >>> I though that would be really cool and help in discovering packages/frameworks. >>> >>> Sven >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âThe smaller and more pervasive the hardware becomes, the more physical the software gets." >> >> >

April 21, 2018

Re: [Pharo-dev] what is demote?

by Cyril Ferlicot

On sam. 21 avr. 2018 at 10:12, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > demoteToRPackageNamed: aString > | newRPackage | > > self unregister. > newRPackage := self class organizer > packageNamed: aString > ifAbsent: [ (self class named: aString) register ]. > newRPackage importPackage: self. > newRPackage classes do: [ :each | > SystemAnnouncer uniqueInstance > classRepackaged: each > from: self > to: newRPackage ]. > > of course no comment because everything is obvious in Pharo, isn't? > > Hi, It's probably to change a package of the form "MyPackage-Something" to a package "MyPackage" with a "Something" tag. -- Cyril Ferlicot https://ferlicot.fr

April 21, 2018