March 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Member: CIRAD

by Serge Stinckwich

On Mon, Mar 11, 2019 at 10:03 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > > On 11 Mar 2019, at 04:24, askoh <askoh(a)askoh.com> wrote: > > > > It would be very interesting if there is a list showing what each > consortium > > member uses Pharo or Smalltalk for. > > Sadly, thatâs not really possible :( > While many members have no problem on freely talk about what they do, > others do not have same approach :) > > Yes I guess this is difficult for some members to be explicit about what they are doing with Pharo. For CIRAD, I can say that they use Smalltalk for their multi-agent modeling platform : http://cormas.cirad.fr/indexeng.htm There is an ongoing work to port CORMAS from VW to Pharo: https://github.com/cormas/cormas Regards, -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

March 11, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 4 March 2019

by Esteban Lorenzano

> On 11 Mar 2019, at 11:39, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Mon, 11 Mar 2019 at 15:00, <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hello! > > This is my weekly ChangeLog, from 4 March 2019 to 10 March 2019. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019 <http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019> > > ChangeLog > ========= > > 6 March 2019: > ------------- > > * I spent last two days trying approaches to make the introduction of +Application+ concept less intrusive. > > Thing is, since several applications can be alive at the same time (in general at least two: Pharo and the > application the user is developing, but there can be more), when you create a window, is mandatory to know > the application it belongs to. > > And this is a problem. > > Why? Well, because there are two ways to do it: > > It can be: > > ---- > MyWindowClass newApplication: myApplication. > ---- > > or: > > ---- > myApplication new: MyWindowClass. > ---- > > And well... both approaches require that you are in possesion of an application when you create a window. > > Really random thought... If somehow a window is created without it knowing the application, > could it create a new application for it - it occurs to me it might be called an "anonymous application" > but I've no idea if that makes sense within the framework, and too many random applications might be unmanageable. Thatâs what happens now: they are assigned to an âNullApplicationâ. But this means you cannot track flow, etcâ¦ so at the end this should not happen (even if for now is good to allow migration of things). Esteban > > cheers -ben > > P.S. Thanks for these ChangeLogs. Great to see whats in the pipeline.

March 11, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 4 March 2019

by Ben Coman

On Mon, 11 Mar 2019 at 15:00, <estebanlm(a)gmail.com> wrote: > Hello! > > This is my weekly ChangeLog, from 4 March 2019 to 10 March 2019. > You can see it in a better format by going here: > http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019 > > ChangeLog > ========= > > 6 March 2019: > ------------- > > * I spent last two days trying approaches to make the introduction of > +Application+ concept less intrusive. > > Thing is, since several applications can be alive at the same time (in > general at least two: Pharo and the > application the user is developing, but there can be more), when you > create a window, is mandatory to know > the application it belongs to. > > And this is a problem. > > Why? Well, because there are two ways to do it: > > It can be: > > ---- > MyWindowClass newApplication: myApplication. > ---- > > or: > > ---- > myApplication new: MyWindowClass. > ---- > > And well... both approaches require that you are in possesion of an > application when you create a window. > Really random thought... If somehow a window is created without it knowing the application, could it create a new application for it - it occurs to me it might be called an "anonymous application" but I've no idea if that makes sense within the framework, and too many random applications might be unmanageable. cheers -ben P.S. Thanks for these ChangeLogs. Great to see whats in the pipeline.

March 11, 2019

[Pharo 8.0] Build #126: 2769-add-Slot-example-write-once-slot

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

There is a new Pharo build available! The status of the build #126 was: SUCCESS. The Pull Request #2770 was integrated: "2769-add-Slot-example-write-once-slot" Pull request url: https://github.com/pharo-project/pharo/pull/2770 Issue Url: https://pharo.fogbugz.com/f/cases/2769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 11, 2019

[Pharo 8.0] Build #125: 2790-standalone-Tool-Registry

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

There is a new Pharo build available! The status of the build #125 was: SUCCESS. The Pull Request #2787 was integrated: "2790-standalone-Tool-Registry" Pull request url: https://github.com/pharo-project/pharo/pull/2787 Issue Url: https://pharo.fogbugz.com/f/cases/2786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 11, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Max Leske

Hi Stef, On 11 Mar 2019, at 8:12, ducasse wrote: > Max > > ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit > normal that it got removed in P7. But we should check this. > I do not have the time today for this. > > normally ifNotNilDo: should be covered by a migrator automatic rewrite > rules (can you check?): Ducasse/Migrator > because in such case you load the migrator packages and execute the > tests of the OSProcess (if any) > then you execute OSProcess and the user of ifNotNilDo: will be > automatically rewritten and you are just left to check > the senders that are left and commit a new version. You have extensions defined for #ifNotNilDo: in your migration definition for 50 to 60. > > If IfNotNilDo: is not covered by a automated migration we should add > one. > It was deprecated before the automated migrations were introduced. > > > Now about your question: yes a new version of OSProcess should be > produced for P7. > The best would be to migrate it to github. I think Dave might disagree ;) If the maintainers are fine with moving to Github then that would be great. I assume that there will be some objections to that (e.g. because of loading in Squeak?) and we (I at least) don't want to maintain a fork / mirror on Github. Pulling from SqueakSource works fine for now. Max > > Let me know if it helps. > > Stef > >> On 11 Mar 2019, at 08:00, Max Leske <maxleske(a)gmail.com> wrote: >> >> Hi all, >> >> Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess >> loading fails. I volunteer to update OSProcess for Pharo 7 but I need >> someone to tell me what the expected workflow is. AFAICT, we've >> simply copied the current ConfigurationOf to the MetaRepoForXX in the >> past without making any changes specific to Pharo. That will not work >> this time. >> So, should I create a new version of OSProcess for all platforms, >> where #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add >> a compatibility package for Pharo? Or something else? >> >> Cheers, >> Max >>

March 11, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Max Leske

On 11 Mar 2019, at 9:38, Thierry Goubier wrote: > Hi Max, > > use the following to load OSProcess: > > Metacello new > configuration: 'OSProcess'; > repository: 'http://www.squeaksource.com/MetacelloRepository'; > load > > As I said a while ago, the ifNotNilDo: thing was corrected long ago > and that configuration updated; the one in the catalog is limited to > Pharo 6. Perfect, that worked. Thanks! > > Thierry > > Le lun. 11 mars 2019 Ã 08:00, Max Leske <maxleske(a)gmail.com> a Ã©crit : >> >> Hi all, >> >> Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading >> fails. I volunteer to update OSProcess for Pharo 7 but I need someone to >> tell me what the expected workflow is. AFAICT, we've simply copied the >> current ConfigurationOf to the MetaRepoForXX in the past without making >> any changes specific to Pharo. That will not work this time. >> So, should I create a new version of OSProcess for all platforms, where >> #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a >> compatibility package for Pharo? Or something else? >> >> Cheers, >> Max >>

March 11, 2019

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Member: CIRAD

by Esteban Lorenzano

Hi, > On 11 Mar 2019, at 04:24, askoh <askoh(a)askoh.com> wrote: > > It would be very interesting if there is a list showing what each consortium > member uses Pharo or Smalltalk for. Sadly, thatâs not really possible :( While many members have no problem on freely talk about what they do, others do not have same approach :) Esteban > > Thanks, > Aik-Siong Koh > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

March 11, 2019

Re: [Pharo-dev] OSProcess for Pharo 7

by Thierry Goubier

Hi Max, use the following to load OSProcess: Metacello new configuration: 'OSProcess'; repository: 'http://www.squeaksource.com/MetacelloRepository'; load As I said a while ago, the ifNotNilDo: thing was corrected long ago and that configuration updated; the one in the catalog is limited to Pharo 6. Thierry Le lun. 11 mars 2019 Ã 08:00, Max Leske <maxleske(a)gmail.com> a Ã©crit : > > Hi all, > > Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading > fails. I volunteer to update OSProcess for Pharo 7 but I need someone to > tell me what the expected workflow is. AFAICT, we've simply copied the > current ConfigurationOf to the MetaRepoForXX in the past without making > any changes specific to Pharo. That will not work this time. > So, should I create a new version of OSProcess for all platforms, where > #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a > compatibility package for Pharo? Or something else? > > Cheers, > Max >

March 11, 2019

[Pharo 8.0] Build #124: Revert "2759-Spec-Deprecated-should-be-removed-from-Pharo-8"

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

There is a new Pharo build available! The status of the build #124 was: SUCCESS. The Pull Request #2788 was integrated: "Revert "2759-Spec-Deprecated-should-be-removed-from-Pharo-8"" Pull request url: https://github.com/pharo-project/pharo/pull/2788 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 11, 2019