[Moose-dev] Re: Migration of tools from Mondrian into Roasal - project status

MOViewRender is used for visualisations: • UML class diagram • View Multiplication constelation • Side by Side Duplication • System complexity • Namespace Hierarchy • System Overview • Within overall hierarchy • Package-wise System Complexity • Evolution matrix • Hierarchy evolution

MOViewRenderer is used in classes (package Mondrian is not included in this list): • DSMBuilder • DSMExample • DudeMultiplicationGroup • FAMIXClass • FAMIXClassGroup • FAMIXNamespaceGroup • FAMIXPackageGroup • GlamorousHealth • GLMBrowser • GLMMondrianEasel • GLMMondrianPresentation • GLMMondrianPresentationTest • GLMMorphicMondrianRenderer • GTVisualizations • HismoClassHistoryGroup • MOCycleTableSample • MOFameView • MOLayerTable • PackageBlueprint • PPParser • TwoDimensionsDistributionMap MOFormsBuilder is used (package Mondrian is not included in this list): • MOFameView>fameShape • MOCycleTableSample>>exampleCycleTable • HismoClassHistoryGroup>>viewEvolutionMatrixOn: Other things: • Create ROGraphVizLayout (used in Annotation Constellation) • DSM uses borderStyle. Mandatory? Should we implement it in Roassal? Obsolete code? Remove it?: • MooseEntity>>openInEasel (it is not called and there is MOEasel) • FAMIXClassGroup>>viewDuplicationComplexity (annotation is commented) • #browsePackageBlueprints • FAMIXNamespace>>accessTo: has flag "maybe not more useful" • FAMIXImplicitVariable does not understand parentType (produces does not understand debugger). _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev