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 <[email protected]> To: dimitris chloupis <[email protected]>; A friendly place where any question about pharo is welcome <[email protected]> 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 <[email protected]> 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 <[email protected]> > To: A friendly place where any question about pharo is welcome > <[email protected]> > 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
