Moose-dev November 2011

moose-dev@list.inf.unibe.ch

25 participants
191 discussions

Issue 743 in moose-technology: This is strange that we have to systematically specify the class of the importer

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 743 by usman.bh...(a)gmail.com: This is strange that we have to systematically specify the class of the importer http://code.google.com/p/moose-technology/issues/detail?id=743 a typical sript to import a model is MooseSqueakClassPackageImporterTask new importerClass: SmalltalkImporter; model: model; addFromPackageNamed: #'Moose-TestResources-LAN'; run; yourself But it is rare that we should change the importerClass (it was useful when we had to import FAMIX2 and FAMIX3 side by side). I suggest that we introduce a default and that we initialize the importerClass to SmalltalkImporter.

12 years, 2 months

Issue 738 in moose-technology: bugs in EyeSee

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Platform-Pharo Component-EyeSee New issue 738 by alexandr...(a)gmail.com: bugs in EyeSee http://code.google.com/p/moose-technology/issues/detail?id=738 I played with the matrix in EyeSee in a Pharo image. I found some problems: - #new:withAll: and #new: seems to raise an emergency debugger, whatever the value we provide - Many references are made that do not belong to EyeSee. For example #zero that refers to MalMatrixCoercion I also found other problems (e.g., hash). I added some tests for those. I produced version 0.9.2 Cheers, Alexandre

12 years, 2 months

Issue 730 in moose-technology: inFamix should create namespaces without path information

by moose-technology＠googlecode.com

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.

12 years, 2 months

Issue 712 in moose-technology: Create a method fillColor:

by moose-technology＠googlecode.com

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.

12 years, 2 months

Issue 703 in moose-technology: inFusion should export C++ Enums

by moose-technology＠googlecode.com

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.

12 years, 2 months

Issue 680 in moose-technology: Exporting metrics to CSV and XML

by moose-technology＠googlecode.com

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.

12 years, 2 months

Issue 679 in moose-technology: Exporting metrics to mse

by moose-technology＠googlecode.com

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.

12 years, 2 months

Issue 673 in moose-technology: Pharo1.3 should be updated in Jenkins

by moose-technology＠googlecode.com

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

12 years, 2 months

Issue 672 in moose-technology: Customizable EyeSee should not show zero metrics

by moose-technology＠googlecode.com

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).

12 years, 2 months

Issue 579 in moose-technology: [Kumpel] Incremental loading/Updating of Kumpel Projects

by moose-technology＠googlecode.com

Status: New Owner: junker.m...(a)gmail.com Labels: Type-Enhancement Priority-High Component-Kumpel New issue 579 by junker.m...(a)gmail.com: [Kumpel] Incremental loading/Updating of Kumpel Projects http://code.google.com/p/moose-technology/issues/detail?id=579 The KMPProjectHistory should offer the possibility to update the model to the current head revision.

12 years, 2 months

← Newer
1
...
4
5
6
7
8
9
10
...
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2011