Moose-dev November 2011

moose-dev@list.inf.unibe.ch

25 participants
191 discussions

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 18 Nov '11

18 Nov '11

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.

1 4

Issue 594 in moose-technology: Cleaning MOAnnouncer
by moose-technology＠googlecode.com 18 Nov '11

18 Nov '11

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

1 1

Why won't my action's shortcut be executed?
by VOGT Simon 17 Nov '11

17 Nov '11

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

1 1

same classes - side by side duplication
by Usman Bhatti 17 Nov '11

17 Nov '11

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

2 1

Help with VerveineJ
by Santiago Vidal 17 Nov '11

17 Nov '11

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

6 20

releasing 4.6
by Tudor Girba 17 Nov '11

17 Nov '11

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."

3 5

merging class and metaclass and hasClassScope
by Usman Bhatti 17 Nov '11

17 Nov '11

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

1 0

Mondrian: MOTreeMapLayout
by Veronica Isabel Uquillas Gomez 16 Nov '11

16 Nov '11

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

2 3

Description de EyeSee
by Alexandre Bergel 16 Nov '11

16 Nov '11

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Issue 696 in moose-technology: inFusion should export the declaredType
by moose-technology＠googlecode.com 16 Nov '11

16 Nov '11

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

1 1

← Newer
1
...
10
11
12
13
14
15
16
...
20
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 November 2011