Moose-dev October 2011

moose-dev@list.inf.unibe.ch

29 participants
175 discussions

Re: Issue 240 in moose-technology: Smalltalk importer scalability
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Comment #2 on issue 240 by tudor.gi...(a)gmail.com: Smalltalk importer scalability http://code.google.com/p/moose-technology/issues/detail?id=240 Anyone interested in picking this up?

1 1

Re: Issue 191 in moose-technology: Do not execute unnecessary transmissions
by moose-technology＠googlecode.com 20 Mar '12

20 Mar '12

Updates: Labels: -Milestone-4.2 Comment #5 on issue 191 by tudor.gi...(a)gmail.com: Do not execute unnecessary transmissions http://code.google.com/p/moose-technology/issues/detail?id=191 (No comment was entered for this change.)

1 1

Issue 600 in moose-technology: Popup does not work properly
by moose-technology＠googlecode.com 03 Mar '12

03 Mar '12

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

1 6

Issue 730 in moose-technology: inFamix should create namespaces without path information
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 730 by tu...(a)tudorgirba.com: inFamix should create namespaces without path information http://code.google.com/p/moose-technology/issues/detail?id=730 Currently, inFamix is exporting namespaces with names containing path information like src/com::example. It should be only com::example.

1 2

Issue 712 in moose-technology: Create a method fillColor:
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: andreho...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 712 by andreho...(a)gmail.com: Create a method fillColor: http://code.google.com/p/moose-technology/issues/detail?id=712 Implement a method fillColor: aBlock to be able to change the fill of a bar based on its value.

1 2

Issue 703 in moose-technology: inFusion should export C++ Enums
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 703 by tudor.gi...(a)gmail.com: inFusion should export C++ Enums http://code.google.com/p/moose-technology/issues/detail?id=703 Currently, there are no Enums in C++ models.

1 3

Issue 680 in moose-technology: Exporting metrics to CSV and XML
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

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.

1 4

Issue 679 in moose-technology: Exporting metrics to mse
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

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.

1 3

Issue 673 in moose-technology: Pharo1.3 should be updated in Jenkins
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Enhancement Priority-High Platform-Pharo Difficulty-Easy New issue 673 by damien.c...(a)gmail.com: Pharo1.3 should be updated in Jenkins http://code.google.com/p/moose-technology/issues/detail?id=673 Dear Doru, could you please update to the latest Pharo1.3 to avoid an annoying bug with the refactoring browser? To reproduce, 1- Download and open a glamorous-toolkit-latest-dev image 2- Open a browser 3- Select a package, right click, refactoring scope, selection It should not open a debugger

1 3

Issue 672 in moose-technology: Customizable EyeSee should not show zero metrics
by moose-technology＠googlecode.com 11 Feb '12

11 Feb '12

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-EyeSee New issue 672 by andreho...(a)gmail.com: Customizable EyeSee should not show zero metrics http://code.google.com/p/moose-technology/issues/detail?id=672 Customizable EyeSee should not show the metric when it is zero to all the entities (in axis x).

1 4

← Newer
1
2
3
4
5
6
7
8
9
...
18
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev October 2011