 |
| Seaside dependencies (click to enlarge) |
There is one circular dependency ("Seaside-Core" and "Seaside-VisualWorks-Core"), but this is probably introduced in the porting to VisualWorks. From what I can see, removing the dependency should be trivial.
Wednesday, March 7, 2012
Analyzing Dependencies in Seaside
The image below shows a dependency analysis using DTangler on Seaside for VisualWorks Smalltalk 7.8.1:
From the DSM it looks like Seaside is layered properly. My initial reaction is that this looks well engineered.
There is one circular dependency ("Seaside-Core" and "Seaside-VisualWorks-Core"), but this is probably introduced in the porting to VisualWorks. From what I can see, removing the dependency should be trivial.
There is one circular dependency ("Seaside-Core" and "Seaside-VisualWorks-Core"), but this is probably introduced in the porting to VisualWorks. From what I can see, removing the dependency should be trivial.
Subscribe to:
Post Comments (Atom)
1 comment:
That doesn't look right "Seaside-VisualWorks-Core" should depend on "Seaside-Core" with no dependency in the other direction. Please file a bug.
Post a Comment