Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Veronica Isabel Uquillas Gomez

Hi Alexandre, Is the defaultMinimal configuration up-to-date? I tried it and it is loading a version of ConfigurationOfHealthReportProducer that does not exist... So I am wondering if I can rely on this minimal configuration in Mondrian. Regards, Veronica

13 years, 9 months

exporting model to mse? do they keep the metrics

by Stéphane Ducasse

Hi guys I could not find metrics in the saved MSE metrics like LOC that cannot be computed by moose. Are metrics saved? I remember writing tests to make sure that this was correct. In addition it would be good to be able to select some metrics to be exported to other formats. Stef

13 years, 9 months

About passing an exporting context to an exporter

by Andre Hora

Hi guys We are implementing a way to export a model and filter some entities. Now we have a question: -- Andre Hora

13 years, 9 months

accessing

by Andre Hora

we wrote this test testHasExactlySamePropertiesThan "self debug: #testHasExactlySamePropertiesThan" | cp | "I should have the same entity than a copy of myself" self assert: (self nodeClass hasExactlySamePropertiesThan: self nodeClass). self assert: (self nodeClass hasExactlySamePropertiesThan: self nodeClass veryDeepCopy). the previous assertion does not work because the incoming references are indeed not pointing to the copy so this is correct that it does not work. cp := self model entityNamed: LANOutputServer mooseName. self deny: (self nodeClass hasExactlySamePropertiesThan: cp). cp := self nodeClass veryDeepCopy. cp instVarNamed: 'state' put: (cp instVarNamed: 'state') veryDeepCopy. cp propertyNamed: #numberOfLinesOfCode put: 12000. "This property is described as a fame property on the entity kind but not existing on the copy so two entities should have different properties" self deny: (self nodeClass hasExactlySamePropertiesThan: cp). cp := self nodeClass veryDeepCopy. cp instVarNamed: 'state' put: (cp instVarNamed: 'state') veryDeepCopy. cp propertyNamed: #NOS ifAbsentPut: 12000. "This property is described but it does not exist on the entity kind so two entities should have different properties" self deny: (self nodeClass hasExactlySamePropertiesThan: cp). Now is there a way to only access the values that are stored in the properties? Because right now we are using allDeclaredProperties and they include all the instance variable as well. -- Andre Hora

13 years, 9 months

deepCopying a mooseentity leads to an infinite loop

by Andre Hora

Hi guys We wrote testHasExactlySamePropertiesThan "p" | cp | "I should have the same entity than a copy of myself" self assert: (self nodeClass hasExactlySamePropertiesThan: self nodeClass deepCopy). cp := self nodeClass deepCopy. cp propertyNamed: #NOP ifAbsentPut: 12000. "This property is described as a fame property but not existing on the copy so two entities should have different properties" self deny: (self nodeClass hasExactlySamePropertiesThan: cp). and deepCopy loops on a FMValueLink -- Andre Hora

13 years, 9 months

About properties

by Andre Hora

Hi guys we are hacking with andre some tests for the exporter. Now we would like to compare two FAMIX entities and in particular their properties here are a bunch of questions we got - why there is no class comment on MSEDefaultState and friends? what is the difference between a property and an attributes - how can I get all the properties defined on an entity? there is allDefinedProperties Now how can I apply a given FMDescription of a property obtained from the the allDefinedProperties to a given entity I was thinking about aDescription valueFor: anEntity Stef and Andre -- Andre Hora

13 years, 9 months

How to access a model from a repository

by Andre Hora

Hi We are checking how we can make the FMRepositoryVisitor parametrized by an exporting context attached to a model. However the Repository only gets the model entities and not the model. This is a pity because we lack information held in the model (sourceLanguage, model versions, tags, who, what and the rest....) export: aModel withMetamodel: aMetamodel to: aStream | tower repository | tower := FMCompleteTower new. tower metaMetamodel: aMetamodel metamodel. tower metamodel: aMetamodel. tower model: (repository := (FMRepository with: aMetamodel) addAll: aModel entities). tower model exportOn: aStream What is the constraint that made that FMRepository does not get a model but just a list of entities? We could pass the context to a repository but it seems better to pass a model. What do you think? Stef and Andre -- Andre Hora

13 years, 9 months

hasExactlySamePropertiesThan: definition

by Andre Hora

hasExactlySamePropertiesThan: aMooseEntity self allDeclaredProperties size = aMooseEntity allDeclaredProperties size ifFalse: [^ false]. (self allDeclaredProperties collect: [:each | each name]) = (aMooseEntity allDeclaredProperties collect: [:each | each name]) ifFalse: [^ false]. self allDeclaredProperties do: [:each | (each getFrom: self) = (each getFrom: aMooseEntity) ifFalse: [^ false] ]. ^ true if you have comment on that definition please let us know. -- Andre Hora

13 years, 9 months

Re: Issue 273 in moose-technology: The Morphic Glamour should update the selectedText in a TextPresentation

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Comment #2 on issue 273 by tudor.gi...(a)gmail.com: The Morphic Glamour should update the selectedText in a TextPresentation http://code.google.com/p/moose-technology/issues/detail?id=273 (No comment was entered for this change.)

13 years, 9 months

About Moose show rooms

by Stéphane Ducasse

Hi guys I would like your input and (also help) for the following. I would like to have a web servers with some selected case studies for a show room on internet We should have it for December. Now I think that we should join forces. I think that we could take We take one or two projects: ArgoUML Papyrus Seaside We could have an apache rewrite rule to dispatch to the right image We create two specific images that contain models for argoUML multiple versions for papyrus a model with a limited amount of entities for Moose itself/seaside so that we get testcoverage.... Then we propose different analysis - metrics - polymetric views - eyeScope - cycle identification - distribution map (may of commits or something) - evolution hierarchy (cf the paper of girba on using Hismo) - reports Usman this should correspond to your ideas of scenario. So let me know what you think. It would be beneficial for the complete community so we need help. Stef

13 years, 9 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