On Nov 10, 2011, at 9:44 PM, Guido Stepken wrote:
Project managers directly can *see*, how much brainpower each programmer is investing and in how far he really cleans up code, defines clear and usable (and used by other coprogrammers) interfaces, or he is messing up the code, producing even more work and costs for others.
You know - "lines not written" -> but they directly show up in the graphs!
do you have an example? A web site because I'm interested for Moose. Stef
Should be standard everywhere, IMHO.
Have fun!
Guido Stepken
Am 10.11.2011 um 21:25 schrieb csrabak@bol.com.br:
As the saying says: "Every person to its taste!", I will not delve in the liking or not of the graphs, but I think the question must be posed:
What practical measures can be extracted of such representation and how can they be used to [help] fulfill the Pharo vision?
-- Cesar Rabak
Em 09/11/2011 19:15, Guido Stepken < gstepken@googlemail.com > escreveu: I like such things, like visualizing class dependencies with girvan newman algorithm:
http://igraph.sourceforge.net/screenshots2.html
or here:
http://www.little-idiot.de/teambuilding/apache-structure.pdf
Should be nice to see, how Pharo has changed over time.
Are there such "reflective tools" available in Pharo? (Should be pretty easy to handover a list of Pharo class dependencies to igraph ...)
Tnx, Guido Stepken