Hi Lukas, Sorry to answer you so late :-(
for understanding packages we have developed different views: 1- package surface blueprints: they give a detailled and simple representation of the incoming/outgoing references to/from a package. It visualizes aslo the intra-references. 2- package references fingerprints: they are based on the principle of Similarity Matrix. The aime of these views is to give an idea about the contextual cohesion of a given package (the coupling between classes is based on the co-using). In other words, these views help to understand the package interfaces (package classes which are referenced from the outside 'In-Interface', and package classes which do reference to the outside 'Out-Interface').
to use these views you should download Cook bundle 'last version'.
let me know if you any question.
bests, Hani
On Jan 5, 2008, at 22:54 PM, Stéphane Ducasse wrote:
On 5 janv. 08, at 20:57, Lukas Renggli wrote:
Thanks for your answers. I had a look at MudPie and modified it slightly to suit my exact needs. If you are interested have a look at the attached visualization. Open the SVG file in Safari, the tooltips on the edge labels give the reason for the dependencies.
@Stef: I would be interested to see a package blueprint of the code.
I will ask hani since we were rewriting the code from scratch and he took the lead I guess that you will get an answer by monday afternoon since he does not connection at home.
I would like to know (no answer before some months) how you imagine seaside 2.9 With layers?
You do not have that cycles in the pictures this is already something good :)
Why seaside code is depending on seaside examples :)
But this is a wonderful case study. Thanks a lot.
@Adrian: Thanks for your offer. I think Hapax is less useful in our case. We know the code pretty well, we are more looking at "hard" dependencies right now.
Lukas
-- Lukas Renggli http://www.lukas- renggli.ch<packages.svg>_____________________________________________ _ _ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev