29 Jun
2011
29 Jun
'11
10:04 a.m.
Isn't
there a test supposed to do that? Or does it just work on MooseModel menu?
I think we should write a test that take all entries in menus and run them.
On a PackageGroup, some commands are strange or does not work:
- utilities
- bookmark entity: it does not update the glamour browser and we should close and reopen
the browser to see bookmarked entities. It also changes the name of my group... which is
not the behavior that I want.
old stuff to remove? I think there is a new bookmark mechanism (with metanool?). If only
I knew where it was... - createLoadScriptForGroup: I tried with a new
class name, the class is not created. When I use MooseScripts, I have a DNU because of
UIManager
The script does not handle class creation -> bug if you want. - visualize:
- browse package blueprint: DNU
that's bad (package blueprints are still lacking tests).
#menuItems: does not exist in Mondrian anymore. (maybe a deprecated would have been
good?) What's the replacement?
- customizable eyesee chart: should have a
progress bar when the computing is slow.
- Dependencies (cycles): seems not working (loop ?)
MODominanceTreeLayout does not scale. Viz can be removed if necessary but it's a
simple viz yet it shows how to combine multiple things (famix, graph, mondrian) -->
good for demo/tutorial - distributionMap for these elements: I just did
"next", "finish" without configuring anything, I have a DNU
You have to think a bit about what the distribution map is supposed to show and make
sensible choices. Default choices may not work since they are computed from the metamodel
without regards.
--> Maybe the wizard should be configurable with default (sensible) choices so that
you don't get the DNU.