Moose-dev June 2011

moose-dev@list.inf.unibe.ch

32 participants
176 discussions

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

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

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

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

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

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

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

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

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

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

← Newer
1
...
9
10
11
12
13
14
15
...
18
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2011