Moose-dev December 2009

moose-dev@list.inf.unibe.ch

29 participants
67 discussions

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

MorphTreeMorph>>mouseEnter: broken in Moose
by Oscar Nierstrasz 18 Dec '09

18 Dec '09

I get an infinite loop of exceptions in the Moose Finder when I load Moose into the latest Pharo. LazyMorphTreeMorph does not understand keyboardFocusOnMouseDown ... Sleuthing shows: MorphTreeMorph>>mouseEnter: event "Changed to take keyboardFocusOnMouseDown preference into account." super mouseEnter: event. self wantsKeyboardFocus ifFalse: [^self]. self keyboardFocusOnMouseDown ifFalse: [self takeKeyboardFocus] But keyboardFocusOnMouseDown is not implemented anywhere in the system. What gives? Alain, it seems this method comes from you. What gives? I am unsure what to do ... - on

3 2

Multi selection in the moose finder
by Simon Denier 18 Dec '09

18 Dec '09

The current selection schema in the moose finder is annoying: I can select one item, I can shift-select a range of items, but I can not select some items in the list. I guess it's related to something in the morphic tree widget, but what are the plans to solve that? -- Simon

2 1

New interaction abilities in mondrian
by Alexandre Bergel 17 Dec '09

17 Dec '09

Comment of Version Mondrian-Alexandre_Bergel.315 is: -=-=-=-=-=-=-=-=-=-=-=-= -added a reference of the viewRenderer to each announcement. This is useful when a window update is needed - added new interaction methods on MOAnnouncer (highlightWhenOver. highlightWhenOver:, stronghigHlightWhenOver) - Added new examples related to interaction on MOEaselHelp - Added new tests for the interaction - Make nodeForDomainValues more flexible -=-=-=-=-=-=-=-=-=-=-=-= Try the following: -=-=-=-=-=-=-=-=-=-=-=-= | view nodes | view := MOViewRenderer new. view interaction strongHighlightWhenOver: [:v | {v - 1 . v + 1. v + 4 . v - 4}]. view shape rectangle width: 40; height: 30; withText. nodes := view nodes: (1 to: 16). view gridLayout gapSize: 2. view open. -=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

mondrian to file
by Tudor Girba 17 Dec '09

17 Dec '09

Hi Alex, I would need to be able to export Mondrian visualizations to files. I somehow recall a discussion in which it was explain how to do it, but I could not find my way. Is it supported? Cheers, Doru -- www.tudorgirba.com "We cannot reach the flow of things unless we let go."

3 3

Mondrian-Alexandre_Bergel.313
by Alexandre Bergel 17 Dec '09

17 Dec '09

Several important improvements. From the user perspective: - added a two new buttons, each offering a menu and a help - export options added (png, bmp, gif, jpeg) From the developer point of view: - used Lint to clean the code Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2009