- Moose-dev - INF Mailman

by Stéphane Ducasse

On Jun 26, 2011, at 6:59 PM, Alain Rastoul wrote: > Hi all, > > Do someone know about a PetitParser grammar for c# or java ? > Verveine seems to be a Java development (and is not accessible). Verveine is based on JDT. > TIA > > Cheers > Alain > > > >

14 years

1
0
0 0

Fwd: [Pharo-project] Moose out of memory

by Stéphane Ducasse

Begin forwarded message: > From: "Alain Rastoul" <alr.dev(a)free.fr> > Date: June 26, 2011 6:43:58 PM GMT+02:00 > To: pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Moose out of memory > Reply-To: Pharo-project(a)lists.gforge.inria.fr > > Hi, > There was a previous message in the list about an out of memory problem with > Moose when running > 3 times MooseScripts createModelForConfigurationOfMoose > I downloaded moose suite 4.5 (Pharo 1.3) and played a bit with it reading > the moose book (nice). > > IMHO although something is perhaps not completly clear in the vm in memory > allocation and/or ui process and/or low space watcher (I tryed to debug the > vm but did not succeed), here the problem seems to be in the Moose model. > I suspect that the problem is just that the cache keeps a reference to the > Moose model each time the script is run, see at the end of > MooseScripts>>createModelForConfigurationOfMoose the model is added to a > cache ((MooseModel root => MooseGroupRuntimeStorage>> byType) and takes abut > 130M of memory each time. > clearing the Moose cache resolve the problem. > MooseModel allInstancesDo:[ :m | m remove ] seems to be working here, except > that there is an exception for the root model (I don't know Moose, it may > not be the best command). > Perhaps the moose model should not be added by type but overriden each time > (beeing identified by a "name" ?). > > PS: Moose is cool :) > > Cheers > Alain > > > >

14 years

1
0
0 0

PetitParser: refer to previous values

by Sean P. DeNigris

Is there a way to do something like: #digit asParser, 'same digit that I just parsed' asParser ? I snooped around and saw PPMemoizedParser, but didn't exactly understand the test for it. Thanks. Sean -- View this message in context: http://forum.world.st/PetitParser-refer-to-previous-values-tp3624600p362460… Sent from the Moose mailing list archive at Nabble.com.

14 years

3
3
0 0

FamixXML

by Andre Hora

Hello, I created a extension of the FAMIX meta-model to support XML. It was also implemented an importer, some metrics and some simple visualization to the XML tree. The importer is in "Import FAMIX XML model from file sources" on the import menu of Moose. It possible to import: setting a file, a directory with XML files or from an URL. Visualization is now under a group of FAMIXXMLElement -> FAMIXXMLElementGroup. To try, first install the last version of Merlin and then the FamixXML: Gofer new squeaksource: 'FamixXML'; package: 'ConfigurationOfMerlin'; load. (ConfigurationOfMerlin project version: #development) load. Gofer new squeaksource: 'FamixXML'; package: 'ConfigurationOfFamixXML'; load. (Smalltalk at: #ConfigurationOfFamixXML) perform: #loadDefault regards, -- Andre Hora

14 years

1
0
0 0

Eclipse plugins

by Nicolas Anquetil

For a project on a large Eclipse Application (Papyrus, for drawing UML graphs), we needed to add Eclipse Plugins. Jannik did a first implementation in Famix to be able to run moose, but it would be nice to do-it-right. So the proposition would be (this is not how we implemented it right now): FamixComponent sub-concept of FamixEntity has: - belongsTo another FamixComponent - childNamedEntities A component is suppose to provide interfaces and require interfaces. How can we represent that? with Type? Eclipse plugins actually decalre other plugins that they require. I believe this is not standard as component should only rely on interfaces, not other explicitly named components ... all input welcome nicolas

14 years

4
19
0 0

an explanation for the complexity of software

by Alexandre Bergel

Interesting case http://www.pcworld.com/businesscenter/article/230747/couple_charged_in_mass… Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years

1
0
0 0

Issue 649 in moose-technology: PNG, BMP, GIF exports do not work anymore in Mondrian

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Mondrian Milestone-4.5 New issue 649 by tu...(a)tudorgirba.com: PNG, BMP, GIF exports do not work anymore in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=649 The dialog appear, but the files are not created.

14 years

1
8
0 0

Issues 4.5

by Laval Jannik

Hi, We have the release 4.5 now. So I think the issues flagged 4.5 should be flagged 4.6 no ? Cheers --- Jannik Laval

14 years

3
3
0 0

Porting Hapax to Pharo

by Simon Denier

I would like to port Hapax from the SCG store to Pharo (seems like a good candidate tool to perform some analysis here on my current project). Some bits have already been ported in Moose-Algos, but I don't think that the Hapax engine was ported itself. Unfortunately my VW image seems completely broken (doesn't launch or hand on start up) so I can't perform the initial step of building MC packages. Does anybody have a working VW image? If yes, can you load Hapax and export it to the squeaksource project Moose-Algos? http://scg.unibe.ch/wiki/howtos/portingfromvisualworkstosqueak -- Simon Denier

14 years

2
7
0 0

export format for moose

by Stéphane Ducasse

Hi guys a client suggested to me that it would be to have - a tab separated exporter to export metrics: (so it would be good to connect the menu with the functionality). - and an xml format so that people can write xls shit. We should spend two hours and get that available Stef

14 years

2
1
0 0

30 students using Moose

by Alexandre Bergel

Hi! Yesterday evening I put 30 engineers in front of Moose. They had no prior knowledge about Smalltalk and visualization. I gave them many examples on how to write scripts in Mondrian. It was an amazing success. People really liked it. So yes, Moose can be use at a low cost for teaching. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years

2
1
0 0

Accessing smalltalk classes after model computation

by Cyrille Delaunay

Hello, I'm not sure this is a problem, but here is the error I had: FAMIXMethod >> numberOfMessageSends <property: #MSG longName: 'Number of message sends' description: 'The number of message from a method'> ^self lookUpPropertyNamed: #MSG computedAs: [self mooseModel isSmalltalk ifTrue: [| parser | parser := VisualWorksParseTreeMetricCalculator new. parser *processMethod:* self *usingImporter: *nil *inModel:* nil. parser numberOfMessageSends] ifFalse: [-1]] Here, to compute this property, we ask the smalltalk compiled method (throught the method in bold). So, if I generate a model, then remove a method in pharo, then ask the corresponding FAMIXMethod for #numberOfMessageSends, it will raise an error because it does not find the compiled method anyMore. Maybe we should force the computation of this kind of property at the model computation ?

14 years

3
2
0 0

Re: FW: Fwd: problems linking code

by Franco Sabadini

Hi, we already tried that as we said we tried the 2 posibilities that appear on the moose book, and none of them work. After doing that we go to Browse -> Source and we can't see the code. Any other ideas? Thanks. - Franco 2011/6/21 Juan Francisco Hurtado <juan.yue(a)hotmail.com> > > Subject: Re: [Moose-dev] Fwd: problems linking code > > From: tudor(a)tudorgirba.com > > Date: Tue, 21 Jun 2011 18:28:45 +0200 > > CC: juan.yue(a)hotmail.com > > To: moose-dev(a)iam.unibe.ch > > > > Hi, > > > > What exactly did you do? > > > > One way to do it is like this: > > > > - download the mse file for argouml 0.28.1 and load it in Moose > > http://themoosebook.org/download/ArgoUML-0-28-1.zip > > > > - download and unzip the corresponding sources > > > http://argouml-downloads.tigris.org/nonav/argouml-0.28.1/ArgoUML-0.28.1-src… > > > > - you should get the following folders > > ArgoUML-0.28.1/ > > src/ > > > > - select the model in Moose Panel, right click and then Utilities/Set > root folder > > > > - point it to the ArgoUML-0.28.1 folder > > > > Cheers, > > Doru > > > > > > > > > On 21 Jun 2011, at 17:48, Franco Sabadini wrote: > > > > > > > > > > > ---------- Forwarded message ---------- > > > From: Franco Sabadini <fsabadi(a)gmail.com> > > > Date: 2011/6/21 > > > Subject: problems linking code > > > To: info(a)moosetechnology.org > > > Cc: juan.yue(a)hotmail.com, Santiago Vidal <santiago.a.vidal(a)gmail.com> > > > > > > > > > Hello, > > > > > > We're trying to use Moose to analyze code replication on a Java > application, but we haven't been able to link the model with the code, we > already tried the 2 possibilities that are shown on the moose book and > nothing worked, also we tried to do it with ArgoUML app and we couldn't do > it either. > > > > > > The Moose versions we tried are from 4.0 to 4.5, and we tried it in > linux, windows and in mac OS. > > > > > > Do you have any idea what could be happening? > > > > > > Thanks. > > > > > > > > > - Franco > > > > > > _______________________________________________ > > > Moose-dev mailing list > > > Moose-dev(a)iam.unibe.ch > > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > > www.tudorgirba.com > > > > "Speaking louder won't make the point worthier." > > >

14 years

1
0
0 0

Mondrian question

by Stéphane Ducasse

Hi guys I would like to have an edge drawn from a package to the classes that use it. I did but it does not work view interaction whenEnteringUpdateNode: [:node | view edgesToAll: #sureReferencingClasses.]. in view shape rectangle. view interaction menuMorphBlock: [ :element | element mooseMenuMorph ]. view nodes: model allPackages forEach: [:pack | view shape rectangle fillColor: Color orange; height: 7; width: 7. view interaction menuMorphBlock: [ :element | element mooseMenuMorph ]. view interaction whenEnteringUpdateNode: [:node | view edgesToAll: #sureReferencingClasses.]. view nodes: pack classes. view gridLayout gapSize: 2. ]. view gridLayout.

14 years

7
44
0 0

Problem with FS Git

by Simon Denier

I'm playing with FS-Git, see how we can use it to browse/extract information from a Git repository. Difficult to get started without a bit of information, but after a while it's ok I have one minor remark and a potential bug: 1) it would be cool to have the timestamp of the commit 2) when trying to recursively browse parents the commit tree, I stumble upon a DNU in GitPackedObject>>unpackRefDeltaContent unpackRefDeltaContent | s delta base | s := (GitObjectSignature loadFrom: file) resolve. "---> (GitObjectSignature loadFrom: file) returns an Integer, which can't answer to #resolve " delta := self readDelta. base := pack packedObjectAt: s. self applyDelta: delta to: base. Is this a known bug? I just tried this morning with the latest version of Camillo as well as with the previous version. -- Simon Denier

14 years

2
1
0 0

passing custom jars to verveinej

by Tudor Girba

Hi Nicolas, I would like to parse ArgoUML 0.32 and I would like to also be able to parse the annotations. For this, I understand that I should pass the jars to the parser. How do I make VerveineJ be aware of the jars? Do I have to edit the verveineJ.sh and add each of the jars to the classpath? Is there no other way? Cheers, Doru -- www.tudorgirba.com "Don't give to get. Just give."

14 years

3
5
0 0

[ANN] Moose Suite 4.5

by Tudor Girba

We are happy to announce the Moose Suite version 4.5: http://moosetechnology.org/download This is a minor release. What is new: • Important fixes in FAMIX to deal better with Java systems • Better EyeSee engine for scripting visual charts • Improved VerveineJ compatibility for Java parsing Have fun, The Moose Team http://moosetechnology.org

14 years

2
1
0 0

Git + Moose ? (Kumpel ?)

by Simon Denier

As another side project which could be of interest here, in order to demo the Moose platform, I would like to load a Git repo into Moose. I was thinking of using Kumpel for example and one of the current Git projects on Squeaksource. It looks like http://www.squeaksource.com/FSGit.html is the most recent project (May 2011). Is it up to date with the latest version of Pharo/FileSystem? I could load it in a 1.3 Core (a few tests red) but not in a Moose 4.4 (problem with RPackage). I am not knowledgeable in either FSGit or Kumpel. Is anyone working on something similar? Would it be difficult or cumbersome? -- Simon Denier

14 years

2
3
0 0

wait before releasing 4.5

by Alexandre Bergel

Hi! I would like to fix the exporter of Mondrian. I will do it today. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years

3
2
0 0

MondrianNew

by Tudor Girba

Hi, I took a look at MondrianNew. This is an API to construct explicitly every node and edge. There is no factory for you, at least not yet. This can be good or bad, depending on your model. Let's take an example: renderer := MORenderer new. node1 := renderer node on: 'hello'. node2 := renderer node on: 'world'. edge := renderer edge from: node1 to: node2. Here you are explicitly remembering the node references and you are passing them to the edge creation. When you have a handful of these nodes, this can fit nicely what you want. As soon as you have a multitude of nodes, it is no longer easy to make the mapping, because you will have to manage the references manually. In MOViewRenderer we have API that helps you lookup and match nodes only in terms of your model (basically you never get to manipulate nodes or edges, unless you really really want to). The idea behind this is that you should only think in terms of your model and never get to manipulate the internals of Mondrian. This works in many cases, but you do not have such a convenient way to work with explicit nodes and edges like above. So, maybe a good thing would be to add finally some edgeFromNode:toNode: that provides a creation of a node without any node lookup. So, you could have: view := MOViewRenderer new. node1 := view node: 'hello'. node2 := view node: 'world'. edge := view edgeFromNode: node1 toNode: node2. What do you think? Cheers, Doru On 20 Jun 2011, at 15:03, Alexandre Bergel wrote: > The package MondrianNew in the squeaksource repository of Mondrian contains a bunch of classes we quickly defined: > MORenderer>> > addEdge: > addEdges: > addNode: > addNodes: > > MOEdgeFactory>> > from:to: > > MONodeFactory>> > on: > > Cheers, > Alexandre -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

14 years

2
2
0 0

[ANN] humane-assessment.com

by Tudor Girba

Hi, I am happy to announce the new home for humane assessment: http://humane-assessment.com Humane assessment is a new software engineering method for making the assessment of software systems practical and manageable. This is made possible by the Moose analysis platform. The core idea is quite simple: build custom analysis tools to analyze the contextual complexity of your software systems so that you can make better decisions. By decisions I mean anything that has to do with the system: it can be technical (such as, is this concept well encapsulated?, or is my component used the right way?), or it can be broad and strategic (such as, should I refactor my system?). To make it practical we need to be able to craft tools (sometimes complex tools) fast. This is made feasible by Moose, and in turn, Moose achieves this because of Smalltalk. The method also covers process and organization-related problems. If you wish, humane assessment is the coat that can place Moose and Smalltalk within any development team. If you want to promote Smalltalk, perhaps you might want to use this path. I would be happy to provide more information, support and even materials. Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

14 years

2
1
0 0

display matching rule in petit parser

by Norbert Hartl

In the petit ui I can easily see the output of a successful parse as result node tree. Is there a way to show the rules that matched a particular node along with the result? thanks, Norbert

14 years

2
6
0 0

verveinej build failed

by Tudor Girba

Hi Nicolas, The latest VerveineJ build failed: http://ci.moosetechnology.org/job/verveinej/70/ :) Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

14 years

2
1
0 0

Customizable EyeSee chart

by Andre Hora

Hello, I created a simple application using EyeSee, Customizable EyeSee chart, where you can set the metrics you want to see (similar to Customizable System Complexity) in a chart. The x axis shows individual entities (a FAMIXClass, a FAMIXPakage, ...) or a group (MooseGroup) according to the granularity you set. The y axis shows the values of the metrics. I you want to try, run the script below and then right-click in a MooseGroup -> Visualize -> Customizable EyeSee chart. Gofer new squeaksource: 'Moose'; package: 'Moose-EyeSeeCharts'; load. todo: - Allow multiple charts - Interaction. regards, -- Andre Hora

14 years

4
10
0 0

Issue 652 in moose-technology: compositeDiagram bugs

by moose-technology＠googlecode.com

Status: New Owner: andreho...(a)gmail.com Labels: Type-Defect Priority-Medium Component-EyeSee New issue 652 by andreho...(a)gmail.com: compositeDiagram bugs http://code.google.com/p/moose-technology/issues/detail?id=652 Trying to use compositeDiagram two problems were found: - ESAbstractDiagram>>elements is working in a wrong way. It should return the elements of the composed diagrams; - interaction over ESAbstractDiagram contains some bugs. The selection is not working (maybe) due the problem above.

14 years

1
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev