- Moose-dev - INF Mailman

Issue 752 in moose-technology: New Mondrian Easel

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Critical New issue 752 by alexandr...(a)gmail.com: New Mondrian Easel http://code.google.com/p/moose-technology/issues/detail?id=752 - When the UI thread crashes, a new easel has to be opened. For example, execute the script: -=-=-=-=-=-=-=-=-= self foo view nodes: (1 to: 20) -=-=-=-=-=-=-=-=-= It will raise a debugger. Remove the "self foo", and press the check or Cmd-s, then I have the same error, even though "self foo" is not in the script. The easel is barely usable without this :-(

13 years, 7 months

1
0
0 0

Re: Jenkins build is still unstable: moose-latest-dev #708

by Alexandre Bergel

Hi! 6 tests are regularly failing. Anyone knows why? How bizarre Alexandre Le 22 nov. 2011 à 18:27, admin(a)moosetechnology.org a écrit : > See <http://hudson.moosetechnology.org/job/moose-latest-dev/708/> > >

13 years, 7 months

2
1
0 0

I'm reluctant to change too much before a release

by Stéphane Ducasse

I would like to work on the importer and fame stuff too. Now what is the process to avoid breaking release just before the release? Stef

13 years, 7 months

3
2
0 0

[Better comment initiative] AnnotationType

by Usman Bhatti

FamixAnnotationType and FamixAnnotationInstance are defined in Famix.Core, so in theory they should be independent of any language. Here is the comment from AnnotationIstance AnnotationInstance is an instance of an AnnotationType. It links an AnnotationType to an actual entity. For example, the following is an AnnotationInstance in Java: @Test(Timeout = 500) This model fits java but not smalltalk pragmas. So is it ok to keep in Famix core? thanx Nicolas and Usman

13 years, 7 months

3
2
0 0

mondrian tests are red

by Tudor Girba

Hi, There are 55 errors and 1 failure in Mondrian. It looks like the root of the issue is that the isShape method disappeared. Cheers, Doru -- www.tudorgirba.com Things happen when they happen, not when you talk about them happening.

13 years, 7 months

3
6
0 0

Famix entity have annotations instances

by Usman Bhatti

Usman and Nicolas, we are working on improving comments of Famix entities. We thought that this thing is worth discussing. Should all famix entities have annotations? For example, source-language, source-anchor and associations cannot be annotated.

13 years, 7 months

2
1
0 0

Loading FAMIX2.1 models

by Stéphane Ducasse

HI guys I would like to do a small experiments: how can I load Famix2.1 models into moose on pharo? After I would like to see how we can connect Moose/VW and Moose/Pharo in case we get people with VW applications. Stef

13 years, 7 months

2
2
0 0

smalltalkClass-related code

by Tudor Girba

Hi Usman, Thanks for committing the code related to smalltalkClass. Now, the tests should never be put in the same package as the implementation. So, I moved the test to Moose-Tests-SmalltalkImporter-LAN and I added a LAN prefix to the class name. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

13 years, 7 months

2
1
0 0

Who is cipt ?

by Alexandre Bergel

Hi! I have seen these initials in place of author name for some methods in moose. It would be great to have a proper name and not initials. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 7 months

3
3
0 0

Issue 558 in moose-technology: Better visitor for Mondrian

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian New issue 558 by alexandr...(a)gmail.com: Better visitor for Mondrian http://code.google.com/p/moose-technology/issues/detail?id=558 Shapes are not correctly handed by MOVisitor. We should move all the display:on: methods of the shapes in a visitor. The goal is to make the core of Mondrian free of any canvas reference. By doing so, we will produce exporter for HTML5 and Javascript...

13 years, 7 months

1
1
0 0

Unhandled exception: Import error: unknwon EMOF class 'FAMIX.Module'.

by Andrew Clark

Hi all, I'm not sure if this is the right place for this, but I couldn't find a moose-user list. I'm trying to set up Code City to see a physical representation of our classes. When I use InFusion to export the MSE (3.0) file, it writes this excerpt: (FAMIX.Module (id: 2) (parentPackage (ref: 5)) (*name '_unknown_file'*) ) Does anyone know what the bold text should read? Thanks, Andrew

13 years, 7 months

2
1
0 0

Issue 745 in moose-technology: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 745 by usman.bh...(a)gmail.com: There is no need by default to specify the importerClass when invoking the MooseCompositeImportTask subclasses http://code.google.com/p/moose-technology/issues/detail?id=745 setUp |importer | importer := MooseSqueakClassPackageImporterTask new. importer importingContext mergeClassAndMetaclass. can be safely rewritten as setUp |importer | importer := MooseSqueakClassPackageImporterTask new. importer importingContext mergeClassAndMetaclass.

13 years, 7 months

1
4
0 0

Issue 594 in moose-technology: Cleaning MOAnnouncer

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 594 by alexandr...(a)gmail.com: Cleaning MOAnnouncer http://code.google.com/p/moose-technology/issues/detail?id=594 It contains many unused methods: registerForEvent: eventClass forNodes: aBlockOrSymbol updateNode: updateBlock updateLayout: aBoolean registerForEvent: eventClass forNode: aBlockOrSymbol updateShape: updateBlock updateLayout: aBoolean toggleAllProcesses

13 years, 7 months

1
1
0 0

Why won't my action's shortcut be executed?

by VOGT Simon

Hi We have another Glamour related question! http://stackoverflow.com/questions/8164627/why-wont-my-actions-shortcut-be-… Simon

13 years, 7 months

1
1
0 0

same classes - side by side duplication

by Usman Bhatti

Is it normal to compare same classes for side by side duplication? Because, I see it in messana browser's detailed report.

13 years, 7 months

2
1
0 0

Help with VerveineJ

by Santiago Vidal

Hi, I had create several MSE files of different versions of a Java system using VerveineJ. Then, I had tried to load them to the Moose Panel but after load two of them I run out of memory in Moose (The Pharo error is "Space is Low"). I had the same problem when loading several versions of Mondrian to Moose Panel. However, we solved it by using the following script (we select only those thing in which we are interested): | mooseModel packages task | #('2.10' '2.13' '2.100') do: [:version | | project | project := (ConfigurationOfMondrian project version: version). [ project load. "This is necessary by Moose to properly import" Gofer new url: ' http://www.squeaksource.com/CollectionExtensions'; version: 'CollectionExtensions-TudorGirba.29'; load. packages := (project packages collect: #name) select: [:p | p beginsWith: 'Mondrian']. mooseModel := MooseModel new. task := MooseSqueakClassCategoryImporterTask new. task importerClass: SmalltalkImporter. task importingContext mergeClassAndMetaclass. task model: mooseModel. task runCandidateOperator. task addFromPackagesNamed: packages. task runWithProgress. mooseModel name: 'Mondrian ', version. mooseModel allMethods do: #numberOfLinesOfCode. mooseModel install. ] on: Error do: [ :ex | self halt. Transcript show: 'cannot load version ', version, ' ', ex printString. ]. ] Is there any way to do the same with VerveineJ (that is, reduce the size of the MSE files)? Or is there a way to expand the memory of Moose? Thanks -- Santiago Vidal

13 years, 7 months

6
20
0 0

releasing 4.6

by Tudor Girba

Hi, I would like to release 4.6 soon. It's been too long, and it contains important fixes. After this, we should allocate the effort to improve the packaging and the configurations. Perhaps one idea is to synchronize this re-packaging effort with the move to SmalltalkHub. What do you say? Cheers, Doru -- www.tudorgirba.com "Value is always contextual."

13 years, 7 months

3
5
0 0

merging class and metaclass and hasClassScope

by Usman Bhatti

Hello, We found a bug in our code to get a smalltalkClass from a famix one and the solution is that one As you can see, we use the fact that when the classes are not merged their names contains _class. The problem is that we cannot use hasClassScope to distinguish whether the method is a class method on a merged class or a class method on non merged class. The following code distinguish between the two in a dirty way. In the following test self assert: ( model entityNamed: #'Smalltalk::LANNode.new()') compiledMethod = (LANNode class>>#new). shows that a class method on a merged class/metaclass should still returns a compiled method of the metaclass. Now is there a better way to do that than to rely on _class? FAMIXMethod>>smalltalkClass "Return the smalltalk class associated with the receiver. Note that it may be different than doing self parentType because the class and metaclass can be merged." ^ ('*_class' match: self parentType name) ifTrue: [self parentType smalltalkClass] ifFalse: [self hasClassScope ifTrue: [self parentType smalltalkClass class] ifFalse: [self parentType smalltalkClass]] testWhenMergingClassAndMetaclassAccessWorks "self debug: #testWhenMergingClassAndMetaclassAccessWorks" "this test tests that we can access smalltalk class and compiledMethod from famix when the class and metaclasses are merged" |model importer fmNewMethodName| model := MooseModel new. importer := MooseSqueakClassPackageImporterTask new. importer importerClass: SmalltalkImporter. importer importingContext mergeClassAndMetaclass. importer model: model. importer addFromPackageNamed: #'Moose-TestResources-LAN'. importer run. self assert: (( model entityNamed: LANNode mooseName) smalltalkClass = LANNode). self assert: ( model entityNamed: (LANNode>>#accept:) mooseName) compiledMethod = (LANNode>>#accept:). self assert: ( model entityNamed: LANNode mooseName) isInstanceSide. self deny: ( model entityNamed: (LANNode>>#accept:) mooseName) hasClassScope. self assert: ( model entityNamed: #'Smalltalk::LANNode.new()') hasClassScope. self assert: ( model entityNamed: (LANNode>>#accept:) mooseName) smalltalkClass = LANNode. self assert: ( model entityNamed: #'Smalltalk::LANNode.new()') smalltalkClass = LANNode class. self assert: ( model entityNamed: #'Smalltalk::LANNode.new()') compiledMethod = (LANNode class>>#new). stef and ussman

13 years, 7 months

1
0
0 0

Mondrian: MOTreeMapLayout

by Veronica Isabel Uquillas Gomez

Hi, How can I try MOTreeMapLayout? I only found a test but not an official example. In one of my trees I just changed the layout to use this one. But when drawing there is an error because a point has a fraction as one of its coordinates (integer@fraction). Best Regards, Veronica

13 years, 7 months

2
3
0 0

Description de EyeSee

by Alexandre Bergel

Hi! Is there a description or a set of slides for EyeSee? I would like to show it to my students. http://www.themoosebook.org/book/internals/eyesee is pretty empty now If none, then I will make some Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 7 months

2
1
0 0

Issue 696 in moose-technology: inFusion should export the declaredType

by moose-technology＠googlecode.com

Status: New Owner: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 696 by tudor.gi...(a)gmail.com: inFusion should export the declaredType http://code.google.com/p/moose-technology/issues/detail?id=696 Method, Function, and StructuralEntities should have a declaredType

13 years, 7 months

1
1
0 0

Re: Issue 533 in moose-technology: inFamix should export the receiver of invocation

by moose-technology＠googlecode.com

Updates: Summary: inFamix should export the receiver of invocation Status: Fixed Labels: Milestone-4.6 Comment #3 on issue 533 by tudor.gi...(a)gmail.com: inFamix should export the receiver of invocation http://code.google.com/p/moose-technology/issues/detail?id=533 (No comment was entered for this change.)

13 years, 7 months

1
0
0 0

Issue 731 in moose-technology: inFamix should export annotation types with proper namespaces

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: georgega...(a)gmail.com Labels: Type-Defect Priority-Medium Component-ExternalTools New issue 731 by tu...(a)tudorgirba.com: inFamix should export annotation types with proper namespaces http://code.google.com/p/moose-technology/issues/detail?id=731 Currently, the annotation types that are present in jar files are exported as belonging to _unknown_pacakge_ instead of their proper namespace

13 years, 7 months

1
1
0 0

Re: Issue 416 in moose-technology: method invocation in Java don't fit metamodel

by moose-technology＠googlecode.com

Updates: Cc: anquetil...(a)gmail.com Comment #4 on issue 416 by tu...(a)tudorgirba.com: method invocation in Java don't fit metamodel http://code.google.com/p/moose-technology/issues/detail?id=416 Should we build AttributeInitializer as a subclass of BehavioralEntity?

13 years, 7 months

1
2
0 0

Re: Issue 417 in moose-technology: Writing informations in a Transcript

by moose-technology＠googlecode.com

Updates: Labels: -Component-Mondrian Comment #7 on issue 417 by alexandr...(a)gmail.com: Writing informations in a Transcript http://code.google.com/p/moose-technology/issues/detail?id=417 Mondrian contains just one "Transcript show:", when doing the benchmark. I consider it acceptable

13 years, 7 months

1
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev