- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Confused about the GTInspector State Tab

by stepharo

I agree. I often want to see the real implementation and not the view that the system wants me to believe. Stef > I am confused about the GTInspector State tab. What is its definition ? > > I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. > > Why then does it not show all variable content and only named variables ? > > Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these have an items view, but not all. > > How can I inspect an individual character of a String ? Or an individual byte ? > > Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are (currently) implemented, and then another tab should show the sign, mantissa, exponent view. > > In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO. It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing. > > I could propose changes or a slice, but I think we should agree on the definition of 'State' first. > > Sven > > >

Oct. 1, 2014

GTPlayground Play Button Semantics

by Sven Van Caekenberghe

Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole workspace contents) ? If so, why ? I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like a notebook containing lots of different things. Sven

Oct. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40275 Home: https://github.com/pharo-project/pharo-core

Oct. 1, 2014

[pharo-project/pharo-core] f82136: 40275

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f821362cb2335e34c3c60ad34adccd29882fc70c https://github.com/pharo-project/pharo-core/commit/f821362cb2335e34c3c60ad3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-01 (Wed, 01 Oct 2014) Changed paths: A GroupManager.package/GroupAnnouncer.class/class/initialization/reset.st A GroupManager.package/GroupAnnouncer.class/class/instance creation/uniqueInstance.st M GroupManager.package/GroupAnnouncer.class/definition.st M Nautilus.package/Nautilus.class/instance/announcement/announcer.st R NautilusCommon.package/NautilusAnnouncer.class/README.md R NautilusCommon.package/NautilusAnnouncer.class/definition.st R OpalCompiler-Core.package/IRBlockReturnTop.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRInstVarAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRInstruction.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRJump.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRJumpIf.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRLiteralVariableAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRMethod.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRPop.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRPushArray.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRPushClosureCopy.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRPushDup.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRPushLiteral.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRReceiverAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRRemoteTempAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRReturn.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRSend.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRSequence.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRTempAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRTempVector.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRThisContextAccess.class/instance/visiting/accept_.st R OpalCompiler-Core.package/IRVisitor.class/README.md R OpalCompiler-Core.package/IRVisitor.class/class/instance creation/on_.st R OpalCompiler-Core.package/IRVisitor.class/definition.st R OpalCompiler-Core.package/IRVisitor.class/instance/visiting/visitMethod_.st R OpalCompiler-Core.package/TIRVisitor.class/README.md R OpalCompiler-Core.package/TIRVisitor.class/definition.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitBlockReturnTop_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitInstVarAccess_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitJumpIf_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitJump_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitLiteralVariableAccess_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitMethod_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitPop_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitPushArray_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitPushClosureCopy_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitPushDup_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitPushLiteral_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitReceiverAccess_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitRemoteTempAccess_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitReturn_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitSend_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitSequence_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitTempAccess_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitTempVector_.st R OpalCompiler-Core.package/TIRVisitor.class/instance/visiting/visitThisContextAccess_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script275.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40275.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Debugger.package/SpecDebugger.class/instance/initialization/initialize.st Log Message: ----------- 40275 14129 Use Announcer>>#when:send:to: in Spec-Debugger https://pharo.fogbugz.com/f/cases/14129 14124 Remove SystemAnnouncer subclass NautilusAnnouncer https://pharo.fogbugz.com/f/cases/14124 14126 Remove SystemAnnouncer subclass GroupAnnouncer https://pharo.fogbugz.com/f/cases/14126 10148 IRVisitor and IRInterpreter https://pharo.fogbugz.com/f/cases/10148 http://files.pharo.org/image/40/40275.zip

Oct. 1, 2014

Confused about the GTInspector State Tab

by Sven Van Caekenberghe

I am confused about the GTInspector State tab. What is its definition ? I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. Why then does it not show all variable content and only named variables ? Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these have an items view, but not all. How can I inspect an individual character of a String ? Or an individual byte ? Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are (currently) implemented, and then another tab should show the sign, mantissa, exponent view. In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO. It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing. I could propose changes or a slice, but I think we should agree on the definition of 'State' first. Sven

Oct. 1, 2014

[pharo-project/pharo-core] 7e5c91: 40274

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7e5c915040ac9fea3447288cfe9f26f3f1e4244f https://github.com/pharo-project/pharo-core/commit/7e5c915040ac9fea3447288c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-01 (Wed, 01 Oct 2014) Changed paths: A Morphic-Examples.package/ClassListExample.class/class/examples/example.st A Morphic-Examples.package/ClassTreeExample.class/class/examples/example.st A Morphic-Examples.package/LazyClassListExample.class/class/examples/example.st A Morphic-Examples.package/PackageTreeExample.class/class/examples/example.st A Morphic-Examples.package/SimpleGridExample.class/class/examples/example.st A Morphic-Examples.package/SimplestClassListExample.class/class/examples/example.st A Morphic-Examples.package/SimplestClassListWithChunkExample.class/class/examples/example.st A Morphic-Examples.package/SimplestClassListWithPagerExample.class/class/examples/example.st A Morphic-Examples.package/SimplestPaginatedClassListExample.class/class/examples/example.st A Morphic-Widgets-NewList.package/NewListRenderer.class/instance/communication with model/commandKeyTypedIntoMenu_.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToAnnouncements.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToTestAnnouncements.st A OpalDecompiler.package/extension/CompiledMethod/instance/gtInspectorDecompilerIn_.st R SUnit-Core.package/TestAnnouncer.class/README.md R SUnit-Core.package/TestAnnouncer.class/definition.st A SUnit-Core.package/TestCase.class/class/accessing/historyAnnouncer.st M SUnit-Core.package/TestCase.class/class/history/history_.st M SUnit-Core.package/TestCase.class/definition.st M SUnit-Core.package/TestResult.class/instance/history/updateResultsInHistory.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script274.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40274.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40274 14125 Remove SystemAnnouncer subclass TestAnnouncer https://pharo.fogbugz.com/f/cases/14125 14122 Classes in Morphic-Examples should include real #example methods https://pharo.fogbugz.com/f/cases/14122 12973 ChangeSorter CMD-W with menu open causes error https://pharo.fogbugz.com/f/cases/12973 14120 decompiler view for GTInspector https://pharo.fogbugz.com/f/cases/14120 http://files.pharo.org/image/40/40274.zip

Oct. 1, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40274 Home: https://github.com/pharo-project/pharo-core

Oct. 1, 2014

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

by Yuriy Tymchuk

> On 01 Oct 2014, at 07:37, stepharo <stepharo(a)free.fr> wrote: > > is Kommiter working for you in 40 latest? > Because I get an error tellling to me that it cannot find Applications / Pharo? I was also getting this some time ago. Didnât check since then Uko >

Oct. 1, 2014

Re: [Pharo-dev] is Kommiter working for you in 40 latest?

by Christophe Demarey

Oct. 1, 2014

Re: [Pharo-dev] GTInspector + Fuel

by Mariano Martinez Peck

On Wed, Oct 1, 2014 at 2:25 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Mariano, > > I am not sure I understand the implication of using addPostMaterializationAction: > in combination with the inspector materialization extension. Where do you > see the opportunity? > > What I thought is the following..... if you are at the inspector level, and you are watching a .fuel it is nice that it materializes the file and then let you inspect the materialized object. However, if the graph was serialized with postMaterializationActions, those would be executed after you click in the inspector. This trick of the postMaterializationActions was used, for example, for when you serialize test failures or debuggers, in order to directly open a new debugger with the materialized stack upon materialization. So.... you are in the inspector, you see a fueled out stack or test failure, you click on it, and you have the debugger opened :) > Cheers, > Doru > > On Tue, Sep 30, 2014 at 10:52 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> That's very nice!!! >> >> >> And that ... together with the ability to define >> #addPostMaterializationAction: is a super awesome combination :) >> >> On Tue, Sep 30, 2014 at 5:17 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> >>> On 30.09.2014, at 22:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> :) >>> >>> Doru >>> >>> >>> On Tue, Sep 30, 2014 at 10:11 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>> wrote: >>> >>>> Hi, >>>> >>>> sorry if this is a known thing, but Iâve just notices this and it made >>>> my day. >>>> >>>> So in GTInspector you can browse filesystem, but when you select a fuel >>>> file, you can press a "plusâ button in top right corner, and it >>>> materialises the object. Amazing. >>>> >>> >>> Hehe ;) Took me 10 minutes on MooseDay (including showing meta info) :D >>> >>> GT rocks! >>> >>> >>>> Uko >>>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- Mariano http://marianopeck.wordpress.com

Oct. 1, 2014