- Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #153: Fix comment on OSWindow >> startTextInput

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

There is a new Pharo build available! The status of the build #153 was: FAILURE. The Pull Request #2781 was integrated: "Fix comment on OSWindow >> startTextInput" Pull request url: https://github.com/pharo-project/pharo/pull/2781 Issue Url: https://pharo.fogbugz.com/f/cases/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 12, 2019

[Pharo 8.0] Build #129: 2777-classbuilder-copyClassSlotsFromExistingClass-needs-to-be-done-by-the-classInstaller-by-default

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

There is a new Pharo build available! The status of the build #129 was: SUCCESS. The Pull Request #2778 was integrated: "2777-classbuilder-copyClassSlotsFromExistingClass-needs-to-be-done-by-the-classInstaller-by-default" Pull request url: https://github.com/pharo-project/pharo/pull/2778 Issue Url: https://pharo.fogbugz.com/f/cases/2777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 12, 2019

[Pharo 8.0] Build #128: 2751-rename-RBBLintRuleTests-to-RBBLintRuleTestData-and-add-comment

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

There is a new Pharo build available! The status of the build #128 was: FAILURE. The Pull Request #2758 was integrated: "2751-rename-RBBLintRuleTests-to-RBBLintRuleTestData-and-add-comment" Pull request url: https://github.com/pharo-project/pharo/pull/2758 Issue Url: https://pharo.fogbugz.com/f/cases/2751 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 12, 2019

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

by askoh

Even a partial list is better than nothing. Besides each member can be as vague or precise as the organization wishes. Some would see the advertising value. All the best, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 11, 2019

[Pharo 8.0] Build #127: 2740-do-not-zap-method-dict-when-making-classes-obsolete

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

There is a new Pharo build available! The status of the build #127 was: SUCCESS. The Pull Request #2741 was integrated: "2740-do-not-zap-method-dict-when-making-classes-obsolete" Pull request url: https://github.com/pharo-project/pharo/pull/2741 Issue Url: https://pharo.fogbugz.com/f/cases/2740 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 11, 2019

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