I loaded the latest version of moose.
MooseLoader load
Then I wanted to try to create a model
MooseLoader createModelForNetwork
Yesterday it worked perfectly I could open a MooseBrowser on it.
and now I cannot
it seems that the MSEPragmaProcessor is not in the image
Does anybody see the same?
Stef
Dear all,
I'm trying to use Moose but I didn't found documentation about the
scription in Easel. I try to get a map of all classes of my project
with the call links. If a method of a class call to an other method of
an other class I would like to have an edge between the two classes.
Can someone help me ? Here is the code I currently have:
view nodes: classGroup using: (RectangleShape withBorder height:
#numberOfMethods; width: #numberOfAttributes; linearFillColor:
#numberOfLinesOfCode within: classGroup).
view edges: classGroup from: #yourself toAll: #directSubclasses.
view treeLayout.
Thanks in advance,
Antoine C.
Hi
I loaded the latest version of Moose and now when I open a normal
package browser (the one of david) I have in addition
Src C. | Sys. Complex | UML diagram raises an error too.
UML diagram raises an error.
how to get rid of the SrcC. Sys.Complexity extra buttons in the
packageBrowser?
I would like to avoid to have the browser polluted with extra stuff. I
would already love to not have the default button bar since I never use
variables senders...
Stef
BTW these buttons appear in the MooseBrowser but they generate also
DNU there. ;(
Hi
I wanted to import pharo into moose and I did MooseBrowser open
import pharo packages....
and then I realized that I must click one by one on each packages.
Is it correct?
Stef
Hi
two remarks
First - It seems strange that candidateClass is defined in ImportingTask
while only the MooseCompositeImporterTask use it and also define the
method run and doNotRun
=> so I pushed down these methods to the right place and the instance
variable too.
MooseImportClassesTask could not run the candidateOperator (it still
cannot).
Now MooseImportClassesTask does not import but just spit out classes
so this is ok and updated the class comments
to reflect that.
Second
you normally do not have to specify the CandidateListOperator
(this is only to switch between FAMIX2 and FAMIX3)
so do not use it
Similarly do not use importerClass: if you do not need it.
It is set by default in ImportingTask>>initialize (this is only
to switch between FAMIX2 and FAMIX3)
Do not do
model := MooseModel new.
importer := MooseSqueakClassPackageImporterTask new.
importer importingContext mergeClassAndMetaclass.
importer candidateClass: CandidateListOperator.
importer importerClass: SmalltalkImporter.
importer model: model; addFromPackagesNamed: packagesToImport; run.
MooseModel root add: model.
but
model := MooseModel new.
importer := MooseSqueakClassPackageImporterTask new.
importer importingContext mergeClassAndMetaclass.
importer model: model; addFromPackagesNamed: packagesToImport; run.
MooseModel root add: model.
Dear All,
Computing the number of lines of code is realized through:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
FAMIXBehavioralEntity>>numberOfLinesOfCode
<MSEProperty: #LOC type: #Number>
<property: #LOC longName: 'Lines of code' description:
'The number of lines of code in a method'>
^self
lookUpPropertyNamed: #LOC
computedAs:
[self mooseModel isSmalltalk
ifTrue:
[| parser |
parser := VisualWorksParseTreeMetricCalculator new.
parser processMethod: self usingImporter: nil inModel: nil.
parser numberOfLinesOfCode]
ifFalse: [-1]]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
How to compute the number of lines of code with a C function?
How comes that this method is so closely related to Smalltalk ?
I am tempted to replace this method with something like:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
FAMIXBehavioralEntity>>numberOfLinesOfCode
<MSEProperty: #LOC type: #Number>
<property: #LOC longName: 'Lines of code' description:
'The number of lines of code in a method'>
^self
lookUpPropertyNamed: #LOC
computedAs:
[self source lineCount]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Where source will be defined as:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
FAMIXBehavioralEntity>>source
^ self sourceAnchor source
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Any comments before I proceed?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi All,
Simon and I discovered the pragma 'viewEvolutionMatrixOn: view '. It
is employed in ClassHistoryGroup>> viewEvolutionMatrixOn:.
What is this pragma for?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear List,
I tried to understand the ScatterplotLayout in VW. Few questions on
the design raised to me:
- Why NodeFigure has variables xBlock and yBlock. I understand what
these variables are for. However, I expected to see them in the shape,
since the node is meant to represent the model, and should therefore
not be aware of where it is supposed to be displayed.
- What xOffset and yOffset are for? I could not really infer their
meaning from the various examples I found
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi guys,
Does anybody have models of the evolution of Azureus in mse format? I
had multiple versions, but they are in xmi and moose can not load
them anymore...
A nice day.
Mircea.