- Moose-dev - INF Mailman

Re: Issue 321 in moose-technology: Problems using java code importer with inFusion in windows

by moose-technology＠googlecode.com

Updates: Labels: -Platform-Squeak Platform-Pharo Comment #1 on issue 321 by tudor.gi...(a)gmail.com: Problems using java code importer with inFusion in windows http://code.google.com/p/moose-technology/issues/detail?id=321 The command should be taken away from the menu until OSProcess works properly.

13 years, 7 months

1
4
0 0

Re: Issue 384 in moose-technology: Properties pane in Glamour

by moose-technology＠googlecode.com

Updates: Status: Duplicate Mergedinto: 716 Comment #1 on issue 384 by tudor.gi...(a)gmail.com: Properties pane in Glamour http://code.google.com/p/moose-technology/issues/detail?id=384 The more general issue is described in 716.

13 years, 7 months

1
0
0 0

Re: Issue 114 in moose-technology: Resizable panes in Finder

by moose-technology＠googlecode.com

Updates: Labels: -Milestone-4.2 Milestone-4.3 Comment #6 on issue 114 by tudor.gi...(a)gmail.com: Resizable panes in Finder http://code.google.com/p/moose-technology/issues/detail?id=114 The basic structure is in place. There are still a couple of things to do: - include the changes to GeneralScrollPane - solve the small scrolling animation problem

13 years, 7 months

1
4
0 0

Re: Issue 122 in moose-technology: Support for keyboard-based navigation in Glamour

by moose-technology＠googlecode.com

Updates: Status: WontFix Comment #5 on issue 122 by tudor.gi...(a)gmail.com: Support for keyboard-based navigation in Glamour http://code.google.com/p/moose-technology/issues/detail?id=122 This will not work anytime soon.

13 years, 7 months

1
0
0 0

Re: Issue 334 in moose-technology: While computing duplication SmallDude does not show a progress bar

by moose-technology＠googlecode.com

Comment #5 on issue 334 by tu...(a)tudorgirba.com: While computing duplication SmallDude does not show a progress bar http://code.google.com/p/moose-technology/issues/detail?id=334 Issue 667 has been merged into this issue.

13 years, 7 months

1
2
0 0

Issue 736 in moose-technology: OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:

by moose-technology＠googlecode.com

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

13 years, 7 months

1
2
0 0

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, 7 months

1
3
0 0

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, 7 months

1
1
0 0

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, 7 months

1
0
0 0

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, 7 months

3
14
0 0

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, 7 months

2
5
0 0

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, 7 months

3
12
0 0

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, 7 months

3
10
0 0

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, 7 months

3
4
0 0

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, 7 months

2
1
0 0

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, 7 months

2
5
0 0

How do we push changes into moose

by Stéphane Ducasse

Hi this is still totally unclear to me how I can change Moose and get my changes not breaking parts of moose that I do not know or are not loaded? I want to work on the importer/extractor proposal I sent around last week. So I can implement the changes but what is the process? Stef

13 years, 7 months

3
5
0 0

Classes and Namespaces imported by a Java class

by Alberto Bacchelli

Hi, Given a FAMIXClass, generated from a Java project parsed with Verveine-J, is it possible to know the classes that it imports? I am referring to this kind of information: import org.argouml.application.events.ArgoDiagramAppearanceEvent; import org.argouml.application.events.ArgoEventPump; It should be easy to write a parser that gets these "imports" from the completeText of the FAMIXFileAnchor, but I don't want to write it if I can have this information more easily. Thanks again. Cheers, Alberto -- View this message in context: http://moose-dev.97923.n3.nabble.com/Classes-and-Namespaces-imported-by-a-J… Sent from the moose-dev mailing list archive at Nabble.com.

13 years, 7 months

5
5
0 0

MooseMonticelloImporter class comment

by Stéphane Ducasse

what about? "MooseMonticelloImporter is a dedicated Smalltalk importer that extends the default Smalltalk importer to deal with classes and methods that are not loaded in memory but contained in Monticello packages." I imagine… so I will publish that and we fix it if this is wrong. Stef

13 years, 7 months

1
0
0 0

About Moose-SmalltalkImporter

by Stéphane Ducasse

Doru This package is bogus because it is incomplete. The importing superclasses taks are missing. They should not be in another package. It is a pain to find our way. Because these classes are not in the Moose-GenericImporter too. but somewhere in between. MooseImportingTask should not be in generic importer too. because it is only for Smalltalk. So I started to commit some changes. Stef

13 years, 7 months

1
1
0 0

removed #FamixSmalltalkImporterManifesto

by Stéphane Ducasse

because it was an experiment. Stef

13 years, 7 months

1
0
0 0

what is a ManifestMfBundle?

by Stéphane Ducasse

ManifestMfBundle has not been documented yet. The class comment should describe the purpose of the class, its collaborations and its variables. Instance Variables: name <ProtoObject | PseudoContext> requiredBundles <Collection> ManifestMfImporter has not been documented yet. The class comment should describe the purpose of the class, its collaborations and its variables. Instance Variables: bundles <(Collection of: Object)> Why people do not put comments in classes? Am I that stupid that I do not understand anything? It is really annoying to have to guess all the time. I crawl crawl and crawl. Stef

13 years, 7 months

2
3
0 0

what are naming convention

by Stéphane Ducasse

Hi in http://www.themoosebook.org/book/internals/famix/core/overview there is todo naming convention for attributes what does it means? naming convention for classes, package, methods, attributes? Stef

13 years, 7 months

2
4
0 0

A real issue…. should I fork my code in Moose

by Stéphane Ducasse

Hi moosers http://code.google.com/p/moose-technology/issues/detail?id=744 I want to rename the classes I wrote apparently this is not valid. So should I fork my code? This can be quite easy in fact but it will lead with some mess. Stef

13 years, 7 months

2
2
0 0

Issue 744 in moose-technology: SmalltalkImporter should be renamed SmalltalkExtractor

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 744 by usman.bh...(a)gmail.com: SmalltalkImporter should be renamed SmalltalkExtractor http://code.google.com/p/moose-technology/issues/detail?id=744 to convey the fact that it goes from source code to model

13 years, 7 months

2
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev