August 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #583: 7060-CoTypeInferencer-DNU-when-editing-code-after-removing-instance-variables

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

There is a new Pharo build available! The status of the build #583 was: FAILURE. The Pull Request #7076 was integrated: "7060-CoTypeInferencer-DNU-when-editing-code-after-removing-instance-variables" Pull request url: https://github.com/pharo-project/pharo/pull/7076 Issue Url: https://github.com/pharo-project/pharo/issues/7060 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 10, 2020

Re: [Pharo-dev] Tools with Proxy support

by Denis Kudriashov

Hi Esteban. Try look into Ghost framework: https://github.com/pharo-ide/Ghost. I carefully put GT support methods into a separate package Ghost-GTSupport . It also includes a tool to collect all messages from given scenario (like opening inspector) which could help you: student := GHStudent new. student inspect. "then check messages:" student learning studiedMessages For new tools upcoming into Pharo 9 the other support package will be required. Also consider implementing Glorp proxies with Ghost. Use GHStudent as an example and I can answer any questions. Then we will have a single place (Ghost) to adopt to any tooling changes. ÑÐ±, 8 Ð°Ð²Ð³. 2020 Ð³. Ð² 00:35, Esteban Maringolo <emaringolo(a)gmail.com>: > Hi, > > I'm having a hard time trying to debug some Glorp code in Pharo 8 > because the inspectors and the glamour things are triggering the > instantiation of my Proxy objects. > > I don't know how the inspectors, variable lists, and other tool work, > but I assume there should be a way to reimplement something in Proxy > to avoid causing a MessageNotUnderstood that triggers the > instantiation. > > If there is no way for it (I guess there is, looking at some gt* > selectors in ProtoObject), please consider having a debugPrintString > (and debugPrintOn:) in the upcoming Spec2 based tools. :-) > > Best regards, > > Esteban A. Maringolo > >

Aug. 9, 2020

[Pharo 8.0] Build #1141: 6342-SubscriptoutOfBounds-while-unzipping-with-ZipArchive

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

There is a new Pharo build available! The status of the build #1141 was: FAILURE. The Pull Request #6343 was integrated: "6342-SubscriptoutOfBounds-while-unzipping-with-ZipArchive" Pull request url: https://github.com/pharo-project/pharo/pull/6343 Issue Url: https://github.com/pharo-project/pharo/issues/6342 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 9, 2020

[Pharo 9.0] Build #582: Merge NewTools v0.4.2.3 with debugger fixes and improvements

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

There is a new Pharo build available! The status of the build #582 was: SUCCESS. The Pull Request #7056 was integrated: "Merge NewTools v0.4.2.3 with debugger fixes and improvements" Pull request url: https://github.com/pharo-project/pharo/pull/7056 Issue Url: https://github.com/pharo-project/pharo/issues/NewTools Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 8, 2020

[Pharo 9.0] Build #581: Typos in ProportionalSplitterMorph extension comments

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

There is a new Pharo build available! The status of the build #581 was: FAILURE. The Pull Request #7065 was integrated: "Typos in ProportionalSplitterMorph extension comments" Pull request url: https://github.com/pharo-project/pharo/pull/7065 Issue Url: https://github.com/pharo-project/pharo/issues/patch Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 8, 2020

Re: [Pharo-dev] Tools with Proxy support

by Esteban Maringolo

It is really difficult to work with these, and it's been like that for a long time (I remember these issues with Pharo 3 and 4). Or at least with GLORP Proxies (I don't know if those you're working with are any different). I put a breakpoint in the Proxy to find what was triggering it and the breakpoint was ignored. I put `1 halt` and my image hung. Pressed Alt+. and the fireworks started. Â¯\_(ã)_/Â¯ Esteban A. Maringolo On Fri, Aug 7, 2020 at 8:59 PM Martin McClure <martin(a)hand2mouse.com> wrote: > > Hi Esteban, > > I also have trouble with this sort of thing in Pharo -- inspectors > sending messages to objects under inspection that are not understood, or > that do not respond in the way the inspector expects. > > It is possible to build a basic inspector that sends no messages at all > to the inspected object (using the mirror methods), and it would be nice > to have that option in Pharo. > > It's also possible to have a "careful" inspector that uses a mirror > method to determine the class of the inspected object, then uses either > the purely-mirroring inspector or the richer inspector, depending on > whether the object's class inherits from Object. Since the GemStone > clients make use of proxy objects, GemStone's inspectors take this > general approach. They're not perfect either, but problems are > considerably fewer. > > Regards, > -Martin > > On 8/7/20 4:33 PM, Esteban Maringolo wrote: > > Hi, > > > > I'm having a hard time trying to debug some Glorp code in Pharo 8 > > because the inspectors and the glamour things are triggering the > > instantiation of my Proxy objects. > > > > I don't know how the inspectors, variable lists, and other tool work, > > but I assume there should be a way to reimplement something in Proxy > > to avoid causing a MessageNotUnderstood that triggers the > > instantiation. > > > > If there is no way for it (I guess there is, looking at some gt* > > selectors in ProtoObject), please consider having a debugPrintString > > (and debugPrintOn:) in the upcoming Spec2 based tools. :-) > > > > Best regards, > > > > Esteban A. Maringolo > > >

Aug. 8, 2020

Re: [Pharo-dev] Tools with Proxy support

by Martin McClure

Hi Esteban, I also have trouble with this sort of thing in Pharo -- inspectors sending messages to objects under inspection that are not understood, or that do not respond in the way the inspector expects. It is possible to build a basic inspector that sends no messages at all to the inspected object (using the mirror methods), and it would be nice to have that option in Pharo. It's also possible to have a "careful" inspector that uses a mirror method to determine the class of the inspected object, then uses either the purely-mirroring inspector or the richer inspector, depending on whether the object's class inherits from Object. Since the GemStone clients make use of proxy objects, GemStone's inspectors take this general approach. They're not perfect either, but problems are considerably fewer. Regards, -Martin On 8/7/20 4:33 PM, Esteban Maringolo wrote: > Hi, > > I'm having a hard time trying to debug some Glorp code in Pharo 8 > because the inspectors and the glamour things are triggering the > instantiation of my Proxy objects. > > I don't know how the inspectors, variable lists, and other tool work, > but I assume there should be a way to reimplement something in Proxy > to avoid causing a MessageNotUnderstood that triggers the > instantiation. > > If there is no way for it (I guess there is, looking at some gt* > selectors in ProtoObject), please consider having a debugPrintString > (and debugPrintOn:) in the upcoming Spec2 based tools. :-) > > Best regards, > > Esteban A. Maringolo >

Aug. 7, 2020

Tools with Proxy support

by Esteban Maringolo

Hi, I'm having a hard time trying to debug some Glorp code in Pharo 8 because the inspectors and the glamour things are triggering the instantiation of my Proxy objects. I don't know how the inspectors, variable lists, and other tool work, but I assume there should be a way to reimplement something in Proxy to avoid causing a MessageNotUnderstood that triggers the instantiation. If there is no way for it (I guess there is, looking at some gt* selectors in ProtoObject), please consider having a debugPrintString (and debugPrintOn:) in the upcoming Spec2 based tools. :-) Best regards, Esteban A. Maringolo

Aug. 7, 2020

[Pharo 9.0] Build #580: Adding support for Commander2 commands in Calypso context menu

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

There is a new Pharo build available! The status of the build #580 was: FAILURE. The Pull Request #6998 was integrated: "Adding support for Commander2 commands in Calypso context menu" Pull request url: https://github.com/pharo-project/pharo/pull/6998 Issue Url: https://github.com/pharo-project/pharo/issues/adding Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 7, 2020

[Pharo 9.0] Build #579: 6849 Integrate Microdown

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

There is a new Pharo build available! The status of the build #579 was: FAILURE. The Pull Request #7045 was integrated: "6849 Integrate Microdown" Pull request url: https://github.com/pharo-project/pharo/pull/7045 Issue Url: https://github.com/pharo-project/pharo/issues/6849 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 7, 2020