Moose-dev November 2011

moose-dev@list.inf.unibe.ch

25 participants
191 discussions

Issue 740 in moose-technology: classNamedOrNil test is bogus

by moose-technology＠googlecode.com

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

13 years, 1 month

Issue 739 in moose-technology: 'Average Huerarchy Height' label is misspelled

by moose-technology＠googlecode.com

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

13 years, 1 month

Why can't I populate my dynamic presentation with an action?

by VOGT Simon

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

13 years, 1 month

Issue 706 in moose-technology: Replace <property: ... > pragmas with <MSEProperty: ...> ones

by moose-technology＠googlecode.com

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'>

13 years, 1 month

what is the MooseMonticelloImporter exactly?

by Stéphane Ducasse

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

13 years, 1 month

Proposal to enhance the MooseTask inheritance and MooseAbstractImporter

by Usman Bhatti

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

13 years, 1 month

we fixed some merlin packages last friday but there are not in Moose

by Usman Bhatti

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

13 years, 1 month

where is the C importer?

by Stéphane Ducasse

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

13 years, 1 month

Moving MooseQeuryResult out of FAMIX-Core

by Stéphane Ducasse

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

13 years, 1 month

what is a module in FAMIX?

by Stéphane Ducasse

Hi What is a module in FAMIX? http://www.themoosebook.org/book/internals/famix/core Stef

13 years, 1 month

← Newer
1
...
12
13
14
15
16
17
18
19
20
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2011