Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Tudor Girba

Hi Martin, It looks like there is a problem with the ConfigurationOfFuelMooseExtension in that the version 1.2 references FuelMooseExtension-MartinDias.10, which does not exist on squeaksource. It could be that the problem is due to the squeaksource problem. Could you check and possibly republish the version? Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

14 years, 1 month

Trying to establish a configuration

by Johan Fabry

Hi all, I have been tinkering a bit to try and get a way in which a specific moose version can be loaded from source, based on a) a virgin Pharo image and b) a moose release (one-click) image. The idea is that this could be done for each moose release. I am stuck, here is what I got so far. Maybe somebody can give me pointers how to continue. In image a) do the following in a workspace: |packversions| packversions := MCPackage allInstances collect: [:pack | pack workingCopy ancestry ancestorString]. Transcript clear. packversions do: [:pack | Transcript show: pack,' ']. Copy the contents of the Transcript INCLUDING THE LAST SPACE! In image b) do the following in a workspace, pasting where indicated. | opstr oldp newp diff| opstr := ReadStream on: '<PASTE HERE>'. oldp := OrderedCollection new. [opstr atEnd] whileFalse: [oldp add: (opstr upTo: Character space)]. newp := MCPackage allInstances collect: [:pack | pack workingCopy ]. diff := newp select: [:cand | (oldp includes: cand ancestry ancestorString) not]. diff inspect. diff now contains all the packages of b) that are not in a). Now we need to know the order in which they are to be loaded, to avoid dependency issues. I thought that the requiredPackages of each MCPackage would enable me to order, but -o surprise- none of the packages have these set. Sooo ... this info must be in Metacello. Hence the question: given a specific MCPackage, how can I obtain the list of required packages from Metacello? I dont care if it is slow BTW, building this list will only be done sporadically. Thanks in advance ... -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

14 years, 1 month

Refactoring in the rendering engine of Mondrian

by Alexandre Bergel

Hi! Together with Santiago and Doru we have been working on a necessary refactoring of the Mondrian rendering engine. This is a prerequisite to make Mondrian generate HTML5. I would like you to shout if you notice a slowdown with a large visualization (e.g., DSM, PackageBlueprint). I used it with large Hapao visualizations, but I was happy about the result. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 1 month

Mondrian refactorization

by Santiago Vidal

---------- Forwarded message ---------- From: Tudor Girba <tudor(a)tudorgirba.com> Date: 2011/5/18 Subject: Re: Mondrian To: Santiago Vidal <santiago.a.vidal(a)gmail.com> Cc: Alexandre Bergel <alexandre.bergel(a)me.com>, Claudia Marcos < marcos.claudia(a)gmail.com> Hi, Please let's move this discussion to the moose-dev mailing list. It would be a good documentation of Mondrian. You can register here: https://www.iam.unibe.ch/mailman/listinfo/moose-dev and send the mail here: moose-dev(a)iam.unibe.ch Cheers, Doru On 18 May 2011, at 14:55, Santiago Vidal wrote: > Hi, > I indented the methods and removed the 'MO' class prefix from each visit method. > I'm not sure about the best way to avoid the creation of a new visitor each time a shape is displayed. Should I save a visitor for each MOGraphElement? The canvas changes each time that a shape is displayed? Can you please tell me what is the cache that I have to moved to the visitor? > > On another topic with Claudia we are advising the final work of two student in which we are going to use Moose. Specifically, we will use Moose to compare different versions of an open source system with the goal of identify differences in its modules. I would like to use Moose in my phd thesis too, so this a first approach. > > Cheers > Santiago > > > 2011/5/17 Tudor Girba <tudor(a)tudorgirba.com> > Thanks. It works now: > http://ci.moosetechnology.org/job/mondrian-latest-dev-on-pharo-1.2/213/ > > Cheers, > Doru > > > On 17 May 2011, at 22:32, Alexandre Bergel wrote: > > > Can you please lunch the build ? > > > > Cheers, > > Alexandre > > > > > > On 17 May 2011, at 16:03, Tudor Girba wrote: > > > >> Hi again, > >> > >> The build based on the 'default' configuration still says that something is missing: > >> http://ci.moosetechnology.org/job/mondrian-latest-dev-on-pharo-1.2/ > >> > >> Cheers, > >> Doru > >> > >> > >> On 17 May 2011, at 21:43, Tudor Girba wrote: > >> > >>> Hi, > >>> > >>> > >>> On 17 May 2011, at 21:37, Alexandre Bergel wrote: > >>> > >>>> Hi Santiago, > >>>> > >>>> I updated the configuration. Your new package is now in. > >>>> The Jenkins should stop complaining by now :-) > >>> > >>> I started a build of Mondrian to check. > >>> > >>>> Each time a node is displayed, a new visitor is created. I do not think this is necessary. > >>> > >>> This is actually not wanted at all because the renderer might have some state later one. > >>> > >>> Cheers, > >>> Doru > >>> > >>>> Would you mind to indent the code with a tabulation at each line? For example: > >>>> -=-=-=-=-=-=-=-=-= > >>>> acceptVisitor: aVisitor > >>>> ^aVisitor visitMODashedLineShape: self. > >>>> -=-=-=-=-=-=-=-=-= > >>>> > >>>> -=-=-=-=-=-=-=-=-= > >>>> acceptVisitor: aVisitor > >>>> ^ aVisitor visitMODashedLineShape: self. > >>>> -=-=-=-=-=-=-=-=-= > >>>> > >>>> Can you remove the 'MO' class prefix from each visit method? (e.g., visitMODashedLineShape: -> visitDashedLineShape:) > >>>> I will do some benchmark to see if we are slower, but we should not be actually. > >>>> > >>>> Cheers, > >>>> Alexandre > >>>> > >>>> > >>>> -- Ing. Santiago A. Vidal ISISTAN Research Institute UNICEN University Paraje Arroyo Seco Campus Universitario (B7001BBO) Tandil, Bs. As. - Argentina Phone: 54 2293 439840 Ext. 42 Fax: 54 2293 439681 Email: svidal(a)exa.unicen.edu.ar http://www.exa.unicen.edu.ar/~svidal

14 years, 1 month

Issue 629 in moose-technology: VerveineJ should not export implicit variables without parentBehaviouralEntity

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 629 by tudor.gi...(a)gmail.com: VerveineJ should not export implicit variables without parentBehaviouralEntity http://code.google.com/p/moose-technology/issues/detail?id=629 Some implicit variables are exported without a parentBehaviouralEntity. To reproduce it: - download ArgoUML 0.28.1: http://argouml-downloads.tigris.org/argouml-0.28.1/ - there are several instances (about 5-6 out of 2000+) of implicit variables without parrentBehaviouralEntity

14 years, 1 month

moose and humane assessment on a5 paper

by Tudor Girba

Hi, Perhaps this can be of interest for you: http://www.tudorgirba.com/blog/humane-assessment-moose-a5 Comments are welcome :) Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

14 years, 1 month

Re: Jenkins build is still unstable: moose-latest-dev #380

by Tudor Girba

Hi, It looks like Mondrian still has a red test. Cheers, Doru On 17 May 2011, at 23:27, admin(a)moosetechnology.org wrote: > See <http://hudson.moosetechnology.org/job/moose-latest-dev/380/> > > -- www.tudorgirba.com "We can create beautiful models in a vacuum. But, to get them effective we have to deal with the inconvenience of reality."

14 years, 1 month

moose wikipedia page

by Tudor Girba

Hi, I added a Wikipedia page for Moose: http://en.wikipedia.org/wiki/Moose_(analysis) Feel free to enhance it. Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

14 years, 1 month

SourceLanguage Object

by Usman Bhatti

I am trying to set the sourcelanguage object of the FamixRepository. So, I create my own subclass of the Famix.SourceLanguage, on the lines of java as follows: [FamePackage("FAMIX")] [FameDescription("CSharpSourceLanguage")] class CSharpSourceLanguage : SourceLanguage { //couldn't find anymore info to set for the class in VerveineJ } And I add it to the famixrepository. This how it appears in the mse file: (FAMIX.SourceLanguage (id: 30)) However, moose does only provide information that its a SourceLanguage object, but does know which source language was used. My questions are: 1. What are the parameters of the SourceLanguage that we should set. I do not see any setName() method? 2. What information does Moose require when parsing Famix.SourceLanguage object? thanx in advance, Usman

14 years, 1 month

[ANN] Moose Suite 4.4

by Tudor Girba

We are happy to announce the Moose Suite version 4.4: http://moosetechnology.org/download What is new: • New EyeSee engine for scripting visual charts • New Kumpel importer for SVN repositories • New Metanool engine for supporting dynamic annotations of models • Simplified look and feel • Improved VerveineJ compatibility for Java parsing • Improved FAMIX support for Java systems • Improved support for complex shapes in Mondrian • Improved RPackage engine support for the Smalltalk importer A list of issues addressed in this release can be found at: http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… Have fun, The Moose Team http://moosetechnology.org

14 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev