- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #624: 7196-IconStyler-is-missing-visitEnglobingErrorNode
by ci-pharo-ci-jenkins2＠inria.fr Aug. 28, 2020

Aug. 28, 2020

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

1 0

Smalltalkhub is now in archive mode (static version)
by Christophe Demarey Aug. 27, 2020

Aug. 27, 2020

Hi all, Since May, Smalltalk is in read-only mode, allowing people to get back their data and move it to another forge if needed. We had several unexpected downtimes with the deprecated version of Smalltalkub (different software stack due to server migration). To enhance the user experience, we put the static version of Smalltalkhub Â« SmalltalkHub archive Â» on-line as the official http://smalltalkhub.com service. It was already announced that it will be done in November but we decided to do it earlier because it improves the current state: - faster and reliable downloads from smalltalkhub.com (mcz files are no longer stored in a Mongo DB but served as static files) - Smalltalkhub archive still allows to list projects, search for a project, see packages, contributors, commits - deprecated version of smalltalkhub is still on-line until November at http://deprecated.smalltalkhub.com/. So you have the best of the 2 versions. Regards, The Pharo consortium team.

1 0

[Pharo 9.0] Build #623: Prevent the inspector to fail on double click on an item in a collection
by ci-pharo-ci-jenkins2＠inria.fr Aug. 27, 2020

Aug. 27, 2020

There is a new Pharo build available! The status of the build #623 was: FAILURE. The Pull Request #7188 was integrated: "Prevent the inspector to fail on double click on an item in a collection" Pull request url: https://github.com/pharo-project/pharo/pull/7188 Issue Url: https://github.com/pharo-project/pharo/issues/inspectorDoubleClickFail Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #622: Deprecate-allSendersToStringDo
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

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

1 0

[Pharo 9.0] Build #621: 6818-wrong-protocol-for-SequenceableCollection---nextToLast
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

There is a new Pharo build available! The status of the build #621 was: FAILURE. The Pull Request #7185 was integrated: "6818-wrong-protocol-for-SequenceableCollection---nextToLast" Pull request url: https://github.com/pharo-project/pharo/pull/7185 Issue Url: https://github.com/pharo-project/pharo/issues/6818 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #620: CopyingLocalVariable-Simplification
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

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

1 0

[Pharo 9.0] Build #619: 7127-Use-semantics-analysis-in-ClyMethodEditorToolMorph--currentEditedAST
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

There is a new Pharo build available! The status of the build #619 was: FAILURE. The Pull Request #7179 was integrated: "7127-Use-semantics-analysis-in-ClyMethodEditorToolMorph--currentEditedAST" Pull request url: https://github.com/pharo-project/pharo/pull/7179 Issue Url: https://github.com/pharo-project/pharo/issues/7127 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #618: CleanBlock-accessVariables-ForDebugger
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

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

1 0

[Pharo 9.0] Build #617: ReservedVariable-lookupDictionary
by ci-pharo-ci-jenkins2＠inria.fr Aug. 26, 2020

Aug. 26, 2020

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

1 0

Re: [Pharo-dev] Pharo-dev Digest, Vol 88, Issue 7
by Richard Uttner Aug. 26, 2020

Aug. 26, 2020

Hi Esteban and Martin, sorry for my contribution to this topic being so late. I fully agree to Martin's suggestion of checking if an inspected object conforms to the rich inspector api before applying it. For dealing with Glorp, I found an easy solution which Pavel will integrate soon in the Glorp port he published some time ago. My approach to find the trigger(s) resolving the proxy was simply hooking #doesNotUnderstand: with a Transcript trace of the current message. So I found out that it were only 3, which I list below along with my implementation in Proxy that stopped any resolving: gtDisplayString Â Â Â self isInstantiated Â Â Â Â Â Â ifTrue: [ ^self class name , ' on ', value gtDisplayString]. Â Â Â ^self class name, ' uninstantiated on ', self query resultClass name gtInspectorVariableNodesIn: aCollection Â Â "Taken from Object, avoiding loop over indexed variables calling #basicSize" Â Â aCollection Â Â Â Â Â Â addAll: ((self class allSlots collect: [ :slot | Â Â Â Â Â Â Â Â Â GTInspectorSlotNode hostObject: self slot: slot ])) readSlot: aSlot Â Â Â "Taken from Object, sent by GTInspectorSlotNode" Â Â Â ^aSlot read: self With this approach, I was not able to trigger proxy resolution by just navigating in the inspector, I had to explicitely send #getValue to the slot. Hope this helps until we have a more general solution! Best regards, Richard Am 08.08.2020 um 18:00 schrieb pharo-dev-request(a)lists.pharo.org: > Message: 1 > Date: Fri, 7 Aug 2020 20:33:50 -0300 > From: Esteban Maringolo<emaringolo(a)gmail.com> > To: Pharo Developers<pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] Tools with Proxy support > Message-ID: > <CAJMgPC+5v4eG+qK3m7LjWmYs3H1J=mWopg_acUU9VcCsY5YJ5g(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > 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 > > > > ------------------------------ > > Message: 2 > Date: Fri, 7 Aug 2020 16:59:10 -0700 > From: Martin McClure<martin(a)hand2mouse.com> > To: Pharo Development List<pharo-dev(a)lists.pharo.org>, Esteban > Maringolo<emaringolo(a)gmail.com> > Subject: Re: [Pharo-dev] Tools with Proxy support > Message-ID:<49dde322-a79d-1b16-798e-9679ce08b1bf(a)hand2mouse.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > 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

3 2