Moose-dev June 2015

moose-dev@list.inf.unibe.ch

33 participants
60 discussions

Roassal vertical bar diagram (with multiple sets)
by Yuriy Tymchuk 25 Jun '15

25 Jun '15

Hi, I need to build a bar diagram with multiple sets. I need to have a vertical representation (bars are horizontal), because I have a longish labels for each step. In Roassal examples I’ve seen RTDoubleBarBuilder, but it appears to be obsolete. What should I use now. Also please forgive me if there is a known solution, and tell me where to look for them. Because now the main place where I look are Roassal examples, and I can’t find anything suitable. Uko

2 4

[ANN] Sonar importer
by Blondeau Vincent 25 Jun '15

25 Jun '15

Hi, I would like to announce that I developed a Sonar importer to get sonar data into a Moose model. It imports the list of metrics and projects available in the Sonar repository. On demand, it imports chosen metrics for all the projects. I let you see the tests and documentation to check the behavior of this importer. The configuration is on the Pharo catalog<http://catalog.pharo.org/catalog>, so it is very easy to load it (else the repo is here<http://smalltalkhub.com/#!/~VincentBlondeau/Sonar>). The importer is based on the public Sonar REST API Version 3.7.2<http://docs.sonarqube.org/display/SONARQUBE43/Web+Service+API>, but should work with recent ones. Don't hesitate to contribute if you want to add new features, the project is in public access! 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.

3 2

MessageNotUnderstood: RTView>>edgesDo: and tagged wiki-like workspaces on ws.stfx.ed
by Offray Vladimir Luna Cárdenas 24 Jun '15

24 Jun '15

Hi all, Trying to do the example on [1] I got the MNU error on this mail subject. Surely this is because there is an alternative way was developed while the Roassal interface are getting stable. So which is the new way? A related thing is that ws.stfx.eu has become a really valuable resource in sharing code easily in our Saturday workshops and I was wondering if there is a way to use it to put a kind of permalink to the last version of a code snipped. Imagine kind of a wiki like feature for workspaces where I can commit to an already published workspace and replace the code for a recent version, without losing the history. Also I imagine the possibility of using custom url (ala bit.ly) and tags for searching related workspaces. Could be this developed easily? Can we help as newbies with this? If this is possible, I imagine facebook page of object profile with code, but pointing to the permalink workspace in ws.stfx.eu, so if the code in facebook is broken, It can be fixed in a community fashion, even for those of us which don't have/want a facebook account. [1] https://www.facebook.com/ObjectProfile/photos/pb.340543479365589.-220752000… Cheers, Offray

2 5

VerveineJ problem
by Alexandre Bergel 23 Jun '15

23 Jun '15

Hi! I am getting an exception when running VerveineJ. /tmp/src> /Users/alexandrebergel/Dropbox/Document/verveinej/verveinej.sh src/ Exception in thread "main" java.lang.IllegalStateException: invalid environment settings at org.eclipse.jdt.core.dom.ASTParser.getClasspath(ASTParser.java:256) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:988) at eu.synectique.verveine.extractor.java.VerveineJParser.parse(Unknown Source) at eu.synectique.verveine.extractor.java.VerveineJParser.main(Unknown Source) The src folder contains one unique file, Label.java, attached here. We run these example to check whether the .MSE file indicates that the class Label depends on AssociatedField. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 4

Re: [Pharo-dev] Re: Searching for a Roassal2 version
by Yuriy Tymchuk 23 Jun '15

23 Jun '15

IMHO project’s version should be orthogonal to pharo versions as much as possible. Uko > On 23 Jun 2015, at 15:49, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 23-06-15 15:13, Esteban Lorenzano wrote: > >> depending on #stable is #wrong! > > The one situation where depending on #stable is ok is > where we talk about a Pharo 4 version where > new development is only on Pharo 5. Stable is then > only a moving target on Pharo 5, not on 4. > > Stephan > > >

2 1

Roassal bug?
by Nicolas Anquetil 23 Jun '15

23 Jun '15

While porting Telescope to a newer version of Roassal, we might have found some bugs, methods that do not exist anymore and are still called: RTShape>>+ calls 'with:with:' RTAbstractLine>>+ calls 'with:with:' RTShapedObject>>addShape: calls 'with:with:' RTSVGVisitor>>visitCompositeShape: calls 'shape1' and 'shape2' RTSVGVisitor2>>visitCompositeShape: calls 'shape1' and 'shape2' nicolas and vincent

5 15

Searching for a Roassal2 version
by Yuriy Tymchuk 23 Jun '15

23 Jun '15

Hi, I want to depend on a version of Roassal2. Should I depend on 1.11? Because 1.12 and 1.13 have blessing: “broken”. o_O Uko

8 26

UML in Moose
by Natalia Tymchuk 22 Jun '15

22 Jun '15

Hi. I want to build a UML class diagram in moose. Can anybody tell me how to do it? Thanks, Best regards, Natalia

2 2

Roassal configuration
by Stephan Eggermont 20 Jun '15

20 Jun '15

There are now two versions 40 in the repo. The one I updated is copied to the metarepos, so the problem is not yet fixed. I only changed the catalog methods, they need to be at the class side. I don't know if you saw this post in pharo-dev? On 19-06-15 07:11, Alejandro Infante wrote: > Hi, > I did that because when using: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; > configurationOf: 'Roassal2'; > loadStable > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > It was installing 1.52 even though the stable version of Roassal was 1.12. > Instead if I used: > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Gofer new smalltalkhubUser: 'ObjectProfile' > project: 'Roassal2'; > package: 'ConfigurationOfRoassal2'; > load. > ((Smalltalk at: #ConfigurationOfRoassal2) project version: #stable) load > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > I was getting the right version (1.12). Gofer>>loadStable does not use the ConfigurationOfRoassal2 class>>loadStable (which is undefined, but many configurations define as self project load: #stable but loadVersion: #stable, which uses the latest version marked #stable. So yes, that is something you'd want to fix in place. And warn about on the mailing list. In this version 1.12 then we see that Roassal is tightly coupled to an old version of GlamourCore. So either ConfigurationOfRoassal2 needs to add a new #stable version every time GlamourCore #stable for Pharo 4 is updated, or it should depend on GlamourCore #stable. And ConfigurationOfGlamourCore has actually the same problem, as #stable currently depends on an old version of Rubric. So that should have been one or two versions more. And please note that this is for the released Pharo 4, where we are only supposed to backport important fixes. I strongly suggest to make ConfigurationOfGlamourCore #stable depend on ConfigurationOfRubric #stable, and to make ConfigurationOfRoassal2 depend on ConfigurationOfGlamourCore #stable. B.t.w. I'm not quite sure why there is an old ConfigurationOfGlamourCore in Pharo5. Depending on #stable instead of #release1 or so works out ok here as long there is not supposed to be a new release for Pharo 4. Stephan

1 0

What's wrong with the moose build?
by Alexandre Bergel 19 Jun '15

19 Jun '15

Hi! The build is red. It would be great to fix this. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev June 2015