- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #738: 21655-MetaLinks-should-by-default-not-announce-a-MetaLinkChanged-only-when-option-is-set

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

There is a new Pharo build available! The status of the build #738 was: SUCCESS. The Pull Request #1160 was integrated: "21655-MetaLinks-should-by-default-not-announce-a-MetaLinkChanged-only-when-option-is-set" Pull request url: https://github.com/pharo-project/pharo/pull/1160 Issue Url: https://pharo.fogbugz.com/f/cases/21655 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2018

[Reflectivity] change regarding announcement in Pharo7

by Marcus Denker

Hi, One questionable (but practical) thing that MetaLinks have is that they announce (MetalinkChanged) when they are installed or uninstalled. This is nice for being able to show them in the UI (and e.g. the Watcher implemented with them). But it is very very slowâ¦ so I now made it an option: https://github.com/pharo-project/pharo/pull/1160 <https://github.com/pharo-project/pharo/pull/1160> it is by default off, but can be turned on reflectively at any point. e.g. the link of the execution counter now looks like this: link := MetaLink new metaObject: self; selector: #increase; optionAnnounce: true. It has announcing enable so that the browser refreshes when it gets added or removed. Marcus

March 28, 2018

[Pharo 7.0-dev] Build #737: 21573-Remove-unused-variables-from-Behavior-hierarchy

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

There is a new Pharo build available! The status of the build #737 was: SUCCESS. The Pull Request #1095 was integrated: "21573-Remove-unused-variables-from-Behavior-hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/1095 Issue Url: https://pharo.fogbugz.com/f/cases/21573 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2018

Re: [Pharo-dev] Slot Questions

by Marcus Denker

> On 24 Mar 2018, at 21:21, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Stateful traits inspired me to reread the flexible object layout paper and I > came up with a few questions about slots: > - What is the plan for tool support? For example, it seems that to make > slots discoverable like any other class or message, "References to it" > should include class definitions, which should be the primary slot client. Yes, these things need to be done.. I have a very large TODO list for this but it is hard to find time > - Why does IndexedSlot have a #name slot? I thought the index and name were > "either or" for instVars. This is the name of the variable. Even though an init-var is accessed by index, it still has a name (e.g. #x in Point). Marcus

March 28, 2018

Re: [Pharo-dev] Why calypso inverse the hierarchy?

by Denis Kudriashov

Hi Stef 2018-03-27 23:11 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi denis > > Calypso asked me where I want to install a method. > Normally this dialog appears when you edit a method which class is not selected in the browser. For example if you enable superclass method visibility and edit one of inherited methods. But give me your scenario. > And I do not really appreciate that I get the inheritance tree reserved. > There is setting for this. And I am not against to change default value or hardcode this part. Originally it was simple list with selected class at the bottom. Then there was issue The currently edited class should be the first option when overriding methods <https://github.com/dionisiydk/Calypso/issues/163>. Idea that first item should be the most common case which is selected class. At the end I realized that I can easily show hierarchy which I though is better than simple list. And I reused existing hierarchy from method visibility list. So there are two points for this dialog: - do we want selected class to be first? - do we want hierarchical view? Best regards, Denis To me it will destroy students. > On my own code which is super stupid I had to think twice. I cannot > image students. > > Then when working on code that is not ours it is be super difficult to > understand anything. > > How can I set that superclass should be higher than subclasses? > > Stef >

March 27, 2018

Re: [Pharo-dev] Calypso: how to see two different methods (without diff) side by side?

by Denis Kudriashov

Hi Stef. I found very simple way how to support it. So maybe next release if there will be time. Best regards, Denis 2018-03-27 21:15 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi denis > > I do not really use a method diff but I would love to be able to see > two methods > side by side. > > Stef > >

March 27, 2018

Re: [Pharo-dev] Why calypso inverse the hierarchy?

by Stephane Ducasse

And by the way I do not understand why calypso asks me where I want to define a method, when I selected already the class in which I'm coding. On Tue, Mar 27, 2018 at 11:11 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi denis > > Calypso asked me where I want to install a method. > And I do not really appreciate that I get the inheritance tree reserved. > To me it will destroy students. > On my own code which is super stupid I had to think twice. I cannot > image students. > > Then when working on code that is not ours it is be super difficult to > understand anything. > > How can I set that superclass should be higher than subclasses? > > Stef

March 27, 2018

Why calypso inverse the hierarchy?

by Stephane Ducasse

Hi denis Calypso asked me where I want to install a method. And I do not really appreciate that I get the inheritance tree reserved. To me it will destroy students. On my own code which is super stupid I had to think twice. I cannot image students. Then when working on code that is not ours it is be super difficult to understand anything. How can I set that superclass should be higher than subclasses? Stef

March 27, 2018

Re: [Pharo-dev] Bloc: Simulating "Worlds"

by Sean P. DeNigris

Aliaksei Syrel wrote > "a reply" Ha ha. Thanks, that clears it up nicely. I'm all set ;) Aliaksei Syrel wrote > P.S. I will reply here with an example when it is done. Looking forward to it :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 27, 2018

Re: [Pharo-dev] Roadmap to Pharo 7 Release

by Peter UhnÃ¡k

> > Since Glamour is not really maintained anymore and source of some > leaks and problems, we want to remove any users > except GTTools. > Can you please provide more info on this? What exactly is going to be removed? Thanks, Peter

March 27, 2018