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

Re: [Pharo-dev] Cleaning up... baseClass, instanceSide, theNonMetaclass

by Guillermo Polito

In my code I use to use instanceSide and classSide. don't know why. Maybe they are clearer to me? On Sun, Feb 11, 2018 at 8:59 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2018-02-11 18:14 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Hi >> >> We already got this discussion and I plan to address it. >> Now I discovered that in addition to instanceSide and theNonMetaclass we >> have >> >> - classClass and baseClass >> - theMetaclass and theNonMetaclass >> - instanceSide and classSide >> >> https://pharo.fogbugz.com/f/cases/20941/deprecate-theMetacla >> ss-and-the-theNonMeta >> >> Even if instanceSide and classSide come from UI concerns I think that >> there are much >> better than the others. >> > > + 100 > > >> >> So have you any concerns and prefer one of the other couples? Because >> we should stop >> accumulate cruft in the system. We do not need three ways to do the same. >> >> Stef >> >> > -- 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

Feb. 12, 2018

[Pharo 7.0-dev] Build #530: 21314 Remove unnecessary "self run:" in IntervalTest and IdentityBagTest

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

There is a new Pharo build available! The status of the build #530 was: SUCCESS. The Pull Request #842 was integrated: "21314 Remove unnecessary "self run:" in IntervalTest and IdentityBagTest" Pull request url: https://github.com/pharo-project/pharo/pull/842 Issue Url: https://pharo.fogbugz.com/f/cases/21314 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2018

[Pharo 7.0-dev] Build #529: 21289 Remove unnecessary "self run:" in BasicBehaviorClassMetaclassTest

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

There is a new Pharo build available! The status of the build #529 was: SUCCESS. The Pull Request #866 was integrated: "21289 Remove unnecessary "self run:" in BasicBehaviorClassMetaclassTest" Pull request url: https://github.com/pharo-project/pharo/pull/866 Issue Url: https://pharo.fogbugz.com/f/cases/21289 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 12, 2018

Esteban's ChangeLog week of 5 February 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 5 February 2018 to 11 February 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=5/2/2018&to=11/2/2018 ChangeLog ========= 6 February 2018: ---------------- * ... and packaging should be [restored](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/214) too. Which means latest vm versions are latest builds from OSVM: === 64bit * [http://files.pharo.org/get-files/70/pharo64-mac-latest.zip](http://files.ph… * [http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip](http… * [http://files.pharo.org/get-files/70/pharo64-linux-latest.zip](http://files.… * [http://files.pharo.org/get-files/70/pharo64-win-latest.zip](http://files.ph… === 32bit * [http://files.pharo.org/get-files/70/pharo-win-latest.zip](http://files.phar… * [http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip](http:/… * [http://files.pharo.org/get-files/70/pharo-linux-latest.zip](http://files.ph… * [http://files.pharo.org/get-files/70/pharo-mac-latest.zip](http://files.phar… === Hints * MacOS VMs now are signed! This should fix a lot of problems we had before. * Please take note that latest win64 build lacks all library dependencies, and many things will not work (working on that) Thanks to [Fabio](https://github.com/fniephaus) to help me put all the pieces together. * Certificates should work now, and we can have a [signed VM](https://github.com/OpenSmalltalk/opensmalltalk-vm/pull/214). * yesterday with Fabio we worked on fix an upload of pharo-vm that was failing: * [https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/160](https://githu… 5 February 2018: ---------------- * I released a patch for iceberg: * [iceberg 0.6.7](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.7) * [libgit 1.0.5](https://github.com/pharo-vcs/libgit2-pharo-bindings/releases/tag/v1.… * [tonel 1.0.6](https://github.com/pharo-vcs/tonel/releases/tag/v1.0.6) this is a maintenance version that fixes a couple of bugs and cleans a bit, but big changes will come next release (0.7) * I published new versions of the certifictes to get a signed mac VM. In theory, this time it should work :) cheers! Esteban

Feb. 12, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by HernÃ¡n Morales Durand

Hi Eliot, One could say that a pragma is a message without a method? I think pragmas were never been integrated properly into the system browser. We can browses pragmas with the PragmaCollection but what I mean is a pragma-aware browser. See for example, there are some pragmas where is easy to infer the meaning: <magritteDescription>, <gtInspectorPresentationOrder:>, and others <eProperty> where is not so clear. So even if we take <gtInspectorPresentationOrder:> is not easy with the current tools to find of which parameters makes sense. I always missed something like the annotation pane plugin or the quality assistant plugin in Nautilus, but for pragmas. This could be an excellent opportunity for Calypso to see how pragmas can be exploited in the way you describe. Thanks for the kind explanation. Cheers, HernÃ¡n 2018-02-12 1:09 GMT-03:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > Hi Hernan, > > > > > _,,,^..^,,,_ (phone) >> On Feb 11, 2018, at 10:47 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> I don't know, but how you you find documentation about specific pragmas? > > The best way is to ensure the pragma has at least one implementation, i.e. there is at least one method in the system that has the same signature as the pragma. This implementation should document the pragma, but even better it should be the method that extracts information from the pragma. > > An example will help. Imagine a pragma that specifies a method belongs on some menu. The method containing the pragma is intended to be an action of the menu, do that when the menu item is selected, the method containing the pragma will b executed. The pragma defines the menu the method belongs to, where in the method, the string to appear in the menu, the hot key for the menu item, etc. > > If the pragma is implemented by a menu builder then > - yes, certainly the pragma can be documented in the m by builder's implementation, but also > - the menu can be built by performing the pragma by the menu builder > > This was my intent when Steve Dahl and I invented pragmas, that there would always be implementations of the pragma in classes that were designed to extract the information from the pragma and add the method containing the pragma to whatever structure the pragma was intended to facilitate updating (menus, inspectors, exported apis, etc). So the most powerful way of use my pragmas is via a visitor pattern: > > When a method with a particular pragma is added or removed, the class containing the method triggers some action. This action collects all the relevant pragma methods in the class hierarchy, creates some builder object, and has the builder perform each method containing a relevant pragma. > > Using pragmas as arbitrary labels is fine, bug doesn't exploit the fact that pragmas are messages, and that hence one can do senders and implementors /and/ perform them. > > HTH > >> >> HernÃ¡n >> >> >> 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> Hi >>> >>> what is this pragma in metaclass method? >>> >>> Stef >>> >> >

Feb. 12, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by Eliot Miranda

Hi Hernan, _,,,^..^,,,_ (phone) > On Feb 11, 2018, at 10:47 AM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > I don't know, but how you you find documentation about specific pragmas? The best way is to ensure the pragma has at least one implementation, i.e. there is at least one method in the system that has the same signature as the pragma. This implementation should document the pragma, but even better it should be the method that extracts information from the pragma. An example will help. Imagine a pragma that specifies a method belongs on some menu. The method containing the pragma is intended to be an action of the menu, do that when the menu item is selected, the method containing the pragma will b executed. The pragma defines the menu the method belongs to, where in the method, the string to appear in the menu, the hot key for the menu item, etc. If the pragma is implemented by a menu builder then - yes, certainly the pragma can be documented in the m by builder's implementation, but also - the menu can be built by performing the pragma by the menu builder This was my intent when Steve Dahl and I invented pragmas, that there would always be implementations of the pragma in classes that were designed to extract the information from the pragma and add the method containing the pragma to whatever structure the pragma was intended to facilitate updating (menus, inspectors, exported apis, etc). So the most powerful way of use my pragmas is via a visitor pattern: When a method with a particular pragma is added or removed, the class containing the method triggers some action. This action collects all the relevant pragma methods in the class hierarchy, creates some builder object, and has the builder perform each method containing a relevant pragma. Using pragmas as arbitrary labels is fine, bug doesn't exploit the fact that pragmas are messages, and that hence one can do senders and implementors /and/ perform them. HTH > > HernÃ¡n > > > 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hi >> >> what is this pragma in metaclass method? >> >> Stef >> >

Feb. 12, 2018

[Pharo 7.0-dev] Build #528: 21322 LayoutFrameTest testIdentity should not use deprecated method fraction:

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

There is a new Pharo build available! The status of the build #528 was: SUCCESS. The Pull Request #869 was integrated: "21322 LayoutFrameTest testIdentity should not use deprecated method fraction:" Pull request url: https://github.com/pharo-project/pharo/pull/869 Issue Url: https://pharo.fogbugz.com/f/cases/21322 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 11, 2018

Re: [Pharo-dev] Do we remove EyeInspector from Pharo 70?

by Peter UhnÃ¡k

I sometimes use the Eye Pointer Inspector to find memory leaks ... is there a replacement for that? Peter On Sun, Feb 11, 2018 at 9:29 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > I would vote for. > > Stef > >

Feb. 11, 2018

Re: [Pharo-dev] what is <localMetaclassMethod>

by Stephane Ducasse

This is one of the problem we will have to fix one of these days. Pragmas are missing PragmasType as we talk about it in the past. On Sun, Feb 11, 2018 at 7:47 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > I don't know, but how you you find documentation about specific pragmas? > > HernÃ¡n > > > 2018-02-11 14:48 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hi >> >> what is this pragma in metaclass method? >> >> Stef >> >

Feb. 11, 2018

Re: [Pharo-dev] flow to contribute?

by Stephane Ducasse

Tx for the explanation. I would not make things more complex. So I would not go on guessing. And I would not do 1 and 2. I would just add an iceberg menu contribute to Pharo and it just shows a large message and/or sets some stuff for me. Stef On Sun, Feb 11, 2018 at 8:38 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 11 Feb 2018, at 18:46, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi >> >> It looks like the flow to contribute changed. I do not find the >> fogbugz integration pop up anymore. >> Where is it? Was is changed? >> So I create a branch manually and commit in my fork and did a pull request >> but this is not clear. > > no, it didnât change. It does not appears if you did not add pharo-project as remote to your pharo fork. > is complicatedâ¦ right now is the only way we have to determine we are working on pharo and not just another random project. > > I am thinking on ways of solving this: > - add an (optional) iceberg properties file where we could define this. > - do a request using github api to know parent project. > > both approaches have pros and cons so I still do not decide (but Iâm more closer to the first option right now) > > Esteban > >> >> Stef >> > >

Feb. 11, 2018