Moose-dev September 2011

moose-dev@list.inf.unibe.ch

30 participants
165 discussions

by jannik.laval

Hi, When I load MSE files, I would like to know which kind of information is inside the file. I think we should think about a solution. Here is the problem: - I can generate a mse file with a generic FAMIX model. - I can generate a mse file with a model containing FAMIXEclipsePlugin entities - I can also generate a mse file with mensana informations When I use a new image, few weeks after, I do not remember the plugins I used. And it is not possible to load the file. The problem is when the time of loading is more than 10 minutes and crash after 9 minutes, I am frustrated :) I propose a solution and I would like to discuss about this problem. I think that we could have a meta information that lists all type of entities in the mse file (for example: (FAMIXClass, FAMIXMethod, FAMIXPackage...)). This information would be checked before the importation and inform the developer if some classes are not present in the system. After that, we can imagine that the developer has the choice between installing the classes or loading a partial model. What are your opinions ? --- Jannik Laval

13 years, 2 months

moose on moose

by Tudor Girba

Hi, Moose On Moose is a report about Moose based on Arki. At the moment we have only a few issues already in the report: http://ci.moosetechnology.org/job/moose-on-moose/ Just a note: this is not a set of generic detections, but a dedicated set of checks super specific to Moose. These kind of checks are at the essence of humane assessment and I would like to see them grow and used for our development. If you want to contribute, the smallest thing you can do is to raise an issue, and then we build it into a rule. To get an idea of the process to get it in the report, you can see my latest blog post: http://www.humane-assessment.com/blog/detecting-wrong-values-in-annotations Cheers, Doru -- www.tudorgirba.com "Quality cannot be an afterthought."

13 years, 2 months

<MSEClass: #Attribute super: 'FAMIX.StructuralEntity'> vs <MSEClass: #Association super: #FAMIXSourcedEntity>

by Stéphane Ducasse

Hi guys Is there a reason why we get #Attribute and not FAMIXAttribute and/or super: #FAMIXStructuredEntity instead of super: 'FAMIX.StructuredEntity' So I would prefer to have something regular either #'FAMIX.Attribute' super: #'FAMIX.StructuredEntity' or #Attribute super: #StructuredEntity In fact I would prefer #'FAMIXAttribute' super: #'FAMIXStructuredEntity' Stef

13 years, 2 months

defining a clear set of change for descriptions

by Stéphane Ducasse

Doru I would like to compile a set of actions/decisions for FAME. So can you compile one based on the discussions we got else this will stay the same. Once we agree I will implement the changes. Stef

13 years, 2 months

fame package annotation related question

by Stéphane Ducasse

I imagine that I cannot ask an FAME attribute the methods that defined it. Am I correct? So this means that if I want to know that an attribute got tagged with a package pragma: I have to query that at the smalltalk level. But this means that I also have to check that this is the correct attributes I got <MSEProperty: #annotationInstances type: #FAMIXAnnotationInstance opposite: #annotatedEntity> <multivalued> <derived> <package: #Java> Stef

13 years, 2 months

Browser is broken in the image from the site

by Mircea Filip Lungu

Hi guys, I downloaded the Moose image from moosetechnology.org. If I right-click on a class in the System Browser, I get a DNU for #isActive sent to AnObsoleteBrowserEnvironment. That image needs to be updated I guess. Cheers, M. -- Mircea Lungu Researcher Software Composition Group University of Bern http://lungu.org/mircea

13 years, 2 months

confused by MSE is it moose or mse?

by Stéphane Ducasse

And if this is MSE why Fame has property tag with MSE... instead of FM? Then I do not understand why this is MSEProperty and not MSEPackage: in that case. Why do we have package: and not MSEPackage: (or FMPackage: and FMProperty: Stef

13 years, 2 months

Issue 710 in moose-technology: Move FAMIXAnnotation* entities to Famix-Core

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix Milestone-4.6 New issue 710 by tudor.gi...(a)gmail.com: Move FAMIXAnnotation* entities to Famix-Core http://code.google.com/p/moose-technology/issues/detail?id=710 Annotations are now used for Smalltalk as well, so they belong to the Core of Famix.

13 years, 2 months

Issue 691 in moose-technology: Change the fill color of bars

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-EyeSee New issue 691 by andreho...(a)gmail.com: Change the fill color of bars http://code.google.com/p/moose-technology/issues/detail?id=691 Script helpers like #setColoredFill or #coloredFill: are not working. I should work like #fillColor: in Mondrian. obs: #setLinearFill is OK

13 years, 2 months

Issue 711 in moose-technology: Color methods not working

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 711 by andreho...(a)gmail.com: Color methods not working http://code.google.com/p/moose-technology/issues/detail?id=711 Supporters color methods #getTemperatureColors: #getColors: is not working.

13 years, 2 months

← Newer
1
...
8
9
10
11
12
13
14
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev September 2011