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

[update 3.0] #30345

by Marcus Denker

30345 ----- 11462 Wrong comment in testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses https://pharo.fogbugz.com/f/cases/11462 11463 RBRefactoringChangeTests >> #testAddMetaclassPattern takes too much time https://pharo.fogbugz.com/f/cases/11463 11460 TabModel>>closeable: is not working https://pharo.fogbugz.com/f/cases/11460 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.615.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.229… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Changes-Mar…

Aug. 27, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Camillo Bruni

that is pretty new, so we didn't fix this issue then :/ (or more probably, we didn't fix all users). => can you open an issue with a description on how to reproduce it? On 2013-08-26, at 22:52, Igor Stasenko <siguctua(a)gmail.com> wrote: > (oops.. pressed send before finishing mail) > > Pharo3.0 > Latest update: #30335 > > .. so it just 10 days old > > > On 26 August 2013 22:51, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> ah, ok.. maybe i use outdated image? >> >> >> >> On 26 August 2013 22:41, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> I think we agreed that >>> - #inspect: returns the inspected value >>> - #inspector: returns the inspector for the given value >>> >>> I thought we fixed exactly the bug you experience since Ben complained a >>> lot about it ;) >>> >>> On 2013-08-26, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> ... or another reason to answer the inspector window.. >>>> because right now it is badly broken: >>>> >>>> EyeInspector class>>inspect: anObject >>>> InspectorWrapper openInspector: (self inspector: anObject). >>>> ^ anObject >>>> >>>> but: >>>> >>>> Morph>>inspectInMorphic: evt >>>> evt hand attachMorph: ((Smalltalk tools inspect: self) extent: >>> 300@200) >>>> >>>> that explains why, when i taking the morph's halo >>>> and then use debug context menu and press inspect it, >>>> it puts morph info the hand, and changing its dimensions.. >>>> instead of putting inspector window into hand! >>>> >>>> you can imagine how annoying it is, when you want to debug morphic code. >>>> >>>> The solution is, of course to answer an inspector window instead of >>>> inspected object.. or, since people argued against this, for such cases, >>>> there should be extra protocol, like >>>> >>>> Smalltalk tools inspectorWindowOn: object >>>> >>>> (i changed the code to answer a window right now, but we need to solve >>> that >>>> dilemma) >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Best regards, > Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Igor Stasenko

(oops.. pressed send before finishing mail) Pharo3.0 Latest update: #30335 .. so it just 10 days old On 26 August 2013 22:51, Igor Stasenko <siguctua(a)gmail.com> wrote: > ah, ok.. maybe i use outdated image? > > > > On 26 August 2013 22:41, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> I think we agreed that >> - #inspect: returns the inspected value >> - #inspector: returns the inspector for the given value >> >> I thought we fixed exactly the bug you experience since Ben complained a >> lot about it ;) >> >> On 2013-08-26, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: >> > ... or another reason to answer the inspector window.. >> > because right now it is badly broken: >> > >> > EyeInspector class>>inspect: anObject >> > InspectorWrapper openInspector: (self inspector: anObject). >> > ^ anObject >> > >> > but: >> > >> > Morph>>inspectInMorphic: evt >> > evt hand attachMorph: ((Smalltalk tools inspect: self) extent: >> 300@200) >> > >> > that explains why, when i taking the morph's halo >> > and then use debug context menu and press inspect it, >> > it puts morph info the hand, and changing its dimensions.. >> > instead of putting inspector window into hand! >> > >> > you can imagine how annoying it is, when you want to debug morphic code. >> > >> > The solution is, of course to answer an inspector window instead of >> > inspected object.. or, since people argued against this, for such cases, >> > there should be extra protocol, like >> > >> > Smalltalk tools inspectorWindowOn: object >> > >> > (i changed the code to answer a window right now, but we need to solve >> that >> > dilemma) >> > >> > -- >> > Best regards, >> > Igor Stasenko. >> >> > > > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Igor Stasenko

ah, ok.. maybe i use outdated image? On 26 August 2013 22:41, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I think we agreed that > - #inspect: returns the inspected value > - #inspector: returns the inspector for the given value > > I thought we fixed exactly the bug you experience since Ben complained a > lot about it ;) > > On 2013-08-26, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: > > ... or another reason to answer the inspector window.. > > because right now it is badly broken: > > > > EyeInspector class>>inspect: anObject > > InspectorWrapper openInspector: (self inspector: anObject). > > ^ anObject > > > > but: > > > > Morph>>inspectInMorphic: evt > > evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300@200 > ) > > > > that explains why, when i taking the morph's halo > > and then use debug context menu and press inspect it, > > it puts morph info the hand, and changing its dimensions.. > > instead of putting inspector window into hand! > > > > you can imagine how annoying it is, when you want to debug morphic code. > > > > The solution is, of course to answer an inspector window instead of > > inspected object.. or, since people argued against this, for such cases, > > there should be extra protocol, like > > > > Smalltalk tools inspectorWindowOn: object > > > > (i changed the code to answer a window right now, but we need to solve > that > > dilemma) > > > > -- > > Best regards, > > Igor Stasenko. > > -- Best regards, Igor Stasenko.

Aug. 26, 2013

Can someone explain me what this code doing?

by Igor Stasenko

NewValueHolder>>contents: anObject | oldValue | lock ifTrue: [ ^ self ]. lock := true. oldValue := contents. contents := anObject. [ self contentsChanged: oldValue ] ensure: [ lock := false ]. ^ contents it is really interesting.. it appears you cannot change the contents of value holder (as you can see it will simply ignore it) when it 'locked' during announcing the change event. i know, this will prevent it from entering recursive loop, but i would instead throw an error in such case(s) because code which modifying the value as a reaction on value change is something really stupid and must be fixed, instead of putting workaround which will block the value holder from accepting new value(s).. and that is really bad: - notification(s) about some property change should not block the value from being able to be changed -- Best regards, Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Camillo Bruni

I think we agreed that - #inspect: returns the inspected value - #inspector: returns the inspector for the given value I thought we fixed exactly the bug you experience since Ben complained a lot about it ;) On 2013-08-26, at 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: > ... or another reason to answer the inspector window.. > because right now it is badly broken: > > EyeInspector class>>inspect: anObject > InspectorWrapper openInspector: (self inspector: anObject). > ^ anObject > > but: > > Morph>>inspectInMorphic: evt > evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300@200) > > that explains why, when i taking the morph's halo > and then use debug context menu and press inspect it, > it puts morph info the hand, and changing its dimensions.. > instead of putting inspector window into hand! > > you can imagine how annoying it is, when you want to debug morphic code. > > The solution is, of course to answer an inspector window instead of > inspected object.. or, since people argued against this, for such cases, > there should be extra protocol, like > > Smalltalk tools inspectorWindowOn: object > > (i changed the code to answer a window right now, but we need to solve that > dilemma) > > -- > Best regards, > Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Esteban A. Maringolo

As a side note: In Dolphin it returns the inspector :) Esteban A. Maringolo 2013/8/26 Igor Stasenko <siguctua(a)gmail.com>: > > > > On 26 August 2013 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> ... or another reason to answer the inspector window.. >> because right now it is badly broken: >> >> EyeInspector class>>inspect: anObject >> InspectorWrapper openInspector: (self inspector: anObject). >> ^ anObject >> >> but: >> >> Morph>>inspectInMorphic: evt >> evt hand attachMorph: ((Smalltalk tools inspect: self) extent: >> 300@200) >> >> that explains why, when i taking the morph's halo >> and then use debug context menu and press inspect it, >> it puts morph info the hand, and changing its dimensions.. >> instead of putting inspector window into hand! >> >> you can imagine how annoying it is, when you want to debug morphic code. >> >> The solution is, of course to answer an inspector window instead of >> inspected object.. or, since people argued against this, for such cases, >> there should be extra protocol, like >> >> Smalltalk tools inspectorWindowOn: object >> >> (i changed the code to answer a window right now, but we need to solve >> that dilemma) >> > ... i mean, changed in my working image. not in Pharo :) > >> >> -- >> Best regards, >> Igor Stasenko. > > > > > -- > Best regards, > Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] So, again, why 'object inspect' should answer an object?

by Igor Stasenko

On 26 August 2013 22:32, Igor Stasenko <siguctua(a)gmail.com> wrote: > ... or another reason to answer the inspector window.. > because right now it is badly broken: > > EyeInspector class>>inspect: anObject > InspectorWrapper openInspector: (self inspector: anObject). > ^ anObject > > but: > > Morph>>inspectInMorphic: evt > evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300@200 > ) > > that explains why, when i taking the morph's halo > and then use debug context menu and press inspect it, > it puts morph info the hand, and changing its dimensions.. > instead of putting inspector window into hand! > > you can imagine how annoying it is, when you want to debug morphic code. > > The solution is, of course to answer an inspector window instead of > inspected object.. or, since people argued against this, for such cases, > there should be extra protocol, like > > Smalltalk tools inspectorWindowOn: object > > (i changed the code to answer a window right now, but we need to solve > that dilemma) > > ... i mean, changed in my working image. not in Pharo :) > -- > Best regards, > Igor Stasenko. > -- Best regards, Igor Stasenko.

Aug. 26, 2013

So, again, why 'object inspect' should answer an object?

by Igor Stasenko

... or another reason to answer the inspector window.. because right now it is badly broken: EyeInspector class>>inspect: anObject InspectorWrapper openInspector: (self inspector: anObject). ^ anObject but: Morph>>inspectInMorphic: evt evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300@200) that explains why, when i taking the morph's halo and then use debug context menu and press inspect it, it puts morph info the hand, and changing its dimensions.. instead of putting inspector window into hand! you can imagine how annoying it is, when you want to debug morphic code. The solution is, of course to answer an inspector window instead of inspected object.. or, since people argued against this, for such cases, there should be extra protocol, like Smalltalk tools inspectorWindowOn: object (i changed the code to answer a window right now, but we need to solve that dilemma) -- Best regards, Igor Stasenko.

Aug. 26, 2013

Re: [Pharo-dev] WhatsUp from: 2013-08-19 until: 2013-08-31

by phil＠highoctane.be

### Here's what I've been up to since the last WhatsUp: - Made a working web app stack and started an application that uses it. Kind of works. - Asked around for the Pharo advantage - Pushed Pharo technology for a project and associated funding. So far, so good - Got DBXTalk working with MySQL on OSX - Had holidays :-) ### What's next, until 2013-08-31 (*): - Refresh one site to host my Pharo offering

Aug. 26, 2013