- Moose-dev - INF Mailman

mapping developers expertise to source code entities

by Fabrizio Perin

Hi, someone can tell me if there is some Moose related tool that i can use to map the expertise of the developers to the source code entities? Kumpel maybe is suitable? Thanks. Cheers, Fabrizio Perin Institut fuer Mathematik und Informatik University Bern, IAM-SCG Neubrueckstrasse 10 CH-3012 Bern, Switzerland Tel: +41 31 511 76 36 FAX: +41 31 631 33 55

13 years, 9 months

2
2
0 0

using the glamour editor with novices

by Tudor Girba

Hi, Today, I gave a Moose training to three developers, and I had the opportunity to see the new Mondrian and Glamour editors being used by novices. They worked well. In particular it is cool to see Glamour being edited and rendered using a Glamour browser :). Seriously, the instant feedback you get from playing in the editor improves the learning curve. There are still a couple of things to be improved, but all in all, I am rather satisfied. Cheers, Doru -- www.tudorgirba.com "Reasonable is what we are accustomed with."

13 years, 9 months

1
0
0 0

fonts in moose environment

by Usman Bhatti

hello all, I am trying to import machine fonts in Moose. I am doing world menu -> system -> settings -> appearance -> standard fonts ... There is an option to "update fonts from system". However, this option does not bring machine fonts in Moose. When I perform the same manipulation in Pharo environment, it provides me a long list of all machine fonts. Any ideas regarding how import all system fonts in Moose? thanx Usman

13 years, 9 months

2
1
0 0

Petit Puzzle

by Norbert Hartl

Hi, I want to ask if there is a elegant solution for the following problem: In my grammar there are references (symbols/names that reference entities somewhere). One is Syntax>>typeReference ^ self failOnReservedWords: ( #uppercase asParser, (#word asParser plus separatedBy: $- asParser) optional ) flatten These typeReferences can be standalone tokens (parsed with a token parse class that parses whitespaces and comments) Syntax>>reference ^ typeReference asn1Token / valueReference asn1Token / ... with PPParser>>asn1Token ^ (ASN1TokenParser on: self) ==> [:node| node value] or embedded in another type Syntax>>valueSetFieldReference ^ $& asParser, typeReference If have two classes, one for the syntax and for the parsing into model objects. Every typeReference should be parsed in the parser class to Parser>>typeReference ^ super typeReference ==> [:node| ASN1ReferenceNode new name: node ] The problem is that it is hard to have the typeReference be tokenized or not and make sure they are all parsed to the ASNReferenceNode. The example above Syntax>>reference ^ typeReference asn1Token / valueReference asn1Token / ... does not work because typeReferences result is transformedd to the model class but the asn1Token applied afterwards gives back a string again. I tried having a second parser typeReferenceToken but that only works if I double the code of typeReference in syntax and parser class. And as I am running short of instance variables I would prefer a solution without having the need for creating new instance variables. Any ideas? I hope I could explain the problem enough to get you the context you need, Norbert

13 years, 9 months

2
3
0 0

to analysis several versions of mc you should contact veronica

by Stéphane Ducasse

because she is building an infrastructure for that and she needs help writing tests and ... Stef

13 years, 9 months

2
1
0 0

asEnglishPlural, removeSuffix:, removePrefix: ?

by Alexandre Bergel

Hi! Apparently these method are used in Moose but are defined nowhere. As a quick hack: String compile: 'asEnglishPlural ^ self'. String compile: 'removePrefix: v ^ (self beginsWith: v) ifTrue: [ self copyFrom: v size + 1 to: self size ] ifFalse: [ self ]'. String compile: 'removeSuffix: v ^ (self endsWith: v) ifTrue: [ self copyFrom: 1 to: (self size - v size)] ifFalse: [ self ]'. Any idea what happened? Shall I open an issue? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 9 months

2
3
0 0

a few Pettit questions

by drush66

I have just watched video of Tudor's great hands on PettitParder tutorial on ESUG, and few questions poped up to me. 1. in PPMSEGrammar, start is encoded ad ^elements end is that a good habit to include end in start method? Somehow this is counter intuitive to me since it seems it would make such grammar non embeddable in another parser, or I am mistaken? 2. can ==> be cascaded in a sense that if we have parser A, its subclass parser B which calls supper and then adds ==>. Can we then have C which is subclass of B, and adds its ==> on top of the one added by B? 3. What do you think, could PettitParser be reasonably used to de-marshal some (binary) network protocol. By reasonably I mean that it would not be an order of magnitude slower than some code hacked from the scratch (but not terribly optimized). -- View this message in context: http://forum.world.st/a-few-Pettit-questions-tp3877633p3877633.html Sent from the Moose mailing list archive at Nabble.com.

13 years, 9 months

3
2
0 0

Importing from Monticello is not working properly

by Santiago Vidal

Hi, The Monticello FAMIX model importer is not creating the following items: - All famixattributes - All famixglobalvariables - All famiximplicitvariables - All famixinheritances - All famixnamespaces - All famixpackages - All model namespaces - All model packages This bug creates some additional problems. For example, the properties numberOfStatements and weightedMethodCount for a class are negative. When I imported the same version of a package using the "ST" option the items were created. Any idea on how to solve it? Thanks Cheers -- Santiago Vidal

13 years, 9 months

4
6
0 0

mondrian easel

by Stéphane Ducasse

doru a point: why dont you use the space on the right because there is only one line fr the binding and nobody use it: so having three lines and the rest for actionners would be good. for the examples I discussed with andre and having the examples in front of the nos of people is important not in yet another browser finally there was a menu to install a script in a class long time ago. I think that this feature is important because it shows that scripting is not the end of the path but a nice way to improve and enhance the system. Stef

13 years, 9 months

3
2
0 0

update on CAnalyzer

by Alexandre Bergel

Hi! CAnalyzer has been updated with the last version of Moose. It works well, but does not follow the Moose rules and conventions (e.g., I do not know whether the metamodel is properly Fame compliant, it does not use MooseChef). In any case, large C programs are loadable in the last version of Moose. I will keep you informed about my progresses. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 9 months

2
2
0 0

Sexy font look

by Stéphane Ducasse

Hi guys we are preparing some videos around moose and we would like to use good (and large) fonts. Do you have some experience/suggestions in this area? Stef

13 years, 9 months

1
0
0 0

Selecting edges for coloring

by Usman Bhatti

Hello, We are working on the visualization of plugins in Mondrian and we are trying to create some custom visu. Question: Is there anyway we can color a few edges in Mondrian according to some condition? That is, we are trying to describe a condition for coloring edges according to the plugin they target as illustrated by the bold line in the script below: view shape rectangle width: [:p | p outgoingFAMIXEclipsePluginImport size] ; height: [:p | p incomingFAMIXEclipsePluginImport size] ; if: [ p | p name includesSubString: 'uml'] fillColor: Color blue. view nodes: (eclipsePluginGroup select: [:p | p name includesSubString: 'papyrus']). view shape arrowedLine *if: [ :i | i target name = 'org.eclipse.papyrus.core'] fillColor: Color red.* view edges: (MooseModel root allModels first allWithType: FAMIXEclipsePluginImport) from: #source to: #target. view dominanceTreeLayout . thanx in advance, Usman & Nicolas

13 years, 9 months

3
5
0 0

what is \*

by Stéphane Ducasse

Hi guys what is \* in Root := Document ? Document := OPEN ElementNode \* CLOSE ElementNode := OPEN NAME Serial ? AttributeNode \* CLOSE

13 years, 9 months

3
7
0 0

MOndrian easel: why the generate view button disappeared?

by stephane ducasse

HI guys I did a demo yesterday and the new little icon does not work from a ui perspective. When you do change like that it would be good that: - they are discussed in the mailing-list - that proposed changed are not worse than before: a check button is not an actuator it is a check box. Stef

13 years, 9 months

6
15
0 0

Mondrian: use of MOVerticalLineWithTimelineLayout

by Veronica Isabel Uquillas Gomez

Hi, How can I use the MOVerticalLineWithTimelineLayout? I can't find any example, could the author provide an example? Thanks, Veronica

13 years, 9 months

2
5
0 0

mondrian: edge from/to the same node

by Veronica Isabel Uquillas Gomez

Hi, Is it possible to have an edge from nodeX to nodeX? I am trying without success, and even if I use node and a copy of that node the edge is not drawn. Any idea? Cheers, Veronica

13 years, 9 months

3
4
0 0

About "SimpleXO"

by Stéphane Ducasse

Hi steffen Moose people and pharoers are interested in your library to map XML to objects. So I was wondering what was its status. Do you got a bit more documentation/tests because I would like to start reading them so that after I can see what we can do to help. Stef

13 years, 9 months

1
0
0 0

solution to import information in XML format in Moose

by Stéphane Ducasse

Hi guys I was discussing with andre and I would like to know what are the solutions that we have in Moose for the following two scenarios. We have a model in FAMIX 1- we want to create entities that are described (probably exported by another tool) in XML. 2- we want to annotate existing entities Another scenario would be to turn XML into mse and create Smalltalk class of the metamodel but this is another story. Doru I do not remember the goal and status of OPAX. Stef

13 years, 9 months

3
2
0 0

Issue 719 in moose-technology: XMLSupport should be in the distribution

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-XML Milestone-4.6 New issue 719 by tudor.gi...(a)gmail.com: XMLSupport should be in the distribution http://code.google.com/p/moose-technology/issues/detail?id=719 XMLSupport was taken out of the configuration because it used to be shipped with Pharo. However, it is not present in Pharo 1.3 anymore. So, we have to add it back to the ConfigurationOfMoose.

13 years, 9 months

1
1
0 0

Issue 717 in moose-technology: Hismo and isStub

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Hismo Milestone-4.6 New issue 717 by alexandr...(a)gmail.com: Hismo and isStub http://code.google.com/p/moose-technology/issues/detail?id=717 The following test fails. No idea why. ClassB is a stub -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= testStubAndHismo | allModelClasses allHistoryModelClasses mooseSampleData sampleMooseModel hismoHistoryModel | mooseSampleData := MooseSampleData new. sampleMooseModel := (mooseSampleData readMSEString: self sampleMSE) name: #'example'. allModelClasses := sampleMooseModel allModelClasses. self assert: (sampleMooseModel allModelClasses size = 1). self assert: (sampleMooseModel allClasses size = 2). hismoHistoryModel := HismoModelHistory new. hismoHistoryModel addLastVersionForMooseModel: sampleMooseModel. allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last isStub not]. self assert: allModelClasses size = allHistoryModelClasses size sampleMSE ^ '( (FAMIX.Namespace (id: 1) (name ''aNamespace'')) (FAMIX.Class (id: 2) (name ''ClassA'') (container (ref: 1)) (parentPackage (ref: 201))) (FAMIX.Method (name ''methodA1'') (signature ''methodA1()'') (parentType (ref: 2)) (LOC 2)) (FAMIX.Attribute (name ''attributeA1'') (parentType (ref: 2))) (FAMIX.Class (id: 3) (name ''ClassB'') (container (ref: 1)) (isStub true) (parentPackage (ref: 201))) (FAMIX.Inheritance (subclass (ref: 3)) (superclass (ref: 2))) (FAMIX.Package (id: 201) (name ''aPackage'')) (FAMIX.Package (id: 202) (name ''aPackage'') (parentPackage (ref: 201))) )' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Indeed, it looks like MooseEntity>>isStub is the trouble maker. We need to create an issue. In the meantime you can use: allHistoryModelClasses := hismoHistoryModel allClassHistories select: [:each | each last versionEntity isStub not].

13 years, 9 months

1
1
0 0

Issue 718 in moose-technology: Glamour editor should provide a wrapping browser in preview

by moose-technology＠googlecode.com

Status: New Owner: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.6 New issue 718 by tudor.gi...(a)gmail.com: Glamour editor should provide a wrapping browser in preview http://code.google.com/p/moose-technology/issues/detail?id=718 Currently, we cannot refer properly to the outside pane from a glamour script in the editor. The reason is because the outer pane is also the pane that receives the script, and thus is not like the default pane that will surround the browser when opened normally. The solution is to wrap the preview in another browser that only forward the entity without the script.

13 years, 9 months

1
1
0 0

#mooseName and fully qualified name?

by Alexandre Bergel

Hi! [context: I am reviving CAnalyzer. My goal is to have it part of Moose for good. ] At the time I worked on it, we had mooseName that return the fully qualified name (e.g., 'file2.hunit.recGlobal'). This was quite handy to lookup value. For example, I could write: mooseModel entityNamed: 'file2.hunit.recGlobal' this will return the definition of recGlobal defined in the file2.h. Apparently, mooseName now returns the name (a String) as a symbol. The method printOn: return the fully qualified name. We had some discussion some times ago, but I kind of forgot what the motivation was for that change. Should't we have a way to fully quality entities? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 9 months

3
4
0 0

ok, more glamour questions

by Esteban Lorenzano

Hi, I have a browser with this form: buildBrowser | browser | browser := GLMTabulator new title: 'Game Viewer'; row: #galaxy; row: #status size: 25; yourself. browser transmit to: #galaxy; andShow: [ :presenter | presenter morph title: [ :aGame | aGame name ]; display: [ :aGame | (HGUIGalaxyMorph on: aGame galaxy) ]. browser transmit to: #status; from: #galaxy; andShow: [ :presenter | presenter text display: [ :aStar | aStar asString ] ]. ^browser problem is that HGUIGalaxyMorph is a very complex morph (well... it will be ;) )... and it updates some status around the "stars"... and I need to transmit that information to other panes... and I don't know how... so... that's the question: how I trigger an event? is that possible? if not... how it is supposed to do something like that? cheers, Esteban

13 years, 9 months

2
1
0 0

Issue 664 in moose-technology: MooseMenu - export GML graph

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 664 by jannik.l...(a)gmail.com: MooseMenu - export GML graph http://code.google.com/p/moose-technology/issues/detail?id=664 It should be cool to specify the place of the new file. For now, it is saved just near the image.

13 years, 9 months

2
9
0 0

Question about export metrics from Moose - with attached

by Paloma Maira de Oliveira

Hello! I'm in trouble (attached) to run the script below: Gofer new squeaksource: 'FameImportExportEx'; package: 'Fame-ImportExport-Extensions'; load. I’m using Windows-OS and Moose Suite 4.5. I need help to export metrics to .CSV. Where should I run the script? I’m running the workspace Moose Suite 4.5, correct? Thank you. -- PROF. PALOMA MAIRA DE OLIVEIRA __________________________________________________________ IFMG - Campus Formiga Doutoranda em Ciência da Computação - DCC/UFMG Mestra em Modelagem Matemática e Computacional - CEFET/MG Bacharel em Ciência da Computação - UNIFOR/MG

13 years, 9 months

4
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev