Hi Mariano, Thank you for the feedback, I've updated the dependency browser package in SqueakSource, have a look for the latest package releases or evaluate the installation script again found in http://swikicaicyt.homeip.net/WebOpus/65 2009/12/26 Mariano Martinez Peck <marianopeck@gmail.com>:
On Sat, Dec 26, 2009 at 10:06 PM, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Hi Mariano! Â Nice to see you liked the Dependency Browser, let's clarify some points about it then,
2009/12/26 Mariano Martinez Peck <marianopeck@gmail.com>:
Hi Hernán: First let me say that this tool is really great and useful. It is helping me a lot to build the metacello configurations. Now, I have a couple of questions:
1) What do the colors mean ? (red, orange, etc). I read here
http://cs.hernanmorales.com.ar/projects/dependencyBrowser/DBrowser-en.php but found nothing :(
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 :)
Ok, done. The official package home page is under http://www.caicyt.gov.ar/letodoc/paquetes-publicados
Hey! I have more questions :)
3) Please, take a Pharo dev image and you will see that the package OCForOB for example, only depends on OmniBrowser and OB-Standard (using dependency browser). However, that package also depends on OCompletion I think. Look for example the method
OBTextPanel >> createCompletionController (category ocforob)
and you will see that it uses the class OController which is from the package OCompletion....So, shouldn't be OCompletion a dependency ?
True, it is fixed now in the latest release.
4) There are certain packages that are not listed in the dependency browser. Examples OB-Standard, OB-Morphic, O2-Standard , etc...most of them (maybe all) seem to have the pattern XXX-YYY. Do you know what can be the problem here? Maybe something related to what you told me about normalized and un-normalized? I would really like to see these packages also.
No, this was a missing line in the package listing. Fixed too.
5) Why there are some packages that have their self as dependency ? For example, take OmniBrowser and you will see that has a dependency OmniBrowser also (as Inheritance and Reference).
May be useful to see internal dependencies? Cheers, Hernán