Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

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.

13 years, 10 months

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

13 years, 10 months

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

13 years, 10 months

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

13 years, 10 months

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 10 months

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 ?

13 years, 10 months

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." > > >

13 years, 10 months

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.

13 years, 10 months

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

13 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev