Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

why do we need a sourcedEntity in a sourcelanguage?

by Stéphane Ducasse

Hi I'm reading SourceLanguage and I was wondering why why do we need sourcedEntities from the sourceLanguage. I do not get its use. Stef

13 years, 7 months

moose data analysis exporter (xml or other...)

by mpescuma

Hi all, I'm a developer that needs to produce (starting from a java project) and import moose data analysis into a own program (written into java or c++). Exists a api moose library (a .dll or somethings of equivalent) that can be linked to my program or can the moose data analysis exported into a xml or equivalent file format ? Can the moose be launched as a command with an stdout without use a user interface or gui ? Thanks, Michele -- View this message in context: http://moose-dev.97923.n3.nabble.com/moose-data-analysis-exporter-xml-or-ot… Sent from the moose-dev mailing list archive at Nabble.com.

13 years, 7 months

Issue 713 in moose-technology: Smart analyzer for the MSE reader

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 713 by alexandr...(a)gmail.com: Smart analyzer for the MSE reader http://code.google.com/p/moose-technology/issues/detail?id=713 it would be nice to have some information in MSE, but until now at least, we did not find an easy solution. One thing we can do easily though is to build a smart analyzer that does not build the meta-model, only traverses the header of entities to recover the types. Anyone would like to take a shot at this? We should create an issue.

13 years, 7 months

FM3PropertyDescription>>packageOf

by Stéphane Ducasse

I suggest that we add to FM3 something like that packagePragma ^ Pragma inMethod: (self mmClass implementingClass >>self implementingSelector) named: #package: package ^ look for FM3Package... if we agree I will write some tests soon. Stef

13 years, 7 months

is there a way to access the defining class of a property?

by Stéphane Ducasse

13 years, 7 months

Meta-information in MSE files

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, 7 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, 7 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, 7 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, 7 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, 7 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