July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fancier Debugger

by Bernat Romagosa

I'd use it :) 2011/7/18 Camillo Bruni <camillo.bruni(a)inria.fr> > Hi everyone, > > last friday I spent some 20mins on improving the debugging experience (at > least for me) by doing to following: > > - removed many "core" message sends from the context stack in the debugger > - automatically expand the context stack if the last stackframe is selected > > For the first task I added a method which filters out all message sends > which IMO are mostly uninteresting when debugging (right now still a but > dirty implemented..): > > - #ifTrue: #ifFalse.... and so forth > - iteration internals on Collections: #do: > - Message sends to Blocks / MethodContexts: #on:do: #value: ... > - Basic accessors on dicts: #at: #at:put: .... > > at least for me this helps me incredibly with locating important pieces of > code in the debugger e.g. reducing the noise.. > > > So is there any interest in this to be added? (of course with a settings > switch to turn it on/off... in case you work on the filtered messages) > > If so I will implement it a bit cleaner and add a decent settings entry... > > cami > -- Bernat Romagosa.

July 18, 2011

Re: [Pharo-project] [Seaside] Problem with announcements in Seaside when using Pharo 1.3

by Philippe Marschall

On 07/17/2011 08:26 PM, StÃ©phane Ducasse wrote: > Hi lukas > > in 1.3 we introduced on:fork: to ensure that for example a system announcement is processed even if a user announcement would break for the same registry. Every time you try to be clever you introduce new problems, so don't try to be clever. The only way to fix broken code is to fix broken code, not by adding additional hacks. Cheers Philippe

July 18, 2011

Re: [Pharo-project] Stubbing class-side methods

by Michael Roberts

is MyClass a domain class or a (unit) test class? thanks, Mike On Sun, Jul 17, 2011 at 10:45 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I keep coming up against this situation over and over in testing. > > MyClass>>doSomethingWorthTesting > Â Â ... > Â Â now := DateAndTime now. > Â Â ... > > I want to control DateAndTime class>>now to make this test determinate and > simulate interesting edge cases, but can't figure out a good way. In Ruby, I > could easily stub it because it's not a live system (or use dependency > injection), but here I don't want to mess with the real DateAndTime class in > case something goes wrong and leaves my system dirty. > > I really hate using dependency injection for this kind of thing (especially > without Ruby's default parameter values). I've been creating MyClass>>now > and stubbing that. Am I being paranoid, should I just hijack the real class > and fix it when I'm done? What's the best way to do this? > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Stubbing-class-side-methods-tp3674065p3674065.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

July 18, 2011

[Pharo-project] Fancier Debugger

by Camillo Bruni

Hi everyone, last friday I spent some 20mins on improving the debugging experience (at least for me) by doing to following: - removed many "core" message sends from the context stack in the debugger - automatically expand the context stack if the last stackframe is selected For the first task I added a method which filters out all message sends which IMO are mostly uninteresting when debugging (right now still a but dirty implemented..): - #ifTrue: #ifFalse.... and so forth - iteration internals on Collections: #do: - Message sends to Blocks / MethodContexts: #on:do: #value: ... - Basic accessors on dicts: #at: #at:put: .... at least for me this helps me incredibly with locating important pieces of code in the debugger e.g. reducing the noise.. So is there any interest in this to be added? (of course with a settings switch to turn it on/off... in case you work on the filtered messages) If so I will implement it a bit cleaner and add a decent settings entry... cami

July 17, 2011

Re: [Pharo-project] [Seaside] problem in configuration of swazoo

by Tudor Girba

Thanks, Janko. It works now. Cheers, Doru On 17 Jul 2011, at 23:56, Janko MivÅ¡ek wrote: > Hi Tudor, > > Try now. I published Swazoo once again, but I'm pretty sure I did > exactly that correction already. Anyway. I hope it works now well. > > Best regards > Janko > > S, Tudor Girba piÅ¡e: >> Hi Janko, >> >> The latest version of the ConfigurationOfSwazoo has a problem. >> >> Specifically, version '2.3.0.0' was recently changed to point to the Swazoo package version 'Swazoo-2.3beta2.6'. However, in Monticello we only have 'Swazoo-janko.3beta2.6'. >> >> Could you fix it, or should I try to do it? >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Speaking louder won't make the point worthier." >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

July 17, 2011

Re: [Pharo-project] [Seaside] problem in configuration of swazoo

by Janko MivÅ¡ek

Hi Tudor, Try now. I published Swazoo once again, but I'm pretty sure I did exactly that correction already. Anyway. I hope it works now well. Best regards Janko S, Tudor Girba piÅ¡e: > Hi Janko, > > The latest version of the ConfigurationOfSwazoo has a problem. > > Specifically, version '2.3.0.0' was recently changed to point to the Swazoo package version 'Swazoo-2.3beta2.6'. However, in Monticello we only have 'Swazoo-janko.3beta2.6'. > > Could you fix it, or should I try to do it? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

July 17, 2011

Re: [Pharo-project] [Seaside] Problem with announcements in Seaside when using Pharo 1.3

by Tudor Girba

I am sure that improving the system is on everyone's intention. Now, let's go back to the problem and see what we can do about it :). Cheers, Doru On 17 Jul 2011, at 23:45, Lukas Renggli wrote: >> It is easy to judge other work, but I can tell you that we are concerned about size and quality much more than average people. >> I'm mainly doing pharo on my free time and I'm spending a lot of energy in making it the best system I dream about. >> >> Now when is the last time that you said to us: guys you are doing a good job? >> Have a look at your emails and you will be surprised. Sometimes positive feedback is much better than absence of negative ones. > > I did not judge your work. I only pointed out that if new things are > integrated (like announcements) it might break with existing users > (and how, in this particular case). I am fine if this is the perfect > implementation for Moose, Glamour and Pharo itself; you just cannot > expect that it is perfect for everybody. There are always users that > need something else (in this case I suspect many); and it would be > cool if that could be facilitated. > > Lukas > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

July 17, 2011

[Pharo-project] problem in configuration of swazoo

by Tudor Girba

Hi Janko, The latest version of the ConfigurationOfSwazoo has a problem. Specifically, version '2.3.0.0' was recently changed to point to the Swazoo package version 'Swazoo-2.3beta2.6'. However, in Monticello we only have 'Swazoo-janko.3beta2.6'. Could you fix it, or should I try to do it? Cheers, Doru -- www.tudorgirba.com "Speaking louder won't make the point worthier."

July 17, 2011

[Pharo-project] [Seaside] Problem with announcements in Seaside when using Pharo 1.3

by Lukas Renggli

> It is easy to judge other work, but I can tell you that we are concerned about size and quality much more than average people. > I'm mainly doing pharo on my free time and I'm spending a lot of energy in making it the best system I dream about. > > Now when is the last time that you said to us: guys you are doing a good job? > Have a look at your emails and you will be surprised. Sometimes positive feedback is much better than absence of negative ones. I did not judge your work. I only pointed out that if new things are integrated (like announcements) it might break with existing users (and how, in this particular case). I am fine if this is the perfect implementation for Moose, Glamour and Pharo itself; you just cannot expect that it is perfect for everybody. There are always users that need something else (in this case I suspect many); and it would be cool if that could be facilitated. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 17, 2011

[Pharo-project] Stubbing class-side methods

by Sean P. DeNigris

I keep coming up against this situation over and over in testing. MyClass>>doSomethingWorthTesting ... now := DateAndTime now. ... I want to control DateAndTime class>>now to make this test determinate and simulate interesting edge cases, but can't figure out a good way. In Ruby, I could easily stub it because it's not a live system (or use dependency injection), but here I don't want to mess with the real DateAndTime class in case something goes wrong and leaves my system dirty. I really hate using dependency injection for this kind of thing (especially without Ruby's default parameter values). I've been creating MyClass>>now and stubbing that. Am I being paranoid, should I just hijack the real class and fix it when I'm done? What's the best way to do this? Thanks. Sean -- View this message in context: http://forum.world.st/Stubbing-class-side-methods-tp3674065p3674065.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 17, 2011