Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: FAMIXPackageGroup>>exportAsGML
by Simon Denier 20 Nov '10

20 Nov '10

On 20 nov. 2010, at 11:47, Tudor Girba wrote: > Hi, > > While browsing the FAMIXPackageGroup class, I stumbled over: > FAMIXPackageGroup>>exportAsGML > > Does anyone know what it is for? It obviously exports to the GML format, but I do not know what tool to use to look at it and I also do not know what exactly it visualizes. http://en.wikipedia.org/wiki/Graph_Modelling_Language In particular, it was used to export package/class dependency graphs, visualize in Yed, and compare with package blueprints. -- Simon

1 0

FAMIXPackageGroup>>exportAsGML
by Tudor Girba 20 Nov '10

20 Nov '10

Hi, While browsing the FAMIXPackageGroup class, I stumbled over: FAMIXPackageGroup>>exportAsGML Does anyone know what it is for? It obviously exports to the GML format, but I do not know what tool to use to look at it and I also do not know what exactly it visualizes. Cheers, Doru -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

1 0

problem loading XMLSupport
by Tudor Girba 20 Nov '10

20 Nov '10

Hi, It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console Could anyone take a look at that? Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

4 7

Re: Issue 289 in moose-technology: Cleaning #forNodes:whenEnteringUpdateShapes:whenLeavingUpdateShapes:withLayoutUpdate:
by moose-technology＠googlecode.com 19 Nov '10

19 Nov '10

Updates: Status: Fixed Comment #2 on issue 289 by alexandre.bergel: Cleaning #forNodes:whenEnteringUpdateShapes:whenLeavingUpdateShapes:withLayoutUpdate: http://code.google.com/p/moose-technology/issues/detail?id=289 (No comment was entered for this change.)

1 0

VerveineJ out of memory error
by Fabrizio Perin 19 Nov '10

19 Nov '10

Hi, i just try to use VerveineJ to import Java code in moose and i'm not able to make it work: first i tried by command line to use VerveineJ to create the mse of LANModel and it worked. Than i tried to use it with one of my case study and i got: java.lang.OutOfMemoryError: Java heap space. I tried to modify the script verveinej.sh adding the -Xmx2048m option ( JOPT="-Xmx2048m" ) and it still doesn't work. Than i tried to use the Moose Wizard and again for the LANModel no problem, but when i tried to import one of my case study i get an error: a message box appear saying that the output.mse file doesn't exist and it ask me to point to an existing file. Apparently verveinej just does not create the file because not able to parse the project and the importer try to go ahead but it does not have any output file from verveinej. Someone has a similar problem? Am i doing something wrong? Cheers, Fabrizio

2 5

Re: Issue 476 in moose-technology: VerveineJ should export some metrics
by moose-technology＠googlecode.com 18 Nov '10

18 Nov '10

Comment #5 on issue 476 by anquetil.nicolas: VerveineJ should export some metrics http://code.google.com/p/moose-technology/issues/detail?id=476 I am not sure I want to follow you on this one. Both metrics can easily be computed from the data already available. I would like to keep Verveine as lean as possible. The compatibility argument does not convince me either. I suppose you mean compatibility with infusion? I mean no harm to infusion and it does provide good inspiration, but it is not a standard, it is only one tool to export java code to MSE (just as VerveineJ is another one).

1 3

Re: problem loading XMLSupport
by Stéphane Ducasse 18 Nov '10

18 Nov '10

thanks this is a good idea to separate it and clean the package structure On Nov 18, 2010, at 1:39 PM, jaayer wrote: > > > > > ---- On Wed, 17 Nov 2010 23:33:47 -0800 Tudor Girba wrote ---- > >> Hi, >> >> It looks like loading the latest XMLSupport raises some problems: >> http://hudson.moosetechnology.org/job/moose-latest-dev/448/console >> >> Could anyone take a look at that? > > I have been trying to make XML-Support more modular. XMLWriter is now stored separately at squeaksource.com/XMLWriter, and the tests are being separated into separate packages as well. > > This: > Gofer new > squeaksource: 'XMLSupport'; > package: 'ConfigurationOfXMLSupport'; > load. > (Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault > > works fine for me. Please try building it again and report back any errors. > >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

1 0

Orion Framework
by Laval Jannik 18 Nov '10

18 Nov '10

Hi guys, Orion is a tool for reengineering, to simulate changes and compare their impact on multiple versions of software source code models. It allows to work on a moose model, change it in multiple versions. Famix tools are compatible with Orion. I already send an email several months ago :) So I repeat what is inside. I publish a small description of Orion on moose website (http://www.moosetechnology.org/tools/orion). A tutorial is also available (For now it is small and maybe it has some english issues. I will improve it) at http://www.moosetechnology.org/docs/Orion. You can try it: ===== Gofer new squeaksource: 'Orion'; package: 'ConfigurationOfOrion'; load. (Smalltalk at: #ConfigurationOfOrion) perform: #loadDefault. ===== I am also available to answer your questions. Cheers, --- Jannik Laval PhD Student - Rmod Team - INRIA Certified Project Management Associate (IPMA) http://www.jannik-laval.eu http://rmod.lille.inria.fr ---

2 2

PetitParser: Parse recursive blocks
by Alberto Bacchelli 17 Nov '10

17 Nov '10

Hi all, I am trying to parse recursive blocks, i.e., blocks that can contain other sub-blocks, by using PetitParser. This is how I would do it: blockParser := ${ asParser, ( blockParser / ( ($} asParser) not, #any asParser)) star, $} asParser It works, but I am not sure it is the most convenient way. Could I have your opinion? Thank you, Alberto

2 1

Re: Issue 483 in moose-technology: Have a wizard to import form VerveineJ
by moose-technology＠googlecode.com 17 Nov '10

17 Nov '10

Updates: Labels: Component-ExternalTools Milestone-4.2 Comment #2 on issue 483 by tudor.girba: Have a wizard to import form VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=483 That is great. What should we load?

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev