Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Re: PetitParser: Different behavior when a parsing is finished

by stephan

I've updated the configuration to use #development of PetitParser. Then I run into the problem that PetitSmalltalk is broken. Can the same version of PetitSmalltalk work on both Pharo3 & 4? It looks like the compiler API changed. Stephan

10 years, 1 month

RTLegendBuilder Questions

by Sean P. DeNigris

I'm using RTLegendBuilder to compare some insurance options. Cool! I was quickly able to cobble together a reasonable legend and align it to any side of my graph :) <http://forum.world.st/file/n4813331/Screenshot_2015-03-19_15.png> As I tweaked, though, I noticed a few things: - Luckily, my domain object's printString is what I want for the label of the legend item. Thus I am able to pass it to #addColor:text: (which I took a while to figure out can take any object for "text:"). I want to pass this object, and not just the label text I want, because that would break the GT Inspector flow. I think there is a missing dimension here for when we want the item and the label to be different. In fact, drop lists in Pharo used to work like this. I think the pattern is carried over from less dynamic or OO languages. In Magritte3, I added #display: to field descriptions of the form [ :domainObject | stringFormToUse ] - #addColoredText:color: and #addColor:text: - do we really need both? I know it's considered best practice to implement: simple: simple:intermediate: simple:intermediate:complicated: style APIs, but I strongly prefer one method that takes a domain object which already has all this info, even at the expensive of a pair of parentheses. OT: Text builders seem inherently restrictive because they always seem to insert a layer between the full power of the underlying objects and the part that's been translated to the builders. I sense that it would be a game changer (and not too hard) to hook the underlying objects together visually a la Lively Kernel instead of implementing a visual or text builder. In fact, I think that's what e.g. Morphic almost-already-is. It was even alluded to in a few papers as right on the horizon. But it's on the Dreams list for now. Anyway, thanks for Roassal. This is fun! ----- Cheers, Sean -- View this message in context: http://forum.world.st/RTLegendBuilder-Questions-tp4813331.html Sent from the Moose mailing list archive at Nabble.com.

10 years, 1 month

The Grapher charting engine

by stepharo

Alex Roassal is really cool now I have one question why we cannot say serie1pointsAndVariations :- given series2pointsAndVariations := given RGrapher new axisX; axisY; seriesWithDeviation: {serie1pointsAndVariations . serie2pointsAndVariations}; maxXAxis: 100; My point is why the line connection is not hidden from the user. I think that roassal is a cool scripting engine but it got ***trapped*** there. A primary user wants to have abstractions Then in a second time he wants to open the trunk and script its own. also why don't you have nice default dec := RTDevVarDecorator new. dec moveBehind; desviation: 0.5; color: (c alpha: 0.3); points: pts. => dec := RTDevVarDecorator new. desviation: 0.5; color: c; points: pts. why the decorator should be added to the builder? So see what I mean why do you expose to the user all the design challenges? I strongly suggest that during 1 month you stop to think in term of script. Imagine that you do not have a workspace anymore. Stef On 20 Mar 2015, at 22:18, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: Dear all, As many of you know, Grapher is a über-cool charting engine, part of Roassal. For people who do not know what Grapher is, here is a (compelling we hope) example: <Screen Shot 2015-03-20 at 6.12.22 PM.png> Which is obtained by the following script: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | b colors points ds pts dec lb | b := RTGrapher new. colors := Array with: Color red with: Color blue. points := OrderedCollection new. colors do: [ :c | ds := RTStackedDataSet new. pts := ((1 to: 100) collect: [ :i | 50 atRandom - 25 ]) cumsum. points add: pts. ds points: pts. dec := RTDevVarDecorator new. dec moveBehind; desviation: 0.5; color: (c alpha: 0.3); points: pts. ds connectUsing: (RTLine new color: (c alpha: 0.5); width: 1 ). b add: ds. b addDecorator: dec. ]. b axisX; axisY. b build. lb := RTLegendBuilder new. lb view: b view. colors doWithIndex: [ :c :i | lb addColor: c text: 'Series ', i printString ]. lb build. b view @ RTZoomableView. b view -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= In our grand vision of making Roassal the best visualizing engine of the Universe (we also know to be modest time to time, but not today :-), Grapher will play a very important role. We would like to stabilize Grapher and make it sure it happily fits everybody needs. You can help on it: - When you are tempted to look at the dark side of the planet (this is where R, JFreeChart, gnuplot, D3 and all their friends live), let us know. We will make sure to make you are happy again. - Share your wishlist with us. We already have a long todo list, but your opinion does matter and will take it seriously - we are open to contributions, which could be financial, bug fixe, enhancement, or simply encouragement. I am very happy to be surrounded by very smart engineers. Your encouragement are making them happy :-) Cheers, Alexandre, in the name of the Object Profile Team NB: sorry for the cross-list posting, but this email is very important for us, and for you we hope. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list vwnc(a)cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

10 years, 1 month

Roassal2, navigate in your view with scrollbars

by Pierre CHANSON

Hi all, new version of smooth scrollbars and pads is available, it allows you to navigate with scalability in the view, check this out: https://vimeo.com/122758568 try out: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | b | b := RTMondrian new. b shape rectangle withBorder; width: [ :cls | cls numberOfVariables * 5]; height: #numberOfMethods; linearFillColor: #numberOfLinesOfCode within: RTObject withAllSubclasses. b nodes: RTObject withAllSubclasses. b edges connectFrom: #superclass. b layout tree. b build. b view @ RTDoubleScrollBar -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= More examples in RTScrollBarBuilderExamples cheers, Pierre

10 years, 1 month

Improvement of grapher's ticks

by Alexandre Bergel

Hi! Milton did a wonderful improvement of Grapher. Consider the following expression: ((1 to: 20) collect: [ :v | 50 atRandom - 5.1 ]) plot It produces: As you can see, the horizontal bar is not in the 0 on the Y axis. And this is quite a problem actually. Excel does it much better. This is now fixed, in the last version of Roassal we have Milton has implemented an optimization algorithm that identify the optimal minimum & maximum value on the axis, and the optimal number of ticks, to have a pleasant reading. Enjoy! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 1 month

Issue 1115 in moose-technology: SVG and PNG Export Broken

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1115 by sean.p.d...(a)gmail.com: SVG and PNG Export Broken https://code.google.com/p/moose-technology/issues/detail?id=1115 In Moose 5.0: 1. In the Roassal Example Browser, select "Animated Scatter Plot" 2. Via the "…" menu a. export as PNG - the image will be clipped to tightly b. export as SVG - error -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 1 month

strange mooseModel behaviour

by Nicolas Anquetil

model entities detect: [:e | (e name = 'theName')] returns an entity model entityNamed: 'theName'. returns nil anybody seen this before? nicolas

10 years, 1 month

usage of moose and easel

by Sebastian Heidbrink

Hi! I am doing my first steps in learning Moose and also Roassal. Is it possible to start Roassal Easel and Moose Panel from the world menu and add a model afterwards? How would one visualize data with the help of Roassal which underlying data is too big for the Pharo image? Is there an example available how one could stream information on a Roassal view? Did somebody already visualize a LAN network? What would be a good framework/project to do such analysis? Thank you for any advice! Sebastian

10 years, 1 month

PetitParser: Different behavior when a parsing is finished

by Damien Cassou

Hi, Stéph and I are trying to revive Coral. There is a unit test that fails: self assert: (CLIParameterParser boolean) fail: #('falsely'). CLIParameterParser class>>boolean | trueToken falseToken | trueToken := (self caseInsensitiveKeywords: #('true' 'yes')) end ==> [:token | true]. falseToken := (self caseInsensitiveKeywords: #('false' 'no')) end ==> [:token | false]. ^ self new setParser: (PPElementParser on: trueToken / falseToken message: 'boolean expected'); name: 'bool' CLIParameterParser class>>caseInsensitiveKeywords: aCollection ^ (PPChoiceParser withAll: (aCollection collect: [ :each | each asParser caseInsensitive ])) token I don't know if this test used to pass but I guess it did. I think the problem is in the new work around "contexts". Can somebody please help? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

10 years, 1 month

Close Issue 1113

by Bernardo Ezequiel Contreras

Hi, Could someone close the issue 1113, please? https://code.google.com/p/moose-technology/issues/detail?id=1113 Thanks and sorry for the inconvenience. -- Bernardo E.C. Sent from a cheap desktop computer in South America.

10 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev