csrabak wrote: > > > > > Em 31/12/2009 15:09, Stéphane Ducasse < [email protected] > > escreveu: > >> Stan > >> My point is not to discourage you. :) Documentation is a state of >> mind and a large valuable job. Now we can do the same as you said >> (a guy ask and the others try to answer and we write comments that >> are pushed into the system). > >> A first step is >> - make a list of the classes that are missing comments: > > +--------+-------+-------+ > | Image | update|missing| > | | |comment| > +--------+-------+-------+ > |1.0-dev | 10502 | 1831 | > +--------+-------+-------+ > |1.1-core| 11098 | 703 | > +--------+-------+-------+ > | 1.1-dev| 11098 | 1795 | > +--------+-------+-------+ > > >> - pick one aweek and via the mailing-list make it better and after >> - we integrate it. > >> First it would be fun and we would get one class commented at the >> end of the week. > > HTH > > -- > Cesar Rabak >
for info, I ran code critics on Lukas's quasi-release http://www.seaside.st/distributions/Seaside-3.0a5.app.zip which is essentially web dev without O2 I believe. (Code critics I can't get to work in web dev) Taking out spelling, there are about 30000 items flagged, of which 4802 long methods. In an ideal world, it would be nice if the whole image passed code critics. > - pick one aweek and via the mailing-list make it better and after > - we integrate it. Well the one that's entertaining me at the moment is JSObject, but I imagine people would rather start with a core class?. ...Stan -- View this message in context: http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-knowledge-Knowledge-reuse-tp4236694p4237295.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
