Hi,
I've been trying to create MSE files of C++ applications with inFamix. When
exploring the created model I can't visualize simple metrics such as
numberOfLinesOfCode. Is there an option to export this metric with inFamix?
Thanks
--
Santiago Vidal
mooseFinderMetanoolIn: composite
<moosePresentationOrder: 10>
composite magritte
title: 'Meta editor';
titleIcon: MooseIcons mooseEditor;
display: [:anObject | anObject mooseInterestingEntity ];
act: [:m |
| result annotationDescription |
annotationDescription := MTLAnnotationDescription new.
result := annotationDescription asMorph addButtons addWindow callInWorld.
In Moose 4.7 the previous line open an empty window with save and cancel
in 4.6 it opens a name and list of type.
I checked and annotationDescription instance variables are exactly the same in both version.
Now this is really complex to understand, since I do not know what changed in magritte in addition.
Any idea?
Stef
self halt.
(result notNil) ifTrue: [
m entity mooseInterestingEntity mooseDescription attributes add: annotationDescription.
m update ] ]
icon: GLMUIThemeExtraIcons glamorousAdd entitled: 'Add annotation';
description: [ :anObject |
| description |
description := MAContainer new.
description label: anObject mooseDescription name.
anObject mooseDescription allAttributes do: [ :attribute |
(attribute isKindOf: MTLAnnotationDescription) ifTrue: [
description add: attribute asMagritteDescription ] ].
description
"anObject mooseDescription asMagritteDescription"
]
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 788 by stephane...(a)gmail.com: Annotation is broken
http://code.google.com/p/moose-technology/issues/detail?id=788
in the latest version of moose, click on the pen then on + and you cannot
create an annotation.
When creating a new issue in the tracker, the template says...
"Please fill in the labels with the following information:
* Type-Defect, Type-Enhancement, Type-Engineering, Type-Review,
Type-Other
* Component-XXX"
but I can't see where to do that. What am I missing ?
cheers, -ben
Yes there is. If I remember correctly there is a visitor or something like that that generates morphic or seaside.
Stef
On Apr 6, 2012, at 5:19 AM, Hernán Morales Durand wrote:
> Hi all,
>
> Is there any support for using Merlin (a wizard library) with Seaside? (or any other web framework like Aida or Iliad)
> Cheers,
>
> Hernán
>
Hi fellows,
I'm starting to use VerveineJ to parse java projects to MSE format. I want
to know if there's a way to set the output path/filename as a parameter of
the execution, instead of the default: "output.mse"
thanks in advance for your answer,
Matías Barahona.
Hi!
I think that Girb10a http://scg.unibe.ch/scgbib deserves an update :-)
@book{Girb10a,
Abstract = {This book offers an overview of the Moose platform
for software and data analysis. More specifically it
covers version 4.0.},
Author = {Tudor G\^irba},
Keywords = {skip-doi moose-pub girba},
Title = {The Moose Book},
Publisher = {Self Published},
Url = {http://www.themoosebook.org/book},
Year = {2010},
Bdsk-Url-1 = {http://www.themoosebook.org/book}
}
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Stef and I think that Kontractor should be include in Moose by default to
offer a tool for reducing title length.
Do you think it's a good idea and do you know a better tool to do this?
--
*Guillaume Larcheveque*
Hi,
when building some browsers, I often find that it would be useful to react in some way while choosing one tab.
For instance, in glamoroust codebrowser (the "standard" one), when you choose between "Instance" and "Meta", you should react in some way, to display class definition or class instance definition (just like regular browsers).
AFAIK, currently there is no way to achieve that. I think adding some protocol (#onSelect:, for instance) to composition presentations, has some sense... what do you think?
cheers,
Esteban
Hi,
I'm trying to customize the import context when loading an mse model by
using the method MooseModel>>importFromMSEStream: aStream filteredBy:
anImportingContext.
The main problem is that after creating the MSE model some metrics
are missing. For example, numberOfLinesOfCode is always 0 for a class. When
I create the model without the importing context the metrics are fine.
The importing context that I'm using has the
following fullNamesOfEntitiesToBeExtracted: 'FAMIX.Comment' 'FAMIX.Access'
'FAMIX.Inheritance' 'FAMIX.Invocation' 'FAMIX.Reference' 'FAMIX.Function'
'FAMIX.Method' 'FAMIX.Module' 'FAMIX.Namespace' 'FAMIX.Package'
'FAMIX.AnnotationType' 'FAMIX.Class' 'FAMIX.Enum' 'FAMIX.ParameterType'
'FAMIX.ParameterizedType' 'FAMIX.PrimitiveType' 'FAMIX.TypeAlias'
'FAMIX.EnumValue' 'FAMIX.GlobalVariable' 'FAMIX.ImplicitVariable'
'FAMIX.LocalVariable' 'FAMIX.Parameter' 'FAMIX.UnknownVariable'
'FAMIX.ParameterizableClass' 'FAMIX.AnnotationTypeAttribute'
Any help? Thanks
Cheers,
Santiago
--
Santiago Vidal
Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-EyeSee
New issue 787 by andreho...(a)gmail.com: Vertical legend is not working
http://code.google.com/p/moose-technology/issues/detail?id=787
Command verticalLegend (ESVerticalLegend) is not working.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-MooseTools
New issue 786 by anquetil...(a)gmail.com: MooseQueryResult>>intersection: is
broken
http://code.google.com/p/moose-technology/issues/detail?id=786
calling intersection between two MooseQueryResult produces an error
because "MooseQueryResult is not a variable type"
This is raised in basicNew:
A possible workaround is to redefine MooseQueryResult>>intersection:
aCollection
| result |
result := self class new.
aCollection do: [ :each|
((self includes: each) and: [(result includes: each) not])
ifTrue: [ result add: each]].
^ result
But it might not be the best solution since I assume basicNew: might be
called from other methods ...
Hi,
I loaded all my stuff in the latest moose based on 1.4.
All the tests of my PetitPHPParser are red. When I click on one red method
the emergency evaluator pops up.
To reproduce it:
1- grab the latest MooseJee from the ci:
http://ci.moosetechnology.org/job/moose-latest-dev/
2- load the petit php parser:
Gofer new
squeaksource: 'PetitPHPParser';
package: 'ConfigurationOfPetitPHPParser';
load.
(Smalltalk at: #ConfigurationOfPetitPHPParser) perform: #loadDefault.
3- Run the tests of the php parser and click on any red method.
How can I debug the problem? Any suggestions on how to proceed?
Thanks,
Fabrizio
Background:
I am trying to use Mondrian to visualize SomeContainerClass holding
SomeOtherContainerClass that holds Equipment classes. So I was thinking
each container class might have a method (#subviewOf: aView) which at
some point does (aView forNode: self do:). Now I have come to the
understanding that I am probably misusing #forNode:do: like that, and am
continuing exploring that, but thought I would report the MNU that I
encountered before moving on - just in case it was desirable to guard
against such abuse.
Steps to Reproduce:
The essence of this distills down to the following in Mondrian Easel,
where this first case works....
view nodes: (1 to: 20).
view forNode: 2 do: [ view nodes: (50 to: 52) ]
but this second case...
view nodes: (1 to: 20).
view forNode: view do: [ view nodes: (50 to: 52) ]
gets MNU "removeAllEdges"
Inserting 'self halt' between the two lines and tracing through to
MONode>>nodeWith:ifAbsent shows the line...
nodeLookedUp := self nodes detect: [:each | each model =
anObject ] ifNone: aBlock.
has in the first case (self nodes) as anOrderedCollection of 20 items
and in the second (self nodes) is an empty Array.
Just reporting for discussion. I am not sure if this would be
considered a bug worth tracking, or just an abuse of the framework.
Cheers, Ben
Hi,
I have a problem with automoose and jenkins.
I basically use automoose to load some code than at the end of the st file
I do:
Gofer new
renggli: 'hudson';
package: 'HudsonBuildTools';
load.
"Run reports"
report := MyReport on: MooseModel root first.
report open.
REPHudson runOn: report spec.
SmalltalkImage current snapshot: true andQuit: true.
What happen is that jenkins ends with a failure claiming that there are no
test runned but the xml file generated by REPHudson is in the folder
together with the Moose image.
Do I miss something? Shouldn't jenkins report about the Arki report?
Thanks for any help.
Cheers,
Fabrizio
Is there a way to load PetitGui with a smaller set of dependecies? Or is Magritte and Grease and etc. needed for the GUI? Loading PetitParser default loads default of Glamour, too. And that's quite a lot.
thanks,
Norbert
Hi,
I'm working on a treemap layout in Mondrian. I created the basic
functionality but am far from finished.
For the current progress see the following screenshots:
http://cl.ly/342z261g021c3X1j3X2b - A visualization of a very simple java
system (https://github.com/mircealungu/SimpleSample)
http://cl.ly/3H3x1K1y3O3j430S0a2z - A visualization of FAMIX itself.
The following is an example of how one sets up the layout:
viewTreemapOn: view
> view nodes: self nodes.
>
> view edges: self nodes
> from: [ :each | each ]
> toAll: [ :each | each children ].
>
> view layout: (MOTreeMapLayoutIncubation withWeightBlock: [ :e |
> | model |
> model := e model.
> model isNil ifTrue: [
> 0.
> ]
> ifFalse: [
> e model entity numberOfLinesOfCode.
> ].
> ]).
The tree structure is given by the edges definition. The layout is created
with a weight block (lines of code here, but could be anything).
At the end I'd like to have something like:
http://cl.ly/3v1L3O2a2n1H1C2x3J0V - TreeMap in Softwarenaut in VisualWorks.
This is the first code that I'm writing with Mondrian, so I'm sure it could
be improved in many areas. If anyone sees a problem with how I set up the
layout. please do tell. If anyone wants to look at the code in detail
please take a look at MOTreeMapLayoutIncubation in my
Softwarenaut repository (I'm creating the tree map layout as part of the
Softwarenaut port to Pharo):
MCHttpRepository
> location: 'http://www.squeaksource.com/Softwarenaut'
> user: ''
> password: ''
The layout is currently in this repo, if it is more mature, it would be
cool to add it to Mondrian itself. I'd like to make it as generic as
possible.
Now for some specific questions:
The red colors you see in the screenshots is actually a bug. What I would
like to do is only color the leaf nodes, but somehow (my guess is, it has
something to do with shape caching?), it also colors the containment blocks.
The way I do it is, while ging through the nodes (MONode) to draw them
If it is a leaf
> node shape fillColor: ((Color fromString: '#ff0000') alpha: 0.1).
If it is a containment block:
> node shape fillColor: (Color fromString: '#eeeeee').
But somehow all shapes (except the root node) are colored with the red
translucent color. Does anyone have an idea why this could be the case?
In general: I'm doing the styling of the nodes (also tried to add some
interactivity) directly inside the layout, but I'm not sure if this is the
Mondrian way to do this, since normally shape definitions and interaction
is defined when creating the view. Is this okay? Or should I do this in
another way?
My thought was that I'd like to have a treemap layout with default, nice
looking interactions, colors etc. without having to define them outside,
when defining the view, so it needs as little setup as possible.
Any inputs in general are greatly appreciated.
Cheers,
Dennis
Dear all,
we already discuss about that in the moose and pharo mailing-list.
Maybe this is too late, but please find a small proposal for gsoc 2012 below.
================================================================
Name: SciSmalltalk
Level: Intermediate
Possible mentor: Serge Stinckwich
Possible second mentor: ?
Description
Smalltalk has at that time no equivalent to mathematical libraries
like NumPy, SciPy (Python) or SciRuby (Ruby).
The goal of the SciSmalltalk project is to develop an open-source
library of mathematical for the Smalltalk programming language (MIT
Licence).
Technical Details
The development of this project is to be done in Pharo Smalltalk, but
the code should be portable to other Smalltalk flavors.
Numerous Smalltalk projects provide already some basic functionalities
(complex and quaternions extensions, random number generator, fuzzy
algorithms, LAPACK linear algebra package, Didier Besset's numerical
methods, ...). A first task will be to do an audit of all the existing
projects that provide some mathematical stuff and build a Pharo
Configuration to load them in a fresh Pharo Smalltalk image. After
that, the student help by his/her mentors will decide what are the
numeric algorithms to develop in priority.
The student will need to know some basic numeric algorithms usually
found in such libraries.
Units tests should also be provided.
Benefits to the Student
The student will help the Smalltalk community in a very concrete way.
The student will learn to design well-designed code with tests.
Benefits to the Community
Having a package providing more elaborate numeric libraries is really
important to develop the use Smalltalk in new domains (robotics, high
performance computing, computer vision, bio-computing, ...). The lack
of numeric librairies hamper the use of the Smalltalk in a scientific
context at the moment. An another goal of this project is to develop a
community of people interested by these topic.
Regards,
--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/
Hi,
I imported a Model generated with InFamix and i tried to navigate the model
with the MooseFinder. Once I click on class the debugger opens with a MNU:
receiver of "classScope" is nil. In fact FAMIXLacalVariable>>belongsTo
returns nil.
Anybody have the same problem?
Cheers,
Fabrizio
Hi,
I was wondering how to open a MooseFinder on an element selected in another
browser. I tried something like this:
browser := GLMTabulator new.
browser
column: #functions;
column:#finder.
browser transmit
to: #functions;
andShow: [ :a |
a list
title: 'Functions';
display: [:each | each ]].
browser transmit
to: #finder;
from: #functions;
andShow: [ :a |
a finder
title: [:each | each mooseName];
.....
^ browser
but I don't know how to proceed (this is why I added the dots).
Any suggestion? Am I doing it the wrong way?
Cheers,
Fabrizio
In Mondrian I can drag nodes around the layout to make a more pleasing
graph. Is there a mechanism built in to facilitate saving and later
reloading the layout of a graph ? Or where should I look into to system
to implement this?
-cheers, Ben
I fixed the two Mondrian failing tests.
All these problems stems from the recent changes in the collection hierarchy. Somehow, the order of elements are not preserved. Here is an example:
Consider the script:
view nodes: (1 to: 4).
view edgesFromAssociations: {1 -> 2 . 1 -> 3 . 3 -> 4}.
view treeLayout
It displays this:
or this:
Before the recent collection changes, it was always the same layout, one of the two. So the tests need to be updated...
The build should be green again
Cheers,
Alexandre
On 27 Mar 2012, at 02:17, admin(a)moosetechnology.org wrote:
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/906/>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.