Mariano Martinez Peck wrote: > > On Sat, Dec 26, 2009 at 10:06 PM, Hernán Morales Durand < > [email protected]> wrote: >> >> Colors were originally for idenfitying dependency types of external >> packages, but the package infos names aren't normalized, E.g. >> Normalized name = "Collections", Un-normalized name = >> "Collections-Strings", hence you will see a lot of false external >> packages colorized. >> >> Orange -> Dependecy of class reference of "external" package, or class >> reference in un-normalized package name. >> Brown -> Dependency of external package loose method, or loose method >> in un-normalized package name. >> Red -> Dependency of inheritance, or inheritance in un-normalized package >> name. >> Blue -> Dependency of a unsolved binding (like a class not present in >> the image). >> > > Thanks for the explanation. Now, as a good programmer you can reuse this > explanation and put it in the website :) > >
Hmm, wouldn't it be handy if the documentation were maintained in a Wiki, so the receiver of the reply could just paste it into the correct place, and it would be loaded into the image ;) Otherwise, this could end up in the 'tacit knowledge' bucket. see http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-knowledge-Knowledge-reuse-td4236694.html#a4236694 http://n2.nabble.com/Solving-the-documentation-problem-Capturing-tacit-knowledge-Knowledge-reuse-td4236694.html#a4236694 ...Stan -- View this message in context: http://n2.nabble.com/about-DependencyBrowser-tp4218735p4254322.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
