- Pharo-dev - lists.pharo.org

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

Exception in Iceberg when removing selectors from anonymous classes

by Steven Costiou

Hi, i downloaded yesterday the latest Pharo 7 and in a playground if you do: class := Object newAnonymousSubclass. (OK) class package. "a RPackage(_UnpackagedPackage)" (OK) class compile: 'test ^nil'. (OK) (class >> #test) package. "nil" (Surprising but no problem with any pharo version since yesterday) class removeSelector: #test. (Exception, see below) An exception is raised in IceSystemEventListener class because the method package is nil: handlePackagesChange: packages IceRepository registry do: [ :repository | | changed | changed := packages anySatisfy: [ :each | repository notifyPackageModified: each name ]. "(EACH IS NIL HERE)" changed ifTrue: [ Iceberg announcer announce: (IceRepositoryModified for: repository) ]] So to fix it, the package needs to be correctly set for each method compiled in an anonymous class, but should anonymous subclasses really raise events when adding/modifying/removing methods? Steven.

April 19, 2018

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

by Stephan Eggermont

Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > And please support the use of baselines. Nobody wants to also mantain a > ConfigurationOf just for the catalog when using baselines. That sounds like a non-problem. One file that never needs to change. Letâs solve the problems first Stephan

April 19, 2018

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

by Esteban Lorenzano

> On 19 Apr 2018, at 11:25, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > And please support the use of baselines. Nobody wants to also mantain a ConfigurationOf just for the catalog when using baselines. thatâs IMO the most important part we need to cover. Esteban > > On Thu, Apr 19, 2018, 05:58 Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > I also think that the catalog is important. If anything is wrong with it we should fix it. > > The problem is that the catalog is never working well with the current unstable version of Pharo (today 7). Not all package developers take the trouble of checking/porting all the time, that is perfectly understandable. > > Moving the catalog to GitHub with a STON meta description is a good idea, of course. All we need is a clean object representing the meta info, the rest comes for free. > > > On 19 Apr 2018, at 10:38, Torsten Bergmann <astares(a)gmx.de <mailto:astares@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 <mailto:stepharo.self@gmail.com>> > >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > >> Betreff: [Pharo-dev] Do we kill the catalog? > >> > >> Hi guys > >> > >> What do we do with it? > >> What alternatives? > >> > >> Stef > >> > >> > > > >

April 19, 2018

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

by Gabriel Cotelli

And please support the use of baselines. Nobody wants to also mantain a ConfigurationOf just for the catalog when using baselines. On Thu, Apr 19, 2018, 05:58 Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I also think that the catalog is important. If anything is wrong with it > we should fix it. > > The problem is that the catalog is never working well with the current > unstable version of Pharo (today 7). Not all package developers take the > trouble of checking/porting all the time, that is perfectly understandable. > > Moving the catalog to GitHub with a STON meta description is a good idea, > of course. All we need is a clean object representing the meta info, the > rest comes for free. > > > On 19 Apr 2018, at 10:38, 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 19, 2018

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

by Thierry Goubier

2018-04-19 10:57 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I also think that the catalog is important. If anything is wrong with it we should fix it. I agree. Issues: - The Catalog doesn't use Metacello, so things loaded via the catalog are not registered properly (upgrades / conflicts) - The Catalog mix multiple Meta repos and you never know, given a configuration in multiple repos, which one the Catalog is giving you. - The Catalog icons are ... non understandable. > The problem is that the catalog is never working well with the current unstable version of Pharo (today 7). Not all package developers take the trouble of checking/porting all the time, that is perfectly understandable. Never tried that one > Moving the catalog to GitHub with a STON meta description is a good idea, of course. All we need is a clean object representing the meta info, the rest comes for free. Maybe. I would like a automated way of extracting the json from a baseline or configuration... to reduce the friction of using the catalog. Thierry >> On 19 Apr 2018, at 10:38, 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 19, 2018

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

by Ben Coman

On 19 April 2018 at 15:38, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> I am doing a pass to cleanup the DelayScheduler hierarchy. >> I'll be refactoring of the hierarchy to aid code understanding >> and eliminate redundant instance variables from the original code. >> The target structure is.... >> DelayNullScheduler -- minimum interface to avoid errors in rest of system >> (6 empty methods) >> |__DelayBasicScheduler -- fully working sans race protection (equivalent >> to Courageous scheduler) >> |__DelaySpinScheduler -- plus race protection >> >> Can someone advise how/where the Bootstrap loads Delay and the >> DelaySchedulers? >> > > Delay and Delay schedulers are atomically loaded during bootstrap (because > they are part of the Kernel package so far). > So there should be nothing special to do there. > > >> where the invocation of Delay_class>>#initialize selects the delay >> scheduler. >> > > Once the image is created, the first method invoked is > > PharoBootstrapInitialization >> initializeCommandLineHandlerAn > dErrorHandling > > which is in the image. You can change it as you please :). > > >> I need to determine whether during transition the Bootstrap might need to >> temporarily hop to a different scheduler, >> and how to provide the new structure in the Image for operational testing >> before switching. >> > > In the bootstrap there is no "switching". A new image is created from > scratch with the code that you provide... > Initially the image has no delay scheduler process, so calling `Delay > class initialize` will create it for you. > > So as soon as you define > > Delay class >> initialize > "Delay initialize" > Scheduler ifNotNil: [ Scheduler stopTimerEventLoop ]. > Scheduler := *MyNewScheduler new*. > Scheduler startTimerEventLoop. > SessionManager default > registerSystemClassNamed: self name > atPriority: 20. > > The bootstrap will take it into account. > I had hoped it would be something simple like that. Thanks for confirming. > And tests will be run with that configuration. > > Maybe there is something else to it? > You want to do test the switching also? Because for this I would do it > with normal smalltalk code... no bootstrap involved... > > >> >> cheers -ben >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

April 19, 2018

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

by Sven Van Caekenberghe

I also think that the catalog is important. If anything is wrong with it we should fix it. The problem is that the catalog is never working well with the current unstable version of Pharo (today 7). Not all package developers take the trouble of checking/porting all the time, that is perfectly understandable. Moving the catalog to GitHub with a STON meta description is a good idea, of course. All we need is a clean object representing the meta info, the rest comes for free. > On 19 Apr 2018, at 10:38, 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 19, 2018