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

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

by Stephane Ducasse

The underlying questions (sorry for people that need subtitles) are: - how do we have a central place to declare projects - right now in Smalltalkhub/list is a nice way to find projects with the move to github we should get a central place Christophe has been working on project repository and we should check what he has. @Christophe? - how do we make sure that we can validated (I can load this version of XMLParser in that version of Pharo) -- in this version of Pharo what is the latest working version of this package - if people do not maintain/add "configuration" into the catalog what is the point? -- How can we ease the participation to the catalog? Esteban I do not care about the format. Do you think that editing STON is easier than a class? I think that we should have a button. Look people do not care about posting their project into the repo. May be we need a crawler? @Peter no cargo is not dead now christophe cannot fix all the time the PharoLauncher and make progress on Cargo -> Pakbot And yes I really want to have something that we can use soon. - Needed immediate actions: -- support baselineOf -- how could we make sure that we can publish in multiple repo? (After this is just a copy so I click on the package and say copy to). What else. @thierry the story I do not use the catalog because the icons are not understandable is not really good to me. Stef On Thu, Apr 19, 2018 at 8:46 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > why to kill it? > right now we do not have a replacement. > > Esteban > >> On 19 Apr 2018, at 08:42, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi guys >> >> What do we do with it? >> What alternatives? >> >> Stef >> > >

April 20, 2018

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

by Stephane Ducasse

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 20, 2018

Re: [Pharo-dev] Hierarchy (roots) of package

by Stephane Ducasse

Thanks Eliot. On Thu, Apr 19, 2018 at 3:06 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi ClÃ©ment, > > > On Apr 18, 2018, at 11:45 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > I would do that: > > Implementation: > rootsInsidePackage := [ :packageName | > | myPackage | > myPackage := RPackageOrganizer default packageNamed: packageName. > myPackage definedClasses select: [ :each | each superclass package ~~ > myPackage ] ]. > > > Don't forget nil superclasses (for proxy classes) so > > each superclass isNil > or: [ each superclass package ~~ myPackage ] ] > > > Example use-case: > rootsInsidePackage value: 'OpalCompiler-Core' > > Is that what you expected ? > > On Thu, Apr 19, 2018 at 7:19 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi >> >> Given a package I would like to know the classes that are roots >> of hierarchy inside the package. >> >> Do we have something like that? >> >> Stef >> > > > > -- > ClÃ©ment BÃ©ra > https://clementbera.github.io/ > https://clementbera.wordpress.com/

April 20, 2018

Re: [Pharo-dev] Hierarchy (roots) of package

by Stephane Ducasse

Thanks ClÃ©ment this is a nice way to do it. I was thinking about a more complex solution. Tx! On Thu, Apr 19, 2018 at 8:45 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > I would do that: > > Implementation: > rootsInsidePackage := [ :packageName | > | myPackage | > myPackage := RPackageOrganizer default packageNamed: packageName. > myPackage definedClasses select: [ :each | each superclass package ~~ > myPackage ] ]. > > Example use-case: > rootsInsidePackage value: 'OpalCompiler-Core' > > Is that what you expected ? > > On Thu, Apr 19, 2018 at 7:19 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi >> >> Given a package I would like to know the classes that are roots >> of hierarchy inside the package. >> >> Do we have something like that? >> >> Stef >> > > > > -- > ClÃ©ment BÃ©ra > https://clementbera.github.io/ > https://clementbera.wordpress.com/

April 20, 2018

Re: [Pharo-dev] [ANN] Pharo Sprint Apr 20

by Marcus Denker

This is tomorrow. > On 13 Apr 2018, at 14:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Pharo Sprint Apr 20 > > https://association.pharo.org/event-2789579 > > We will organize a Pharo sprint / Moose dojo Apr 20 , starting at > 10:00am. (Local Time Paris). > > Goals of this sprint: > > â¢ Pharo 7 issues > > Remote Sprint > Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: > > > Known Local Sprint meetings > > Lille/France: > It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come > >

April 19, 2018

Re: [Pharo-dev] Slot Questions

by Sean P. DeNigris

Sean P. DeNigris wrote > Question #4: > Given: > Object subclass: #MyClass > slots: { #var1 => MySlot } > classVariables: { } > category: '' > and > MyClass >>#var1: anObject > var1 := anObject > MySlot>#write:to: doesn't seem to be sent when I `myClassInstance var1: > 2`. > I tried to insert a halt, 1 inspect, etc. I am able to intercept #read: on > the other hand All issues from this thread seem to be resolved in latest Pharo 7, except the above. This seems like a bug if IIUC. Can anyone confirm? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 19, 2018

Re: [Pharo-dev] [Pharo-users] [Pharo-Launcher] call for tests on Windows

by Richard Sargent

The good news is that the same version of Pharo Launcher worked essentially perfectly under Windows 10. As expected, the launcher was installed in AppData\Local. However, I continue to find an AppData\Roaming\pharo directory created when the launcher was installed. Its contents are as I described in the issue created for the Windows 7 installation. Suggestion: Some of the lists are quite long. It might be useful to be able to sort them by e.g. name or date of last change, both ascending and descending. On Mon, Apr 16, 2018 at 9:54 AM, Richard Sargent < richard.sargent(a)gemtalksystems.com> wrote: > I ran the launcher against my Windows 7 office computer and have created > an issue with my feedback. > https://github.com/pharo-project/pharo-launcher/issues/93 > > > > On Mon, Apr 16, 2018 at 7:13 AM, Christophe Demarey < > christophe.demarey(a)inria.fr> wrote: > >> Hi, >> >> Regarding the various problems Pharo Launchers had on Windows, we worked >> on a new installer based on Advanced Installer [1] to avoid UAC (User >> Account Control) and write permissions problems. This new installer now >> installs Pharo Launcher in the userâs local app data folder (where for >> sure, he has write permissions). Pharo Launcher also now have its own icon >> and use its own name instead of Pharo. Also, the uninstaller now works as >> expected. Last but not least, the installer is now signed to avoid warning >> of Windows Defender. >> Thanks to Ben Coman who did the first version of the packaging using >> Advanced Installer (was NSIS). >> This version should also improve the launch of Pharo images on Windows. >> >> So, please could you install and test this new version: and report any >> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ >> We do not have windows users around so itâs hard to know if it works >> outside our tests boxes. >> >> Thanks, >> Christophe >> >> [1] https://www.advancedinstaller.com/ >> > >

April 19, 2018

Re: [Pharo-dev] Slot Questions

by Sean P. DeNigris

Sean P. DeNigris wrote > Another issue: > Changing the slots in the template from "{ #var1 => MySlot adjustment: 10 > }" > to "{ #var1 => MySlot adjustment: 100 }" has no effect unless I accept an > intermediate "{ #var1 }" Fixed by https://pharo.fogbugz.com/f/cases/21725/ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

April 19, 2018

Re: [Pharo-dev] Hierarchy (roots) of package

by Eliot Miranda

Hi ClÃ©ment, > On Apr 18, 2018, at 11:45 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > I would do that: > > Implementation: > rootsInsidePackage := [ :packageName | > | myPackage | > myPackage := RPackageOrganizer default packageNamed: packageName. > myPackage definedClasses select: [ :each | each superclass package ~~ myPackage ] ]. Don't forget nil superclasses (for proxy classes) so each superclass isNil or: [ each superclass package ~~ myPackage ] ] > > Example use-case: > rootsInsidePackage value: 'OpalCompiler-Core' > > Is that what you expected ? > >> On Thu, Apr 19, 2018 at 7:19 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Hi >> >> Given a package I would like to know the classes that are roots >> of hierarchy inside the package. >> >> Do we have something like that? >> >> Stef >> > > > > -- > ClÃ©ment BÃ©ra > https://clementbera.github.io/ > https://clementbera.wordpress.com/

April 19, 2018

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

by Peter UhnÃ¡k

> What do we do with it? > What alternatives? > Stef Is Cargo dead? I thought that was supposed to be the alternative. > That sounds like a non-problem. One file that never needs to change. Letâs > solve the problems first > How so? If I want for the catalog to load a specific version of Git(Hub) project, then I need to specify a tag. Which means every time I make a new release, I need to update the configuration. At least this is how I saw other people were addressing it. Peter

April 19, 2018