Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Serge Stinckwich

For some function, the Roassal Grapher is not really good. Try this for example: b := RTGrapher new. b extent: 600 @ 200. ds := RTDataSet new. ds dotShape ellipse size: 0. ds points: (-2.0 to: 10.0 by: 0.001). ds connectColor: Color red. ds x: #yourself. ds y: [ :x | (x exp) sin ]. b add: ds. b axisXWithNumberOfTicks: 3. b axisYWithNumberOfTicks: 4. b build. b view This is well known problem when someone use n-equally space joint in a grapher. There is some explanation here: http://maurizzzio.github.io/function-plot/ The solution need to implement an interval arithmetic library apparently. Nicolas implement an arbitrary-precision float library available in SciSmalltalk, but I not sure this is enough for a grapher. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

10 years

[ANN] Edge bundles

by Alexandre Bergel

Dear All, Here is a preview of what we will demonstrate at ESUG. Best is to see it live try this: -=-=-=-=-=-=-=-=-=-=-=-= b := RTBundleBuilder new. b from: {TRObject. TRTest} using: #subclasses. b edges shape line color: Color black. b bezier color: (Color blue alpha: 0.5). b useBezierlineWith: #dependentClasses. b build. lb := RTLegendBuilder new. lb view: b view; right. lb addText: 'RTBundleBuilder: TRObject and TRTest subclasses'. lb addColor: Color black text: 'Hierarchy'. lb addColor: (Color r: 0 g: 120 b: 0 range: 255) text: 'Dependent classes'. lb addColor: Color red text: 'Senders'. lb build. b view -=-=-=-=-=-=-=-=-=-=-=-= A very short video is available on: https://vimeo.com/131891902 <https://vimeo.com/131891902> Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years

moose with fuel

by Usman Bhatti

Hi, With Vincent, we are reviving Fuel export/import for Moose. Name: ConfigurationOfFuelMooseExtension-usmanbhatti.28 Author: usmanbhatti Time: 22 May 2015, 1:55:11.568166 pm UUID: 297195bb-ea59-4cb5-8ea4-ba1195b39842 Ancestors: ConfigurationOfFuelMooseExtension-MarianoMartinezPeck.27 Add new baseline to work on pharo 3.0 and symbolic dev version usman & vincent

10 years

the importance of your story

by Tudor Girba

Hi, I gave last week a talk at NDC Oslo on "Don't demo facts. Demo stories!". While the talk is less technical, I did exemplified the message by demoing Spotter in comparison with the search support from Eclipse. There are several things I would like to emphasize. I compared our solution with an "industry standard" one. We often think our system as being niche and perhaps not mature enough. We need to change that perception about our work. We build state of the art. One thing that I did not mention explicitly in the talk is the size of the implementation. The Spotter implementation is 3500 lines of code -- and that it is so large because it currently comes with its own widgets. Furthermore, the extensions average 8 lines per custom processor (including the method header and the pragma). This is orders of magnitude smaller than what is typically out there, and it is precisely the reason why we can compete even if we are fewer. But, to get out there and compete we have to set that high goal for ourselves. For example, with GT we do not want to compete. We want to outcompete. So can you. While details are important, high goals require us to get away from those details. Only polishing details will tend to limit you to incremental improvements. We need to jump from time to time. But, these jumps are hard. On the one hand, it is hard to find the right jump and convince people to jump with you. On the other hand, they are hard to predict. For example, Spotter would have not been predictable one year ago. Yet, dry goals are not enough to keep us going. We need stories that make us dream. And the beauty is that Pharo breaths such a story. We should not limit ourselves to that story only. For example, with GT we want to reinvent the developer experience by making the developer be able to mold visual tools to her context because that is the only effective way to build sustainable systems. This little point of view will turn the IDE upside down, and this is only possible in a system like Pharo. Choose your high goal and tell its story through the system that you build. And remember that Pharo already offers a beautiful story to start from. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years

Roassal vertical bar diagram (with multiple sets)

by Yuriy Tymchuk

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

10 years

[ANN] Sonar importer

by Blondeau Vincent

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.

10 years

MessageNotUnderstood: RTView>>edgesDo: and tagged wiki-like workspaces on ws.stfx.ed

by Offray Vladimir Luna Cárdenas

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

10 years

VerveineJ problem

by Alexandre Bergel

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

10 years

Re: [Pharo-dev] Re: Searching for a Roassal2 version

by Yuriy Tymchuk

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

10 years

Roassal bug?

by Nicolas Anquetil

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

10 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev