Thanks Lukas. I was looking at the pdf about the dependencies of OB but it is different to what you told me at the beginning. For example, you told me:
OB-Refactory --> Refactoring-Core, OB-Standard OB-Regex --> Refactoring-Core, OB-Standard
But in the pdf I see OB-Regex --> OB-Refactory
I just need to know the DIRECT dependencies. Those classes you use, extend, reference or whatever. If OB-Regex used directly classes from OB-Standard for example, ok, then it is a dependency. But, if you told me OB-Standard just because it was a dependency for OB-Refactory (and this was a dependency for OB-Regex), then, I don't care about it. I just need to know the direct dependencies (not also the dependencies or my dependencies haha )
I don't get what you mean, but the PDF is correct because it is created from the code. The PDF only contains direct dependencies, transitive ones are removed, only the information you need to know to load correctly. We create the Seaside loaders with this information. Lukas
Cheers
Mariano
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch