Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Please remove "Software Cartographer" from Moose page
by Adrian Kuhn 28 Dec '09

28 Dec '09

Hi Doru, please remove "Software Cartographer" from Moose page. It never integrated with Moose at all. http://www.moosetechnology.org/tools/vw/softwarecartographer thanks, AA

5 18

Mondrian health report
by Alexandre Bergel 28 Dec '09

28 Dec '09

Since I slightly modified the cacheBounds initialization when translating nodes when adding the features wanted by Marco, I regenerate the mondrian health report. Slightly improvement from the one I sent at the beginning of the month. I discovered an opportunity to gain many % when rendering nodes. I will work on that soon. Report produced on 2009-12-28T13:32:14+00:00 Benchmark ManyNode (simple rendering of nodes) : 100 nodes => 16 ms 200 nodes => 54 ms 300 nodes => 108 ms 400 nodes => 187 ms 500 nodes => 301 ms 600 nodes => 446 ms 700 nodes => 574 ms 800 nodes => 755 ms 900 nodes => 949 ms 1000 nodes => 1148 ms 1600 nodes => 3043 ms Benchmark ManyEdges (simple rendering of edges) : 10 edges => 1 ms 20 edges => 5 ms 30 edges => 13 ms 40 edges => 180 ms 50 edges => 50 ms 60 edges => 79 ms 70 edges => 117 ms 80 edges => 174 ms 90 edges => 256 ms 100 edges => 342 ms 200 edges => 4432 ms 300 edges => 35438 ms 55.08 % of methods are covered Progress from last time: -0.96 % Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 5

www.moosetechnology.org
by Tudor Girba 28 Dec '09

28 Dec '09

Hi, Moose has a new den: http://www.moosetechnology.org/ Most of the content (including the users) was ported from moose.unibe.ch. Here are the main diffs: - The look suffered a minor surgery - I created a small ad-like movie to introduce the logo (embedded on the main page). It does not have sound, but it's a start - The tools were reorganized: those tools that were only available in VW are now under /tools/vw. For the popular tools like codecity, softwarenaut and chronia, we have a forward in /tools (e.g., www.moosetechnology.org/tools/codecity) . - I added http://www.moosetechnology.org/development for development related pages - The publications list is up to date based on scg.bib and uses the latest Citezen implementation by Oscar. At this moment, there is no automatic update, and if you want to get your publications online, please let me know. - http://www.moosetechnology.org/docs/famix/3.0 is generated dynamically from the MSE specification. This will probably grow in the near future to offer a more detailed documentation. - The old moose.unibe.ch redirects to the new page (except for the / resources which are still hosted on macamis.unibe.ch for serving large files) I would like to thank Lukas for all the support he provided to deal with the technical details of redirects and server settings. Cheers, Doru -- www.tudorgirba.com "Live like you mean it."

3 9

Dialect/Operating System matrix for moose tools
by Norbert Hartl 26 Dec '09

26 Dec '09

Hi, I've started to play around with moose a bit. The tools page on the moose site has quite impressive tools to offer. But as soon as I took a pharo image and loaded moose into it I recognized that it is (again) not as easy as I hoped. For a lot of the tools I don't meet the smalltalk dialect requirements and/or I don't meet the operating system requirements. So, is there a matrix where I can see which of the tools are usable in which dialect or operating system? Thanks, Norbert

5 13

Problem generating a mse with infusion
by Simon Denier 26 Dec '09

26 Dec '09

Hi all I'm trying to generate a mse file for a java project with infusion. It stops somewhere with this error: Writing the MSE file for the path: /Users/deniersi/workspace/GecO/src --Export started-- MSE file generation aborted! which does not give much help. Last lines in the mse describe beginning of a method (FAMIX.Method (id: 4318) (sourceAnchor (ref: 9706)) (parentType (ref: 3)) ref 9706 is '_unknown_path\_unknown_file' Any idea about how to debug? -- Simon

2 1

Missing invocations?
by Alberto Bacchelli 26 Dec '09

26 Dec '09

Hi, I still use VisualWorks 7.6nc and FAMIX2.1 to analyze Java systems in Moose. I still have to move to Pharo, sorry... I am trying to find the connections between Java classes of a software system. Besides inheritance (which is perfectly recognized), I would also like to consider other type of relations, such as invocations. Although many invocations are correctly recognized, there is -at least- one case which I cannot extract. For example, if you take ArgoUML 0.28 [0], that I parsed into a MSE file [1] using inFusion 7.2.7, and consider the class org.argouml.application.api.Argo [2], you can find this code: ==== ==== ==== [...] public final class Argo { [...] /** * Key for default startup directory. */ public static final ConfigurationKey KEY_STARTUP_DIR = Configuration.makeKey("default", "user", "dir"); [...] ==== ==== ==== I believe that, between all the invocations done by this Argo class, there should be the invocation to the method "makeKey(String,String,String)" that belongs to the class Configuration. However, if I call "outgoingInvocations" on the FAMIX Class representing the Java class Argo, I cannot get this invocation. It is possible that this problem is not caused by Moose, but by the generation of the MSE file: I manually looked for the Argo class inside the MSE file [1]. I found that it has id = 202. I looked at all the references (idref: 202) to this id. I could find 4 connections to all the methods of this class, many connections to all the attributes of this class, but no reference to this "makeKey" method invocation. Is this problem caused by the fact that the method invocation is in the main body of the class? What happens if such an invocation is to be found inside a class method, is it correctly recognized? Thank you in advance. Ciao, Alberto [0] http://www.inf.usi.ch/phd/bacchelli/research/argouml/2009-03-23-argoUML_0.2… [1] http://www.inf.usi.ch/phd/bacchelli/research/argouml/2009-03-23_argoUML_0.2… [2] http://www.inf.usi.ch/phd/bacchelli/research/argouml/Argo.Java

2 1

Why could we not make Moose load in a core image?
by Stéphane Ducasse 24 Dec '09

24 Dec '09

tried to load moose in pharoCore-rc401 This package depends on the following classes: RBProgramNodeVisitor OBPluggableTextMorphWithShout OBTextMorphWithShout RBVariableNode RBBlockLintRule RBProgramNode You must resolve these dependencies before you will be able to load these definitions: FAMIXMetaModelClassesShouldNotOverrideRule FAMIXMetaModelClassesShouldNotOverrideRule>>checkClass: FAMIXMetaModelClassesShouldNotOverrideRule>>group FAMIXMetaModelClassesShouldNotOverrideRule>>metaModelClasses FAMIXMetaModelClassesShouldNotOverrideRule>>name FAMIXMetaModelClassesShouldNotOverrideRule>>rationale FAMIXMetaModelClassesShouldNotOverrideRule>>selectorsThatShouldNotBeOverriden FAMIXMetaModelClassesShouldOverrideRule FAMIXMetaModelClassesShouldOverrideRule>>checkClass: FAMIXMetaModelClassesShouldOverrideRule>>group FAMIXMetaModelClassesShouldOverrideRule>>metaModelClasses FAMIXMetaModelClassesShouldOverrideRule>>name FAMIXMetaModelClassesShouldOverrideRule>>rationale FAMIXMetaModelClassesShouldOverrideRule>>resultClass FAMIXMetaModelClassesShouldOverrideRule>>selectorsThatShouldBeOverriden FameNameConventionBetweenFM3AndSmalltalkRule FameNameConventionBetweenFM3AndSmalltalkRule>>addClass:toMetaBuilderCollection: FameNameConventionBetweenFM3AndSmalltalkRule>>checkClass: FameNameConventionBetweenFM3AndSmalltalkRule>>group FameNameConventionBetweenFM3AndSmalltalkRule>>name FameNameConventionBetweenFM3AndSmalltalkRule>>rationale FameOppositeAttributeShouldPointBackRule FameOppositeAttributeShouldPointBackRule>>checkMethod: FameOppositeAttributeShouldPointBackRule>>group FameOppositeAttributeShouldPointBackRule>>name FameOppositeAttributeShouldPointBackRule>>rationale FameSuperclassMetaDescribedExistRule FameSuperclassMetaDescribedExistRule>>addClass:toMetaBuilderCollection: FameSuperclassMetaDescribedExistRule>>checkClass: FameSuperclassMetaDescribedExistRule>>group FameSuperclassMetaDescribedExistRule>>name FameSuperclassMetaDescribedExistRule>>rationale MOEaselTextEditor MOEaselTextEditor>>bindingOf: MOEaselTextEditor>>hasBindingOf: MOEaselTextEditor>>hasBindingThatBeginsWith: MOEaselTextEditor>>textMorphClass MOTextMorphWithShout RBProgramNode>>isSuper RBVariableNode>>isSuper SmalltalkMethodVisitor SmalltalkMethodVisitor classSide>>on: SmalltalkMethodVisitor>>acceptAssignmentNode: SmalltalkMethodVisitor>>acceptBlockNode: SmalltalkMethodVisitor>>acceptCascadeNode: SmalltalkMethodVisitor>>acceptMessageNode: SmalltalkMethodVisitor>>acceptMethodNode: SmalltalkMethodVisitor>>acceptReturnNode: SmalltalkMethodVisitor>>acceptSequenceNode: SmalltalkMethodVisitor>>acceptVariableNode: SmalltalkMethodVisitor>>classifyMethodNode: SmalltalkMethodVisitor>>createAccessTo:writing: SmalltalkMethodVisitor>>createReferenceTo: SmalltalkMethodVisitor>>extractCommentsFromNode: SmalltalkMethodVisitor>>importer SmalltalkMethodVisitor>>importer: SmalltalkMethodVisitor>>matchConstant: SmalltalkMethodVisitor>>matchConstructor: SmalltalkMethodVisitor>>matchGetter: SmalltalkMethodVisitor>>matchSetter: SmalltalkMethodVisitor>>methodEntity SmalltalkMethodVisitor>>parseTreeForSource: SmalltalkMethodVisitor>>resolve: SmalltalkMethodVisitor>>resolveInstanceSide: SmalltalkMethodVisitor>>runWith:and: SmalltalkMethodVisitor>>runWithSource:and: SmalltalkMethodVisitor>>visitArgument: SmalltalkMethodVisitor>>visitNode: VisualWorksParseTreeMetricCalculator VisualWorksParseTreeMetricCalculator>>acceptAssignmentNode: VisualWorksParseTreeMetricCalculator>>acceptBlockNode: VisualWorksParseTreeMetricCalculator>>acceptCascadeNode: VisualWorksParseTreeMetricCalculator>>acceptMessageNode: VisualWorksParseTreeMetricCalculator>>acceptMethodNode: VisualWorksParseTreeMetricCalculator>>acceptSequenceNode: VisualWorksParseTreeMetricCalculator>>classNameFromMethod VisualWorksParseTreeMetricCalculator>>computeCyclomaticNumber: VisualWorksParseTreeMetricCalculator>>countConditionals: VisualWorksParseTreeMetricCalculator>>cyclomaticNumber VisualWorksParseTreeMetricCalculator>>cyclomaticNumber2 VisualWorksParseTreeMetricCalculator>>cyclomaticNumber: VisualWorksParseTreeMetricCalculator>>initialize VisualWorksParseTreeMetricCalculator>>methodBodyOn: VisualWorksParseTreeMetricCalculator>>methodComplexity VisualWorksParseTreeMetricCalculator>>methodComplexity: VisualWorksParseTreeMetricCalculator>>numberOfConditionals VisualWorksParseTreeMetricCalculator>>numberOfConditionals: VisualWorksParseTreeMetricCalculator>>numberOfLinesOfCode VisualWorksParseTreeMetricCalculator>>numberOfLinesOfCode: VisualWorksParseTreeMetricCalculator>>numberOfMessageSends VisualWorksParseTreeMetricCalculator>>numberOfMessageSends: VisualWorksParseTreeMetricCalculator>>numberOfStatements VisualWorksParseTreeMetricCalculator>>numberOfStatements: VisualWorksParseTreeMetricCalculator>>parameterComplexityMultiplier VisualWorksParseTreeMetricCalculator>>parameterComplexityMultiplier: VisualWorksParseTreeMetricCalculator>>processMethod:usingImporter:inModel: VisualWorksParseTreeMetricCalculator>>resetMetricValues VisualWorksParseTreeMetricCalculator>>visitArgument: VisualWorksParseTreeVisitor VisualWorksParseTreeVisitor>>checkThatClassIsStillCorrect VisualWorksParseTreeVisitor>>classNameFromMethod VisualWorksParseTreeVisitor>>compiledMethod VisualWorksParseTreeVisitor>>famixNameFor: VisualWorksParseTreeVisitor>>importer VisualWorksParseTreeVisitor>>importer: VisualWorksParseTreeVisitor>>inModel VisualWorksParseTreeVisitor>>inModel: VisualWorksParseTreeVisitor>>isDirtySuperInMethod:withReceiver: VisualWorksParseTreeVisitor>>isSuperInMethod:withReceiver: VisualWorksParseTreeVisitor>>methodBodyOn: VisualWorksParseTreeVisitor>>methodEntity VisualWorksParseTreeVisitor>>methodEntity: VisualWorksParseTreeVisitor>>processMethod:usingImporter:inModel: VisualWorksParseTreeVisitor>>stClass VisualWorksParseTreeVisitor>>stClass: VisualWorksParseTreeVisitor>>stParseTree Select Proceed to continue, or close this window to cancel the operation.

2 1

Re: [Moose] moose-dev on Nabble?
by Tudor Girba 23 Dec '09

23 Dec '09

Hi Geert, Thanks for the suggestion. I created a Nabble mailing list: http://n3.nabble.com/moose-dev-f97923.html Cheers, Doru On 19 Dec 2009, at 18:22, Geert Claes wrote: > Could you add moose-dev on Nabble for those who prefer to follow > moose online rather than via email? > _______________________________________________ > Moose mailing list > Moose(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose -- www.tudorgirba.com "Every thing has its own flow."

2 3

FAMIXNamespace question & comment
by Johan Fabry 22 Dec '09

22 Dec '09

Hi all, 2 short ones: If I have a FAMIXNamespace, how do I obtain a reference to the model that contains this namespace? FAMIXNamespace has child scopes instead of namespaces, which makes it ugly to define a Glamour tree view on models and their namespaces. I have therefore added the code below, I think it would be a good idea to add that to the core as well. FAMIXNamespace>>allNamespaces ^ self childScopes -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

3 5

new moose problems
by Adrian Dozsa 21 Dec '09

21 Dec '09

Hi all, I've tried today the latest Moose version (the Squeak based one) - http://moose.unibe.ch/resources/download/moose-suite-4_0-beta-2.app.zip I've extracted a famix 3 mse with the latest inFusion (build Dec 21) and tried to import it into Moose. But I get a lot of errors: 'Element ''FAMIX.PrimitiveType'' not found.' and a lot of 'Error(Object)>>doesNotUnderstand: #createInstance' Can somebody help me out here, please. Thanks, Adrian Dozsa

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev