Moose-dev September 2014

moose-dev@list.inf.unibe.ch

42 participants
134 discussions

roassal2 popup
by Tudor Girba 01 Oct '14

01 Oct '14

Hi, I took the liberty of changing a bit the appearance of the text popup: made the text with white, and smaller; made the border less prominent. This is particularly needed in more complicated visualizations. Take a look: https://dl.dropboxusercontent.com/u/18323746/Tmp/roassal2-popup-before.png https://dl.dropboxusercontent.com/u/18323746/Tmp/roassal2-popup-after.png I hope that is fine. What do you think? [image: Inline image 3] Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

2 2

GTInspector + Fuel
by Yuriy Tymchuk 30 Sep '14

30 Sep '14

Hi, sorry if this is a known thing, but I’ve just notices this and it made my day. So in GTInspector you can browse filesystem, but when you select a fuel file, you can press a "plus” button in top right corner, and it materialises the object. Amazing. Uko

2 1

My wish for the Glamourous crew
by Alexandre Bergel 30 Sep '14

30 Sep '14

Since you are working on a new code browser. Please please please, it would be fantastic to see the definition of the setUp method when I create a new test method. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

Build failed in Jenkins: moose-5.0 #2535
by admin＠moosetechnology.org 30 Sep '14

30 Sep '14

1 0

Version for PetitParser for backward comptability
by Usman Bhatti 30 Sep '14

30 Sep '14

Hi all, Recently, there have been changes in PetitParser related to support for island grammar and parsing context which requires some modifications in the tools using PetitParser. Not all tools can be adapted immediately to use the new version. Hence, I have created a new version of PetitParser that loads the packages prior to these changes for backward compatibility. Name: ConfigurationOfPetitParser-usmanbhatti.49 Author: usmanbhatti Time: 28 September 2014, 8:58:00.540857 pm UUID: 54877ca2-77b0-4c5e-937d-5124dd76b075 Ancestors: ConfigurationOfPetitParser-JanKurs.48 adding a baseline and a version that loads packages before changes made to petitparser related to parsing context and island grammar. regards, usman

4 10

alex's demo at vissoft
by Tudor Girba 30 Sep '14

30 Sep '14

Hi, It seems that Alex's demo at VISSOFT has done very well :). Take a look at the tweets (feel free to retweet). Good job, Alex! Live analysis is hot, and right now, we are on top of it. Let's keep it up. [image: Inline image 1] Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 3

SmallDude-Core-NicolasAnquetil.46
by Nicolas Anquetil 30 Sep '14

30 Sep '14

Hi all, we did some work on Dude. One thing that was bothering us was that it cleaned the source code (remove comments, '{', ...), but left empty lines behind that interfered with the detection. To correct that: - DudeSourceCodeLine now keeps the lineno of its line in the original source code - empty lines do not generate any DudeSourceCodeLine - DudeSourceCodeFragment keeps beginLine and endline in terms of real line numbers in the source code - DudeSourceCodeFragment also has to keep the length of the clone fragment as the number of non empty lines (previously it would be computed from beginLine and endline) - and we had to refactor the code in various places to deal with these changes Overall, a rather big commit, but the tests (new and old) are green nicolas Name: SmallDude-Core-NicolasAnquetil.46 Author: NicolasAnquetil Time: 30 September 2014, 1:42:10.634399 pm UUID: f5004983-82f1-4649-8e8e-efe22776cb35 Ancestors: SmallDude-Core-TudorGirba.45 changed Dude so that empty lines are discarded when computing clones

1 0

Re: Extracting CK+OO metrics from .mse file by Moose
by Serge Stinckwich 29 Sep '14

29 Sep '14

On Mon, Sep 29, 2014 at 1:46 PM, Cường Phạm <cuongpham92(a)gmail.com> wrote: > Dear Mr Serge Stinckwich, > > It is me again, sorry for disturbing. I have asked Mai Anh and Fabrice about > this issue, but unfortunately they do not work in this specific topic. May I > ask you about the way I export CK+OO metrics from MOOSE? > > As you suggested, I use MOOSE 5.0 and successfully imported mse file into > MOOSE. Now I do see these metrics in section "Properties" of tab "All > modelclasses", but I could not find any button to export this to some kind > of document such as xml or html file. Do I have to write any code to extract > them out? There is no generic way to dump all the information of a model. MOOSE is a platform to analyse and visualize your model depending of what you want to do. Normally people who want to analyze some properties of their system, write a specific script in Pharo in order to visit their model in an appropriate way. For example, if you want to generate a collection with the number of methods (WMC metrics) for each classes of your model, you can do: self allClasses collect: [:eachClass | eachClass numberOfMethods]. If you want to generate a result html file, you can do the following: FileLocator desktop / 'result.html' writeStreamDo: [:out| out << '<html><head><title>Results</title></head><body><table border=1>'. out << '<tr bgcolor=silver>'; << '<th>Class</th><th>number of methods</th></tr>'. self allClasses collect: [ :eachClass| out << '<tr>'; << '<th>'; << eachClass asString; << '</th>'; << '<th>' ; << eachClass numberOfMethods; << '</th>' ; << '</tr>' ]. out << '</table></body></html>'. ] For exemple, with a model with all the Collection classes, I will obtain the attached html table. After that you need to adapt the html dump to your needs. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

1 0

Vissoft, anyone?
by Alexandre Bergel 29 Sep '14

29 Sep '14

Hi! Any of you is at vissoft? I think Roberto is... Alexandre

1 0

Re: JS2Moose
by Alexandre Bergel 29 Sep '14

29 Sep '14

Hi! I will try to answer you more in detail ASAP. But you are missing the notion of prototype and attributes. A prototype may contains attributes and functions. If things are missing in Famix, the. We can easily extend it. It is made to be expandable. I reply to the moose mailing list since many expert in modeling will we this email. Alexandre > Le 26-09-2014 à 19:18, Leonardo Silva <leonardo.humberto(a)gmail.com> a écrit : > > Hi Alexandre, > > I've checked the JS2Moose project. > > Suppose the following JS code: > > function circle (radius) { > this.radius = radius; > } > circle.prototype.getArea = function () { > return (this.radius * this.radius * 3.14); > } > > > For this code, JS2Moose generated the following MSE: > > ( > (FAMIX.Function (id: 4) > (name 'window') > (staticUseStrictEnabled true) > (numberOfLinesOfCode 1) > (numberOfStatements 1)) > > (FAMIX.Function (id: 5) > (name 'circle') > (parentScope (ref: 4)) > (staticUseStrictEnabled true) > (numberOfLinesOfCode 52) > (numberOfStatements 1)) > > (FAMIX.Function (id: 6) > (name '$5_27') > (parentScope (ref: 4)) > (staticUseStrictEnabled true) > (numberOfLinesOfCode 60) > (numberOfStatements 1)) > ) > > So, I am not sure this MSE has all the data we need. For example: > > - "radius" is not described in the MSE > - "getArea" in the MSE is represented using another name, "$5_27" > - there is not association between getArea (id: 6) and circle (id: 5) > > Of course, maybe we are doing something wrong, but it seems the MSE > does not include many important nodes that are available in a JSON file > generated by Esprima. > > We can also have a skype meeting to better clarify this question. > > Leonardo

2 3

← Newer
1
2
3
4
5
6
7
8
...
14
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 September 2014