December 2012 - Pharo-users

Browsing inherited methods in Nautilus

by dimitris chloupis

Is it possible to browse inherited methods in Nautilus without going back the hierarchy ? I want the class to display all its methods including the ones that it inherits from super classes.

Dec. 19, 2012

Re: [Pharo-users] Who's in charge of the Pharo Website - some corrections might help.

by Marcus Denker

On Dec 19, 2012, at 9:23 AM, Tim Mackinnon <tamackinnon(a)gmail.com> wrote: > For these kinds of things do you prefer I just raise an issue directly or > does it make sense to post here? > Putting it on the tracker might be a good idea.. this way multiple people can fix it and not just one.. Marcus

Dec. 19, 2012

Re: [Pharo-users] Who's in charge of the Pharo Website - some corrections might help.

by Tim Mackinnon

For these kinds of things do you prefer I just raise an issue directly or does it make sense to post here? Tim -- View this message in context: http://forum.world.st/Who-s-in-charge-of-the-Pharo-Website-some-corrections… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 19, 2012

Re: [Pharo-users] How are people doing TDD?

by Tim Mackinnon

Thanks everyone - it sounds like its not something we were necessarily doing wrong. I will check out some of the suggestions. It seems like there is a need to get some of this improved but I would prefer it be improved for 2.0 - which I will try and download and see how its coming along. Hopefully next year I might find some time to see if I can help out in some small way. Tim -- View this message in context: http://forum.world.st/How-are-people-doing-TDD-tp4659726p4659955.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 19, 2012

Re: [Pharo-users] How are people doing TDD?

by Hernan Wilkinson

Hi Tim I wrote a package called TDDFacilities that helps you to do TDD, for example presing ctrl + t on the code panel saves the method and runs the test. If there is an error, it shows the debugger directly so you can fix the problem. Also if you change the test when debugging, it runs the teardown and setup automatically and so on... I works on Pharo 1.3, I don't remember if it works on 1.4... but should be easy to port it :-) I hope it helps On Tue, Dec 18, 2012 at 7:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I do not know. > I know that hernan wilkinson was using pahro for doing TDD. There was a > package for TDD. > Now we are ready to improve but we need people to submit code because we > are busy. > > Stef > > > > I am curious how people are doing TDD in Pharo? I just tried a session > with > > some of the guys at the UK Smalltalk meetup and I was finding it a bit > > frustrating in the Pharo 1.4 image. > > > > I really like the new Toggle from Class to Test (cmd-j) option that got > > introduced - someone has definitely been writing tests in Pharo - > however it > > does my head in that pressing it after editing a method doesn't jump me > > back. I also find the same problem when editing a test - that pressing > cmd-t > > to run it, just puts a "t" in my source code and doesn't run the test. > > > > On a related theme - I also find it a bit awkward that I often have to > click > > in the source pane to get focus there to enter some code, I'm kind of > > missing some easy keystroke to put focus there so I can just start > typing in > > a new method. > > in nautilus I think that you have tab. > > > > > Am I missing some tricks here? Will the new 2.0 help with some of this (I > > wanted to try it to see but the one click link is broken). I did try the > CI > > link - but I couldn't see where the 1-click job was running. As an aside > - > > there seem to be lots of red balls on Jenkins? > > > > Tim > > > > > > > > -- > > View this message in context: > http://forum.world.st/How-are-people-doing-TDD-tp4659726.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125* Mobile: +54 - 911 - 4470 - 7207 email: hernan.wilkinson(a)10Pines.com site: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

Dec. 18, 2012

Re: [Pharo-users] How are people doing TDD?

by Benjamin

In Pharo 2.0 Nautilus have a better integration of test and of shortcuts. Because of a lack of time (or of people) Nautilus is not maintained in 1.4, since the focus is 2.0 since a while. About the combination with AutoTest, it's really possible (and could be really cool) to implement a AutoTest plugin for Nautilus (the whole plugin mechanism has been designed for AutoTest actually ^^) Can you try in 2.0 and give some feedback ? :) Thanks in advance, Ben On Dec 18, 2012, at 3:32 AM, Stuart Herring wrote: > On 18 December 2012 13:10, Tim Mackinnon <tamackinnon(a)gmail.com> wrote: >> I really like the new Toggle from Class to Test (cmd-j) option that got >> introduced - someone has definitely been writing tests in Pharo - however it >> does my head in that pressing it after editing a method doesn't jump me >> back. I also find the same problem when editing a test - that pressing cmd-t >> to run it, just puts a "t" in my source code and doesn't run the test. >> > I have the same frustration with alt/cmd-t it kind of defeats the > purpose of a keyboard shortcut if you've got to click somewhere on the > screen first before you can use it. > > Have you looked at Autotest? http://squeaksource.com/Autotest.html > It will run tests whenever you save them, and also tries to determine > which tests to run when you modify model classes. The only thing > that's a little bit disappointing is that it doesn't update the test > indicators in the browser. > > I wonder if in Pharo 2.0 someone could combine the concepts of the > in-browser test runner and Autotest. So that accepting changes in the > browser uses the same heuristics autotest does to run the tests, and > then uses the Growl style notifications for failures, with the > green/red/yellow test indicators being updated. > > Regards, > Stuart >

Dec. 18, 2012

Re: [Pharo-users] What makes code unreadable ( was Re: Nautilius Method Source Pane Coloring )

by Attila Magyar

Yes, bad names, long methods, mixed level of abstractions for example Sent from my ASUS Eee Pad dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > > >you mean by "unreadable code" , bad choice of naming methods and variables or something more than that , or something else ? > > >From: Attila Magyar <m.magyar3(a)gmail.com> >To: dimitris chloupis <thekilon(a)yahoo.co.uk>; A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> >Sent: Tuesday, 18 December 2012, 15:46 >Subject: Re: [Pharo-users] Nautilius Method Source Pane Coloring > > >On Tue, Dec 18, 2012 at 10:42 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > >Another example would be not to allow accepting a method if is not commented. Could annoy some people , but I wonder if there is any real benefit in the long ru > > >I think, using comments inside methods and documenting libraries and projects are fairly different topics. I found people often using lots of comments as an excuse for writing unreadable code. But documenting the usage of a library is unarguably important. > > >

Dec. 18, 2012

What makes code unreadable ( was Re: Nautilius Method Source Pane Coloring )

by dimitris chloupis

you mean by "unreadable code" , bad choice of naming methods and variables or something more than that , or something else ? ________________________________ From: Attila Magyar <m.magyar3(a)gmail.com> To: dimitris chloupis <thekilon(a)yahoo.co.uk>; A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> Sent: Tuesday, 18 December 2012, 15:46 Subject: Re: [Pharo-users] Nautilius Method Source Pane Coloring On Tue, Dec 18, 2012 at 10:42 AM, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: Another example would be not to allow accepting a method if is not commented. Could annoy some people , but I wonder if there is any real benefit in the long ru I think, using comments inside methods and documenting libraries and projects are fairly different topics. I found people often using lots of comments as an excuse for writing unreadable code. But documenting the usage of a library is unarguably important.

Dec. 18, 2012

Re: [Pharo-users] Nautilius Method Source Pane Coloring

by Attila Magyar

On Tue, Dec 18, 2012 at 10:42 AM, dimitris chloupis <thekilon(a)yahoo.co.uk>wrote: > Another example would be not to allow accepting a method if is not > commented. Could annoy some people , but I wonder if there is any real > benefit in the long ru I think, using comments inside methods and documenting libraries and projects are fairly different topics. I found people often using lots of comments as an excuse for writing unreadable code. But documenting the usage of a library is unarguably important.

Dec. 18, 2012

Re: [Pharo-users] Nautilius Method Source Pane Coloring

by dimitris chloupis

good point . I have to agree. ________________________________ From: Igor Stasenko <siguctua(a)gmail.com> To: dimitris chloupis <thekilon(a)yahoo.co.uk>; A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> Sent: Tuesday, 18 December 2012, 15:22 Subject: Re: [Pharo-users] Nautilius Method Source Pane Coloring On 18 December 2012 10:42, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > ah sorry I missed "worse even".Â I thought you suggesting that writting long > comments should be counted as negative. > > Also I never asked anybody to start documenting Morphic, I only said I would > prefer if focus was more on documentation than improving existing features. > > Also I dont find that red color thing an importan feature anyway. Though I > do find writting small readable well commented methods extremely important. > If a coder cant figure out what clean code is and why he should do it, I > don't think some red color in the side is going to stop him. > > The problem is that most people start "dirty" with the desire to clean > later, of course they realise that cleaning the code later is actually a lot > of work and never do it. > I did see that happen a lot when I was doing python for blender addons. > Fortunately the situation with pharo is a lot better. > > I am actually considering forcing clean code , with my project . Because I > will be redesigning all those tools of course basing it in the existing > great > work that there is . And was wondering how much a bad idea that is. For > example moving comments outside the method source code using something like > meta tags and forcing the method never to exceed 10 lines. Sound like a bad > idea to me, but still makes me think if there is potential. > > Another example would be not to allow accepting a method if is not > commented. Could annoy some people , but I wonder if there is any real > benefit in the long run. > this mode would be not very nice for quick prototyping. About the topic: yes, counting the number of AST elements would be better metric for determining whether code "stinks" or not :) -- Best regards, Igor Stasenko.

Dec. 18, 2012