New subject: Migration of tools from Mondrian into Roasal - project status

7 May 2013

Hi!

There is a compilation of the work I have to do in order to remove Mondrian
from Moose. If you find something irrelevant or missing or you have a note
I should consider, I will appreciate it!

Cheers,
Jura

MOViewRender is used for visualisations:

   1. UML class diagram
   2. View Multiplication constelation
   3. Side by Side Duplication
   4. System complexity
   5. Namespace Hierarchy
   6. System Overview
   7. Within overall hierarchy
   8. Package-wise System Complexity
   9. Evolution matrix
   10. Hierarchy evolution

MOViewRenderer is used in classes (package Mondrian is not included in this
list):

   1. DSMBuilder
   2. DSMExample
   3. DudeMultiplicationGroup
   4. FAMIXClass
   5. FAMIXClassGroup
   6. FAMIXNamespaceGroup
   7. FAMIXPackageGroup
   8. GlamorousHealth
   9. GLMBrowser
   10. GLMMondrianEasel
   11. GLMMondrianPresentation
   12. GLMMondrianPresentationTest
   13. GLMMorphicMondrianRenderer
   14. GTVisualizations
   15. HismoClassHistoryGroup
   16. MOCycleTableSample
   17. MOFameView
   18. MOLayerTable
   19. PackageBlueprint
   20. PPParser
   21. TwoDimensionsDistributionMap

MOFormsBuilder is used (package Mondrian is not included in this list):

   1. MOFameView>fameShape
   2. MOCycleTableSample>>exampleCycleTable
   3. HismoClassHistoryGroup>>viewEvolutionMatrixOn:

Other things:

   1. Create ROGraphVizLayout (used in Annotation Constellation)
   2. DSM uses borderStyle. Mandatory? Should we implement it in Roassal?

Obsolete code? Remove it?:

   1. MooseEntity>>openInEasel (it is not called and there is MOEasel)
   2. FAMIXClassGroup>>viewDuplicationComplexity (annotation is commented)
   3. #browsePackageBlueprints
   4. FAMIXNamespace>>accessTo: has flag "maybe not more useful"
   5. FAMIXImplicitVariable does not understand parentType (produces does
   not understand debugger).