Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Cyrille Delaunay

Hello, I would like to manage the size of a chart when drawing it into a glamour presentation. For now the default size is quite big and i am not able to see it fully. Does such a mechanism already exist ? Or do you have any starting points where I should look at ? Is this possible for example with mondrian visualizations ?

13 years, 10 months

DistributionMap wizard improvements

by Cyrille Delaunay

Hello, I Improved the distributionMap wizard on several points: => no long computations anyMore. Should be usable with large models => adding some 'conditions' before leaving the first pane. Avoid to end with exceptions: - if properties are not well entered - if properties specified are not 'computable' for this model => refactored/cleaned code/ Divided into shorter methods/recategorized Looks at least cleaner than before It should fixe the problems recently experimented when trying all moose menus

13 years, 10 months

Question about export metrics from Moose

by César Couto

I am a PhD student at UFMG, Brazil, and I'm working with source code metrics. I have a FAMIX model generated by the inFusion tool and I would like to know if the Moose can export source code metrics (LOC, WMC, LCOM, etc) of Java classes to .CSV ou XML files? Is there any plugin of the Moose that have this functionality? Cesar Couto -- http://www.decom.cefetmg.br/cesar

13 years, 10 months

Menus of Moose - MooseModel menu

by jannik.laval

Hi, I am trying menus in Moose 4.6. I loaded Moose from MooseScript (method createModelForMoose). And I tried all command in menus. Here are my comments: On a MooseModel, some commands are strange or does not work: - browse: - code with dependencies: > why are there 2 times Smalltalk in the first pane ? > the visu seems strange and slow ! > is it used by someone ? - code with design flow > unusable as it is slow > is it used by someone ? - code with namespace > is it used by someone ? - code with package > is it used by someone ? - export: - export to fl > does not work, there is a DNU. It seems that the notification does not work - export to mse > same problem than export to fl - import file structure > no progress bar. > why is it loaded in the same mooseModel and change the model name ? - import from fl / mse > it imports, but I do not see what it does. There is no new model in the root. And no new entities in my model. > after the import mse, the MooseBrowser twinkled !!! (strange behavior) and the VM used 100% of my processor.... - utilities - bookmark entity: do nothing after asking for a name - ensure classes and namespaces: do nothing. What is it ? - infer namespace parents based on names: do nothing - set root folder does not work: I select a folder, and it does not keep my selection. Jannik

13 years, 10 months

Issue 668 in moose-technology: moose menu - on a MooseModel - import file structure

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 668 by jannik.l...(a)gmail.com: moose menu - on a MooseModel - import file structure http://code.google.com/p/moose-technology/issues/detail?id=668 importing a file structure should not change the model name.

13 years, 10 months

Issue 669 in moose-technology: moose menu - on a MooseModel - import from fl/mse

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 669 by jannik.l...(a)gmail.com: moose menu - on a MooseModel - import from fl/mse http://code.google.com/p/moose-technology/issues/detail?id=669 the import seems to work, but I do not see the changes. There is no new entities in my model. Maybe the browser is not well updated or the cache ?

13 years, 10 months

Issue 659 in moose-technology: MooseMenu - bookmark entity

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 659 by jannik.l...(a)gmail.com: MooseMenu - bookmark entity http://code.google.com/p/moose-technology/issues/detail?id=659 In the menu of a package group: - 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. Is it an old stuff to remove? I think there is a new bookmark mechanism (with metanool?). If only I knew where it was...

13 years, 10 months

Issue 660 in moose-technology: MooseMenu - Create load script

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 660 by jannik.l...(a)gmail.com: MooseMenu - Create load script http://code.google.com/p/moose-technology/issues/detail?id=660 - 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. === Ok, so: or we ask for a class name, and we create it, or we do not ask... or maybe we can provide a list with existing classes.

13 years, 10 months

Menus of Moose - PackageGroup menu

by jannik.laval

Hi, I am trying menus in Moose 4.6. I loaded Moose from MooseScript (method createModelForMoose). And I tried all command in menus. Here are my comments: 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. - createLoadScriptForGroup: I tried with a new class name, the class is not created. When I use MooseScripts, I have a DNU because of UIManager - visualize: - browse package blueprint: DNU - customizable eyesee chart: should have a progress bar when the computing is slow. - Dependencies (cycles): seems not working (loop ?) - distributionMap for these elements: I just did "next", "finish" without configuring anything, I have a DNU - distributionMap for these parts: I have a SubscriptOutOfBounds. - export GML graph: I want to specify the place of the file - package wise system complexity: Zero Divide - encaps DSM: the name are not well placed - enriched cycleTable: should have a progress bar - enriched dsm too. Jannik

13 years, 10 months

Issue 654 in moose-technology: [Glamour] Undocumented differences between types of actions

by moose-technology＠googlecode.com

Status: Accepted Owner: damien.c...(a)gmail.com CC: tudor.gi...(a)gmail.com, cy.delau...(a)gmail.com Labels: Type-Other Priority-Medium Component-Glamour Difficulty-Easy New issue 654 by damien.c...(a)gmail.com: [Glamour] Undocumented differences between types of actions http://code.google.com/p/moose-technology/issues/detail?id=654 There are multiple ways to add actions to a presentation: - using #selectionAct: - using #act:* - using #dynamicActionsOnSelection: These methods do not have comments that help in distinguishing them. The moose book doesn't present them either. If you explain them to me, I will write the documentation at the appropriate places.

13 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev