Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

Roassal -- where is GTExampleFinder
by Peter Uhnák 19 Sep '15

19 Sep '15

When loading latest Roassal the loader was complaining about missing GTExampleFinder. Where can I find that? Peter

3 4

GTDebugger create method
by Peter Uhnák 17 Sep '15

17 Sep '15

Hi, does GTDebugger support creation of new methods? Also not having tooltips on the buttons isn't entirely helpful. Thanks, Peter

2 1

MooseModel source language
by Usman Bhatti 16 Sep '15

16 Sep '15

Hi, I propose to change this: MoosModel>>sourceLanguage: aSymbol ^sourceLanguage := aSymbol by: MoosModel>>sourceLanguage: aSourceLanguage sourceLanguage := aSourceLanguage. sourceLanguage mooseModel: self So, that we don't have to remember to add manually the source language to the model. Is it ok to do this change? usman

8 16

Chapter on Moose
by Alexandre Bergel 15 Sep '15

15 Sep '15

Hi! I have written the following: https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Moose/0308-… <https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Moose/0308-…> Comments are welcome! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

VerveineJ problem?
by Alexandre Bergel 15 Sep '15

15 Sep '15

Hi! I am getting an exception with VerveineJ. No idea why. VerveineJ processing file: ./agilevisualization/example/HelloWorld.java *** VerveineJ visitor got exception: 'java.lang.NullPointerException' while processing file: ./agilevisualization/example/HelloWorld.java The code is simply: I have a .mse file that is created however. Any what’s going on? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

MooseQuery performance issues
by Blondeau Vincent 15 Sep '15

15 Sep '15

Hi, I wanted to use MooseQuery to get some call graphs in a model. I have 4720 graphs to compute, I start from a class and I want all the incoming invocations at class level recursively. I used the default queryAllIncomingInvocations of MooseChef and the one of MooseQuery. It takes 1min20 with MooseChef. With MooseQuery, it takes 5 mins to do ~500 graphs... so 50 mins to calculate everything (I didn't try ;) ).. Maybe some performance improvement is needed? Cheers, Vincent ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

2 5

distinct colors
by Alexandre Bergel 14 Sep '15

14 Sep '15

Hi! Just to let you know. I have slightly improved the normalizer. You can now send #distinctColorUsing: aBlockOrSymbol Consider the following example: b := RTMondrian new. b shape circle. b nodes: Collection withAllSubclasses. b edges connectFrom: #superclass. b layout tree. b normalizer normalizeSize: #numberOfMethods; distinctColorUsing: #package. b This gives to each class a color depending on its package. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Survey] QualityAssistant experience mini-survey
by Yuriy Tymchuk 14 Sep '15

14 Sep '15

Dear Pharoers, I kindly ask you to participate in the QualityAssistant mini-survey: http://rio.inf.usi.ch/survey/index.php/818331 <http://rio.inf.usi.ch/survey/index.php/818331>. It will take only a few minutes of your time (or less), and will give us a better understanding of how QualityAssistant is currently used and how to improve it. Cheers! Yuriy

3 3

Pillar 2.0.0: Introduction of PetitPillar
by Ferlicot D. Cyril 14 Sep '15

14 Sep '15

Hi everyone! Yes, a new version of Pillar, again! With this version we removed the old parser of Pillar to introduce PetitPillar base on PetitParser. This parser is slower than the previous one but we will be able to improve his speed. We will also be able to improve Pillar at the parser level, which was impossible before. So we will be able to remove some hacks and improve the experience of the users. If you are good in parser and you want to contribute to his improvement, feel free to help, we have a lot of tests to help. This is my first parser so I am sure it have a lot of rooms for improvement. -- Cheers Cyril

3 2

Metacello and suffixes in package names
by Usman Bhatti 14 Sep '15

14 Sep '15

Hi, It seems that Metacello does not consider PackageName-xyz and PacakgeName-BranchName-xyz as the same package. I suspect it because when I look at the packages loaded by two different configurations with and without branch names as package name suffixes are not the same. Could someone knowing the internals of Metacello confirm it? So, here is a log of Metacello of the loadDirective for ConfigOfGlamour with and without packages with branch names. I have truncated the output to highlight important parts of the log. ----------- Metacello log follows ---------------------- Without branching (Rubric and Glamour-Morphic-Renderer loaded only once): linear load : atomic load : 3.3.0 [ConfigurationOfGlamour] linear load : 3.1.3.Moose51 [ConfigurationOfGlamourCore] --------------------List of Packages---------------- atomic load : 1.2.14.Moose51 [ConfigurationOfRubric] load : Rubric-AndreiChis.207 load : Glamour-Morphic-Renderer-AndreiChis.324 --------------------List of Packages---------------- linear load : 1.13 [ConfigurationOfRoassal2] linear load : 3.1.4 [ConfigurationOfGlamourCore] --------------------List of Packages---------------- With branching (old versions overwrites the fixes): linear load : atomic load : 3.3.0 [ConfigurationOfGlamour] linear load : 3.1.3.Moose51 [ConfigurationOfGlamourCore] --------------------List of Packages---------------- atomic load : 1.2.14.Moose51 [ConfigurationOfRubric] load : Rubric-Moose51-usmanbhatti.207 load : Glamour-Morphic-Renderer-Moose51-usmanbhatti.324 --------------------List of Packages---------------- linear load : 1.13 [ConfigurationOfRoassal2] linear load : 3.1.4 [ConfigurationOfGlamourCore] atomic load : 1.2.15 [ConfigurationOfRubric] load : Rubric-AlainPlantec.206 load : Glamour-Morphic-Renderer-AndreiChis.321 --------------------List of Packages---------------- --------------- What it actually changes is packages with branch name are overwritten with their predecessors and hence fixes are not correctly included in the resulting image. It seems that ensuring correct loading in the presence of branched packages requires no other configuration is loading previous versions of the branched packages.

4 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev