- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Spec tabs, which one is active ?

by Erwan Douaille

2013/8/26 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > A workaround could be that when a tab is selected, it set an instance > variable with the correct value. > > Yes, it will be cool. But i didn't *find* something like "whenTabSelectionChanged:" in tabManager or tab model. How can i catch the selection event? > This way , you can always do something like > > myCanvas generates. > > where myCanvas is set by the tab. > And in addition, you do not have to use a switch case :) > > yes > Ben > > On Aug 26, 2013, at 3:58 PM, Erwan Douaille <douailleerwan(a)gmail.com> > wrote: > > Hi, > > I'm using TabManager and i would like to know which tab is active. I > didn't found any methods for that. > Any clue ? > > In UIPainter, i will use it to know which tab canvas i have to generate. > > Thanks :) > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com> > > > Thanks :) -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 27, 2013

Re: [Pharo-dev] Rubrik, scroll to end?

by plantec

Hi, I've added #scrollToTop and #scrollToBottom in RubScrolledTextMorph. Notice that you can use a RubConfigurationChanged announcement to reconfigure views: | consoleTextModel | consoleTextModel := RubScrolledTextModel new. (consoleTextModel newScrolledText beWrapped embeddedInMorphicWindowLabeled: 'Rubric try') openInWorld. consoleTextModel setText: 'some text .....'. consoleTextModel announce: (RubConfigurationChanged new configurationBlock: [:view | view scrollToBottom ]) or: | consoleTextModel | consoleTextModel := RubScrolledTextModel new. (consoleTextModel newScrolledText beWrapped embeddedInMorphicWindowLabeled: 'Rubric try') openInWorld. consoleTextModel setText: 'some text .....'. consoleTextModel reconfigureViewWith: [:view | view scrollToBottom ]. Cheers Alain Le 23 aoÃ»t 2013 Ã 11:49, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > in an incredible ugly way, yes... :) > > consoleTextModel := RubScrolledTextModel new. > consoleTextArea := consoleTextModel newScrolledText beWrapped. > > ... > > consoleTextArea scrollPane > vScrollbarValue: 1; > updateScrollbars. > > On Aug 23, 2013, at 11:44 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Esteban, >> >> Did you success to do it? do you know how to "scroll-to-end" in spec/morph? >> >> MartÃn >> >> >> On Thu, Aug 15, 2013 at 5:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi guys, >> >> anyone knows how to do a "scroll-to-end" with rubrik? >> >> thanks, >> Esteban >> >> >

Aug. 27, 2013

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

by Igor Stasenko

On 19 August 2013 07:00, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > Mainly working on TxModel rendering with Athens and laying it out. Have slow but steady progress (need to solve a lot of tiny details, along the way > ### What's next, until 2013-08-31 (*): > Finish a text view morph and put more flesh in text layout & rendering engine, provide a coordinate feedback (point<->position).. and start thinking about notificaitons for doing smart updates (so when user edits or navigates the text, to update minimal portions on screen/recompute minimal necessary layout) > (*) we'll be expecting results by then ;) > > -- Best regards, Igor Stasenko.

Aug. 27, 2013

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

by Igor Stasenko

done https://pharo.fogbugz.com/default.asp?11465#83505 On 26 August 2013 22:54, Camillo Bruni <camillobruni(a)gmail.com> wrote: > 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. > > -- Best regards, Igor Stasenko.

Aug. 27, 2013

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

by Igor Stasenko

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 > > well, it won't work that way.. #inspector: returns the inspector model , but not the actual morph i don't know how to get the window morph from it (maybe its easy?).. I mean, even if you change this to use #inspector: instead of #inspect: Morph>>inspectInMorphic: evt evt hand attachMorph: ((Smalltalk tools inspect: self) extent: 300@200) it won't work (#extent: did not understood by inspector object, neither you can attach it to hand). So, i forced to change this method to look like this: inspectInMorphic: evt Smalltalk tools inspect: self yeah.. i will open the issue then. -- Best regards, Igor Stasenko.

Aug. 27, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

Aug. 27, 2013

Re: [Pharo-dev] [update 3.0] #30345

by StÃ©phane Ducasse

Thanks I plan to retry to do some integration now that I have the information about what to do when it fails. On Aug 27, 2013, at 10:05 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 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

[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