Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Issue 736 in moose-technology: OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:
by moose-technology＠googlecode.com 16 Nov '11

16 Nov '11

Status: New Owner: tudor.gi...(a)gmail.com CC: usman.bh...(a)gmail.com Labels: Type-Defect Priority-High Platform-Pharo New issue 736 by usman.bh...(a)gmail.com: OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd: http://code.google.com/p/moose-technology/issues/detail?id=736 Describe the problem: what do you get? Message-not-understood: OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd: what do you expect? a moose model How to reproduce the problem: step by step if necessary - download moose 4.6-dev - import citezen (www.squeaksource.com/citezen) - import citezen packages in moose Additional information: platform, context which may impact the problem - Mac OS x 10.6.6 Please fill in the labels with the following information: * Type-Defect

1 2

Issue 740 in moose-technology: classNamedOrNil test is bogus
by moose-technology＠googlecode.com 16 Nov '11

16 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 740 by usman.bh...(a)gmail.com: classNamedOrNil test is bogus http://code.google.com/p/moose-technology/issues/detail?id=740 There correct test should be When we give a metaclass name we should get the metaclass of the class and not nil testClassNamedOrNil "(self selector: #testClassNamedOrNil) debug" self assert: (MooseUtilities classNamedOrNil: Model name) = Model. self assert: (MooseUtilities classNamedOrNil: FAMIXNameResolver name) = FAMIXNameResolver. self assert: (MooseUtilities classNamedOrNil: (FAMIXNameResolver name , FAMIXNameResolver metaclassTag) asSymbol) = FAMIXNameResolver class

1 3

Issue 739 in moose-technology: 'Average Huerarchy Height' label is misspelled
by moose-technology＠googlecode.com 16 Nov '11

16 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 739 by vonbecm...(a)gmail.com: 'Average Huerarchy Height' label is misspelled http://code.google.com/p/moose-technology/issues/detail?id=739 Pharo1.3 Latest update: #13315 Moose:4.6_dev Steps to reproduce: #. open OverviewPyramid>>renderOn: * Type-Defect

1 1

Why can't I populate my dynamic presentation with an action?
by VOGT Simon 15 Nov '11

15 Nov '11

Hi We have a Glamour related question! http://stackoverflow.com/questions/8137471/in-moose-why-cant-i-populate-my-… Simon

1 0

Issue 706 in moose-technology: Replace <property: ... > pragmas with <MSEProperty: ...> ones
by moose-technology＠googlecode.com 14 Nov '11

14 Nov '11

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Famix New issue 706 by tudor.gi...(a)gmail.com: Replace <property: ... > pragmas with <MSEProperty: ...> ones http://code.google.com/p/moose-technology/issues/detail?id=706 Look for senders of: propertySignature <property: #XXX longName: 'YYY' description: 'ZZZ'> And replace with: propertySignature <MSEProperty: #propertySignature type: #Number> <MSEComment: 'ZZZ'>

3 14

what is the MooseMonticelloImporter exactly?
by Stéphane Ducasse 14 Nov '11

14 Nov '11

I discovered MooseMonticelloImporter…. :) and some methods cannot compile :) I would merge MooseMonticelloPopulator and MooseMonticelloVisitor (because this is about only 3 stupid accessors). scope is undeclared. :( sad it means that there are not tests :( importFileNamed: name | version definitions visitor progressBar step | self setMooseModel. [ version := self repository versionFromFileNamed: name. ] on: Error do: [:ex | self inform: 'Package ', name, ' not accessible from the file system?'. ^ self targetModel]. definitions := version snapshot definitions. MooseCustomTask runWithProgress: [:bar | visitor := MooseMonticelloClassPopulator new importer: self. definitions do: [ :def | def accept: visitor. bar increment]. ] description: 'Importing classes' length: (definitions size). self setSuperclassesAndCreateStubs. "create a scope, this is necessary for the method visitor which is VW aware" scope := Dictionary new. self targetModel allClasses do: [:famixClass | famixClass attributes do: [:famixAttribute | (self scopeOfClass: famixClass) at: famixAttribute name bind: famixAttribute]]. MooseCustomTask runWithProgress: [:bar | "import methods" definitions do: [ :def | (def isKindOf: MCMethodDefinition) ifTrue: [ visitor := MooseMonticelloMethodPopulator new importer: self. def accept: visitor. self targetModel addAll: visitor entities]]. bar increment. ] description: 'Importing methods' length: (definitions size). ^ self targetModel

2 5

Proposal to enhance the MooseTask inheritance and MooseAbstractImporter
by Usman Bhatti 14 Nov '11

14 Nov '11

Here is a proposal MooseTask MooseAbstractImporter (which right now is not used and only contain error handling and importingContext) this class could hold the plugin mechanism that would be run as a tearDown from now. MooseImportingTask - Renamed SmalltalkImportingTask (add importerClass logic) MooseCompositeImporterTask MooseSqueakClassPackageImporterTask -> MoosePharoClassPackageExtractTask MooseSqueakClasssCategoriesImporterTask - >MoosePharoClassCategoriesExtractTask MooseImportClassesTask -> MooseExtractClassesTask FileStructureImporter(/Extractor) MooseOperator Since we will not be able to inherit from the same superclass MSEReader and MooseAbstractImporter. We could define one trait to represent the plugin management and apply to the MSEReader and MooseAbstractImporter. So let us know what you think. Stef and Usman

3 12

we fixed some merlin packages last friday but there are not in Moose
by Usman Bhatti 14 Nov '11

14 Nov '11

to have a default select: [:each | 'pac*' match and to avoid to have ' in drop box and this is not in the latest version of moose. How do we know merge process work in moose? Stef

3 10

where is the C importer?
by Stéphane Ducasse 14 Nov '11

14 Nov '11

Hi alex where is the C importer? Because I do not understand if FAMIX-C is just what is needed. Stef

3 4

Moving MooseQeuryResult out of FAMIX-Core
by Stéphane Ducasse 14 Nov '11

14 Nov '11

it would be better to move MooseQueryResult out of FAMIX-Core we could move them to FAMIX-Implementation or something like that. Stef

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev