Moose-dev September 2011

moose-dev@list.inf.unibe.ch

30 participants
165 discussions

Issue 706 in moose-technology: Replace <property: ... > pragmas with <MSEProperty: ...> ones
by moose-technology＠googlecode.com 14 Nov '11

14 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix New issue 706 by tudor.gi...(a)gmail.com: Replace <property: ... > pragmas with <MSEProperty: ...> ones http://code.google.com/p/moose-technology/issues/detail?id=706 Look for senders of: propertySignature <property: #XXX longName: 'YYY' description: 'ZZZ'> And replace with: propertySignature <MSEProperty: #propertySignature type: #Number> <MSEComment: 'ZZZ'>

3 14

Verveine-PHP
by Cyrille Delaunay 13 Nov '11

13 Nov '11

Hello, With nicolas we started to have a look at the eclipse-php-parser (provide with PDT), to export a famix-mse file from a PHP project. We already started to build an eclipse plugin that does some work: => We create an AST for each php file of the project => Then we have a visitor on this ast, and we are therfore able to make a specific action for each kind of node visited => For now, we just export some FAMIXNamespace, FAMIXClass, FAMIXMethods. So what's left is to implement each visit-method to extract informations for each node visited. For that we will have to know a bit more PHP :) Maybe the metamodel will have to be extended to take into account some PHP-specific elements, I don't know. If you want to have a look, sources are available via svn at: https://scm.gforge.inria.fr/svn/lse/Projects/Verveine Vervaine provide the extractor (not yet finished) for Java ans this one for PHP. Both are using a common mechanism to generate famix entities and extract them to mse. I will be on holidays until august and will probably no longer work on it until august. So if you want to have a look (and have the courage to install eclipse to read java code:)), have some suggestions, want to implement something, feel free to participate :)

7 15

happy man...
by Alexandre Bergel 14 Oct '11

14 Oct '11

Hi ! Yesterday I spent about 30 minutes with a guy from microsoft to generate .mse from C#. We were able to extract the data and generate the mse. I was happy to have a blueprint complexity after such a short amount of time. Usman, we use http://ccimetadata.codeplex.com for extracting the data. I can share the code if you wish. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 21

Annotation pattern
by Andre Hora 11 Oct '11

11 Oct '11

Hello, What should be the conversion in the pragma #MSEClass:super: in #annotation methods? For now there is no conversion, example: - super with dot and MSEClass without prefix of the meta-model (Famix) FAMIXClass>>annotation <MSEClass: #Class super: 'FAMIX.Type'> - super without dot and MSEClass without prefix of the meta-model (Famix) FAMIXComment>>annotation <MSEClass: #Comment super: #FAMIXSourcedEntity> <package: #FAMIX> - MSEClass with prefix of the meta-model (Hismo) and super without dot HismoAbstractHistory>>annotation <MSEClass: #HismoAbstractHistory super: #FAMIXEntity> I can fix it if you tell me correct pattern. -- Andre Hora

2 2

Issue 715 in moose-technology: VerveineJ does not export source anchors to Enums
by moose-technology＠googlecode.com 09 Oct '11

09 Oct '11

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 715 by tu...(a)tudorgirba.com: VerveineJ does not export source anchors to Enums http://code.google.com/p/moose-technology/issues/detail?id=715 FAMIX.Enums should have SourceAnchors attached.

1 1

Petit Puzzle
by Norbert Hartl 06 Oct '11

06 Oct '11

Hi, I want to ask if there is a elegant solution for the following problem: In my grammar there are references (symbols/names that reference entities somewhere). One is Syntax>>typeReference ^ self failOnReservedWords: ( #uppercase asParser, (#word asParser plus separatedBy: $- asParser) optional ) flatten These typeReferences can be standalone tokens (parsed with a token parse class that parses whitespaces and comments) Syntax>>reference ^ typeReference asn1Token / valueReference asn1Token / ... with PPParser>>asn1Token ^ (ASN1TokenParser on: self) ==> [:node| node value] or embedded in another type Syntax>>valueSetFieldReference ^ $& asParser, typeReference If have two classes, one for the syntax and for the parsing into model objects. Every typeReference should be parsed in the parser class to Parser>>typeReference ^ super typeReference ==> [:node| ASN1ReferenceNode new name: node ] The problem is that it is hard to have the typeReference be tokenized or not and make sure they are all parsed to the ASNReferenceNode. The example above Syntax>>reference ^ typeReference asn1Token / valueReference asn1Token / ... does not work because typeReferences result is transformedd to the model class but the asn1Token applied afterwards gives back a string again. I tried having a second parser typeReferenceToken but that only works if I double the code of typeReference in syntax and parser class. And as I am running short of instance variables I would prefer a solution without having the need for creating new instance variables. Any ideas? I hope I could explain the problem enough to get you the context you need, Norbert

2 3

Mondrian: use of MOVerticalLineWithTimelineLayout
by Veronica Isabel Uquillas Gomez 03 Oct '11

03 Oct '11

Hi, How can I use the MOVerticalLineWithTimelineLayout? I can't find any example, could the author provide an example? Thanks, Veronica

2 5

Issue 717 in moose-technology: Hismo and isStub
by moose-technology＠googlecode.com 03 Oct '11

03 Oct '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hismo Milestone-4.6 New issue 717 by alexandr...(a)gmail.com: Hismo and isStub http://code.google.com/p/moose-technology/issues/detail?id=717 The following test fails. No idea why. ClassB is a stub -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testStubAndHismo | allModelClasses allHistoryModelClasses mooseSampleData sampleMooseModel hismoHistoryModel | mooseSampleData := MooseSampleData new. sampleMooseModel := (mooseSampleData readMSEString: self sampleMSE) name: #'example'. allModelClasses := sampleMooseModel allModelClasses. self assert: (sampleMooseModel allModelClasses size = 1). self assert: (sampleMooseModel allClasses size = 2). hismoHistoryModel := HismoModelHistory new. hismoHistoryModel addLastVersionForMooseModel: sampleMooseModel. allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last isStub not]. self assert: allModelClasses size = allHistoryModelClasses size sampleMSE ^ '( (FAMIX.Namespace (id: 1) (name ''aNamespace'')) (FAMIX.Class (id: 2) (name ''ClassA'') (container (ref: 1)) (parentPackage (ref: 201))) (FAMIX.Method (name ''methodA1'') (signature ''methodA1()'') (parentType (ref: 2)) (LOC 2)) (FAMIX.Attribute (name ''attributeA1'') (parentType (ref: 2))) (FAMIX.Class (id: 3) (name ''ClassB'') (container (ref: 1)) (isStub true) (parentPackage (ref: 201))) (FAMIX.Inheritance (subclass (ref: 3)) (superclass (ref: 2))) (FAMIX.Package (id: 201) (name ''aPackage'')) (FAMIX.Package (id: 202) (name ''aPackage'') (parentPackage (ref: 201))) )' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Indeed, it looks like MooseEntity>>isStub is the trouble maker. We need to create an issue. In the meantime you can use: allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last versionEntity isStub not].

1 1

Issue 664 in moose-technology: MooseMenu - export GML graph
by moose-technology＠googlecode.com 01 Oct '11

01 Oct '11

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 664 by jannik.l...(a)gmail.com: MooseMenu - export GML graph http://code.google.com/p/moose-technology/issues/detail?id=664 It should be cool to specify the place of the new file. For now, it is saved just near the image.

2 9

Question about export metrics from Moose - with attached
by Paloma Maira de Oliveira 30 Sep '11

30 Sep '11

Hello! I'm in trouble (attached) to run the script below: Gofer new squeaksource: 'FameImportExportEx'; package: 'Fame-ImportExport-Extensions'; load. I’m using Windows-OS and Moose Suite 4.5. I need help to export metrics to .CSV. Where should I run the script? I’m running the workspace Moose Suite 4.5, correct? Thank you. -- PROF. PALOMA MAIRA DE OLIVEIRA __________________________________________________________ IFMG - Campus Formiga Doutoranda em Ciência da Computação - DCC/UFMG Mestra em Modelagem Matemática e Computacional - CEFET/MG Bacharel em Ciência da Computação - UNIFOR/MG

4 4

← Newer
1
...
5
6
7
8
9
10
11
...
17
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 September 2011