- Pharo-users - lists.pharo.org

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

by dimitris chloupis

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. ________________________________ From: Sven Van Caekenberghe <sven(a)stfx.eu> 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, 11:21 Subject: Re: [Pharo-users] Nautilius Method Source Pane Coloring On 18 Dec 2012, at 10:05, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > There is no such thing as too lengthy comments or too many comments as far as me is concerned > Actually I would prefer if all that effort you are asking here would be spent on documenting those libraries in the first place. Trying to figure out Morphic by reading code is definetly not fun. Euh, I am not sure what your remark has to do with what I wrote about a specific feature, although I can understand your frustration with Morphic. All the open source code that I wrote is clean, unit tested and documented. I don't think you can ask anybody to start documenting something like Morphicâ¦ > From: Sven Van Caekenberghe <sven(a)stfx.eu> > To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > Sent: Tuesday, 18 December 2012, 10:43 > Subject: [Pharo-users] Nautilius Method Source Pane Coloring > > Hi, > > The way Nautilus colors method source panes is absolutely great: if reminds you of paying attention to long methods in a gentle way. > > However, right now the metric is 'number of characters in method source', while it should be more related to complexity. > > For example, using long names for variables or messages will be counted as negative towards this metric. Worse even, lots of comments, which is good most of the time, also counts as negative. > > Number of nodes in the AST would be one solution, but maybe a too expensive one. > > Maybe quickly scanning for tokens while skipping whitespace and comments and then counting the tokens would be doable ? > > Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 18, 2012

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

by Sven Van Caekenberghe

On 18 Dec 2012, at 10:22, Attila Magyar <m.magyar3(a)gmail.com> wrote: > I usually use two different browser for the test and code. But I still haven't figured out how to use keyboard shortcuts effectively. Autotest can help to run the test automatically after accepting the code. Yeah, that is what I do as well: use multiple browsers for multiple contexts, usually with an open test runner as well (with a specific subselection of tests). I like shortcuts and I absolutely want them, but Smalltalk is quite visual for me, and I use the mouse/trackpad a lot. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 18, 2012

Re: [Pharo-users] Any recommended VPS Hosting for Pharo?

by Bernat Romagosa

I've used VPSLink without an issue for two years. Cheap, fast and reliable. I also got a VPSSlim slice, they had a Black Friday offer you couldn't refuse (17â¬/year), but I can't tell you much because I've only had it for less than a month. Cheers! 2012/12/18 Sven Van Caekenberghe <sven(a)stfx.eu> > I have been using an Amazon AWS EC2 Micro Instnance for more than a year > (it is free in the first year). > > http://aws.amazon.com/ec2 > http://stfx.eu (and everything on top of that) > > I has a great management interface. The only disadvantage is the CPU > throttling in the micro instance, more than 1 minute of 100% CPU amd you > get a very slow machine. > > In terms of memory: you hardly need 100Mb per imageâ¦ > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > On 18 Dec 2012, at 01:22, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > > > Does somebody runs Pharo in a VPS/Cloud environment? > > Can that somebody recommend its hosting? > > > > I prefer Ubuntu/Debian solutions instead of CentOS (which seems to be the > > norm), but mainly because AFAIK there are no pre-built binaries for it. > > > > I'll appreciate any real use experience, comments, discussions and flame > > wars about this. :) > > > > Regards! > > > > -- > > Esteban > > -- Bernat Romagosa.

Dec. 18, 2012

A post on Smalltalk by a Ruby developer

by Miguel Moquillon

The write is about class variables in Ruby and in Smalltalk. The author, by looking for the origin of them (in order to have a better understanding of them), has discovered Smalltalk. He then explore the definition of the class and class instance variables both in Smalltalk and in Ruby. http://patshaughnessy.net/2012/12/17/ruby-smalltalk-and-class-variables -- Miguel Moquillon

Dec. 18, 2012

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

by Attila Magyar

I usually use two different browser for the test and code. But I still haven't figured out how to use keyboard shortcuts effectively. Autotest can help to run the test automatically after accepting the code. Sent from my ASUS Eee Pad Tim Mackinnon <tamackinnon(a)gmail.com> wrote: >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. > >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. >

Dec. 18, 2012

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

by Sven Van Caekenberghe

On 18 Dec 2012, at 10:05, dimitris chloupis <thekilon(a)yahoo.co.uk> wrote: > There is no such thing as too lengthy comments or too many comments as far as me is concerned > Actually I would prefer if all that effort you are asking here would be spent on documenting those libraries in the first place. Trying to figure out Morphic by reading code is definetly not fun. Euh, I am not sure what your remark has to do with what I wrote about a specific feature, although I can understand your frustration with Morphic. All the open source code that I wrote is clean, unit tested and documented. I don't think you can ask anybody to start documenting something like Morphicâ¦ > From: Sven Van Caekenberghe <sven(a)stfx.eu> > To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > Sent: Tuesday, 18 December 2012, 10:43 > Subject: [Pharo-users] Nautilius Method Source Pane Coloring > > Hi, > > The way Nautilus colors method source panes is absolutely great: if reminds you of paying attention to long methods in a gentle way. > > However, right now the metric is 'number of characters in method source', while it should be more related to complexity. > > For example, using long names for variables or messages will be counted as negative towards this metric. Worse even, lots of comments, which is good most of the time, also counts as negative. > > Number of nodes in the AST would be one solution, but maybe a too expensive one. > > Maybe quickly scanning for tokens while skipping whitespace and comments and then counting the tokens would be doable ? > > Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 18, 2012

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

by dimitris chloupis

There is no such thing as too lengthy comments or too many comments as far as me is concerned Actually I would prefer if all that effort you are asking here would be spent on documenting those libraries in the first place. Trying to figure out Morphic by reading code is definetly not fun. ________________________________ From: Sven Van Caekenberghe <sven(a)stfx.eu> To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> Sent: Tuesday, 18 December 2012, 10:43 Subject: [Pharo-users] Nautilius Method Source Pane Coloring Hi, The way Nautilus colors method source panes is absolutely great: if reminds you of paying attention to long methods in a gentle way. However, right now the metric is 'number of characters in method source', while it should be more related to complexity. For example, using long names for variables or messages will be counted as negative towards this metric. Worse even, lots of comments, which is good most of the time, also counts as negative. Number of nodes in the AST would be one solution, but maybe a too expensive one. Maybe quickly scanning for tokens while skipping whitespace and comments and then counting the tokens would be doable ? Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 18, 2012

Nautilius Method Source Pane Coloring

by Sven Van Caekenberghe

Hi, The way Nautilus colors method source panes is absolutely great: if reminds you of paying attention to long methods in a gentle way. However, right now the metric is 'number of characters in method source', while it should be more related to complexity. For example, using long names for variables or messages will be counted as negative towards this metric. Worse even, lots of comments, which is good most of the time, also counts as negative. Number of nodes in the AST would be one solution, but maybe a too expensive one. Maybe quickly scanning for tokens while skipping whitespace and comments and then counting the tokens would be doable ? Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Dec. 18, 2012

Re: [Pharo-users] Any recommended VPS Hosting for Pharo?

by Sven Van Caekenberghe

I have been using an Amazon AWS EC2 Micro Instnance for more than a year (it is free in the first year). http://aws.amazon.com/ec2 http://stfx.eu (and everything on top of that) I has a great management interface. The only disadvantage is the CPU throttling in the micro instance, more than 1 minute of 100% CPU amd you get a very slow machine. In terms of memory: you hardly need 100Mb per imageâ¦ -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill On 18 Dec 2012, at 01:22, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Does somebody runs Pharo in a VPS/Cloud environment? > Can that somebody recommend its hosting? > > I prefer Ubuntu/Debian solutions instead of CentOS (which seems to be the > norm), but mainly because AFAIK there are no pre-built binaries for it. > > I'll appreciate any real use experience, comments, discussions and flame > wars about this. :) > > Regards! > > -- > Esteban

Dec. 18, 2012

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

by Camillo Bruni

You should definitely try 2.0. We added tons of shortcuts to - navigate source code - change focus (source / method / class / package) - refactor - run tests ... and many more. If you open the new browser in 2.0 click on the triangle on the top left of the window and select "Shortcuts description" for a complete list. On 2012-12-17, at 23:33, Stuart Herring <st-lists(a)stuartherring.com> 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