You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pharo versions 8 and 9 allow from UML to give the different dependencies between the classes of a package.
An example with Kendrick's Core sub packages (tags).
But we note the following fact, when we select all the Kendrick sub packages, we cannot see the different dependencies between the sub packages because the representation that UML allows us to have is very minimal (this is due to the large number of classes).
We are not looking at class diagram, but more reference dependencies even if in a dynamic type language this is more difficult to be exhaustive about them. There is a dependency browser inside Pharo that allow you do browse them in the context of a package.
We need to check what classes depend on, whether it is on our own classes or on external ones.
For this a dependency diagram would help a lot
The text was updated successfully, but these errors were encountered: