Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-Famix
New issue 509 by andreho...(a)gmail.com: Modularization Quality Metric
http://code.google.com/p/moose-technology/issues/detail?id=509
We implemented the Bunch metrics of coupling and cohesion as quality
metrics for existing packages (FAMIXPackage) and namespaces
(FAMIXNamespace).
Now the idea is to implement the Modularization Quality Metric as a quality
metric for existing group of packages (FAMIXPackageGroup) and namespaces
(FAMIXNamespaceGroup).
Pointer to the papers that propose the metrics:
Using Automatic Clustering to Produce High-Level System Organizations of
Source Code (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=693283)
Bunch: A Clustering Tool for the Recovery and Maintenance of Software
System Structures
(http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=792498)
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 644 by cy.delau...(a)gmail.com: A fly by help to show each time the
source code of an entity
http://code.google.com/p/moose-technology/issues/detail?id=644
Maybe it would be interesting when navigating in moose, to always have a
fly by help that show the source code of an element
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Glamour
New issue 582 by tudor.gi...(a)gmail.com: Watcher support in Glamour
http://code.google.com/p/moose-technology/issues/detail?id=582
Like we now have a statusbar, we should also have a detailed preview shown
in a floating Watcher window. The behavior would be similar to Quick Look
on Mac.
Updates:
Summary: Hapao should provide a legend in every window
Comment #3 on issue 602 by tudor.gi...(a)gmail.com: Hapao should provide a
legend in every window
http://code.google.com/p/moose-technology/issues/detail?id=602
Then let's name the issue for what it should do.
Status: New
Owner: ----
CC: tudor.girba
Labels: Type-Defect Priority-Medium
New issue 489 by jfabry: Glamour: action list without the dropdown
http://code.google.com/p/moose-technology/issues/detail?id=489
I have a Glamour pane that is an actionList where I do 5
populate:on:entitled:with: so that the pane has 5 buttons. Now what happens
is that the pane also has a dropdown menu, with the same actions as the
buttons. This menu should not be there according to Doru ...
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Hapao Component-Mondrian
New issue 600 by alexandr...(a)gmail.com: Popup does not work properly
http://code.google.com/p/moose-technology/issues/detail?id=600
It takes times to appear and does not always appears.
I am not sure where the problem comes from. Probably Mondrian. The popup
has problems probably because the visualization takes time to render.
Classes in Hapao are nested within a very large node. This prevent classes
to be catched as a bitmap.
Tested on Pharo 1.3.
Thanks Laurent & Patrick
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Fame
New issue 680 by andreho...(a)gmail.com: Exporting metrics to CSV and XML
http://code.google.com/p/moose-technology/issues/detail?id=680
We should export the metrics from Moose models to CSV and XML.
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Fame
New issue 679 by andreho...(a)gmail.com: Exporting metrics to mse
http://code.google.com/p/moose-technology/issues/detail?id=679
Just to document the issue.
As most of the metrics are not described at the Fame level we are losing
this information when we export a model to MSE in Moose. We know that most
of the metrics can be recalculated in the model, but in some cases they
cannot.
For example, when exporting in Moose a Java (VerveineJ) model we lose the
metrics cyclomaticComplexity (CYCLO) and numberOfStatements (NOS) and we
cannot recalculate them.