Moose-dev January 2016

moose-dev@list.inf.unibe.ch

34 participants
47 discussions

Script of the day: Charting several data sets
by Alexandre Bergel 21 Jan '16

21 Jan '16

Hi! Just in case you did not know, we have a MultipleData to chart using bars several data sets. For example: -=-=-=-=-=-=-=-=-= b := RTGrapher new. d := RTMultipleData new. d barShape color: Color blue. d points: #( #('hello' 1 2 1) #('world' 2 4 2) #('bonjour' 3 5 4) #('Gutten Morgen' -1 4 -5)). d addMetric: #second. d addMetric: #third. d addMetric: #fourth. "d barChartWithBarCenteredTitle: #first." d barChartWithBarTitle: #first rotation: -30. b add: d. b -=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Problem with Rubric?
by Alexandre Bergel 20 Jan '16

20 Jan '16

Hi! I regularly see very obvious problems with Rubric. I have just downloaded the latest Moose image and typing in a Playground and get an exception in: RubTextComposer>>recomposeFrom: start to: stop delta: delta Am I the only one? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

loading ozone in moose
by Usman Bhatti 20 Jan '16

20 Jan '16

I'm try to load Ozone in moose 5.1 but I got the following error: This package depends on the following classes: MalCyclesCoverageAndSort DSMMatrix DSMCellTest DSMCell NumberColoredDSM You must resolve these dependencies before you will be able to load these definitions: weightedSize testWeightedSize doLayerGraphModified .... Does anyone know what happened to the classes that are not found in the newer version because it loaded correctly in Moose 5.0 (Pharo 3.0)? Are these renamed or is there a package not loaded in the latest moose? tx!

2 2

Sugiyama layout is now working...
by Alexandre Bergel 20 Jan '16

20 Jan '16

Hi! I have found and fixed a bug in the Sugiyama layout. Example of usage: b := RTMondrian new. b shape box color: Color red. b nodes: (1 to: 100). b edges connectFrom: [ :v | v // 2 ]. b layout sugiyama. b normalizer normalizeSize: #yourself; alphaColor: 0.4. b Here is a screenshot in Hapao: :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

spotter: top search for senders and references
by Tudor Girba 19 Jan '16

19 Jan '16

Hi, With the latest GT integration, we also integrated the search for senders and references from the first step. Here is a detailed explanation about it, including what we still want to do, how it’s done, and how to discover what else is around: http://www.humane-assessment.com/blog/spotting-senders-references-with-gtsp… Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

1 0

a new version of gtdebugger
by Tudor Girba 18 Jan '16

18 Jan '16

Hi, A new version of GTDebugger was just integrated. Several issues were addressed. Some more notable things are: - the stack shows columns for class, method, other info - there are new keybindings in place that do not collide with the text editor - the accept/cancel buttons are in the contextual menu at least for Pharo 5 - the variables pane received a label There are still some things todos left like: - the columns in the stack should be resizable - thisContext, stackTop - perhaps make the key bindings controllable through settings We kindly invite everyone to test it and provide feedback. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

1 0

Re: [Pharo-users] [ann] gtdebugger in pharo 5.0
by Nicolai Hess 17 Jan '16

17 Jan '16

2016-01-08 11:24 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > We are about to integrate in Pharo a new member of the Glamorous Toolkit: > the GTDebugger. As this is a significant change that might affect your > workflow, here is some background information to help you deal with the > change. > > First, you should know that the change is not irreversible and it is > easily possible to disabled the new debugger through a setting. However, > please do take the time to provide us feedback if something does not work > out for you. We want to know what can be improved and we try to react as > fast as we can. > > A practical change comes from the fact that the variables are manipulated > through a GTInspector, which makes it cheaper to maintain in the longer run. > Accept and Cancel buttons shouldn't be there or should not act on if the codepane hasn't changed. (every press on "accept" writes a new method version, although the contents didn't changed - tested on Latest update: #50524 ) Most (all?) other tools don't have Accept/Cancel buttons. - I really miss the "List Methods using 'varname'/List Methods storing into 'varname' - is "stackTop" now gone ? I thought you wanted to add it to the stack ? - thisContext is gone as well ? - the Bytecode/GT button is badly placed, it looks like the "downarrow" window menu icon is a dropdown menu with label "Bytecode" (since when do we put buttons in the title pane? - the evaluator pane is shown as "dirty", as it does not make a difference if we accept the text in this pane, there shouldn't be a dirty indicator. - you can not use the inspector pane to change inst var values - there is no way to refresh the inspector pane I don't open bugtracker entries now, I 'll wait maybe this issues aren't bugs but features. nicolai

4 6

1 failing test (MooseQuery)
by Tudor Girba 16 Jan '16

16 Jan '16

Hi, So, the VM was updated and the become: issues are solved. There is now only 1 failing test: https://ci.inria.fr/moose/job/moose-6.0/1077/testReport/junit/Moose.Tests.F… The problem is that MooseOutgoingCompositeQueryResult doesNotUnderstand #atScope: I suspect it has to do with the new addition of the Moose Query implementation. Could someone look at the new Moose Query? Cheers, Doru -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

1 1

PetitParser Browser
by Anne Etien 15 Jan '16

15 Jan '16

Hi, Does anyone knows why when using PetitParser Browser, the debugger tab presents a tree composed of only one or maximum two elements (even if it enters more rules)? Any help will be useful because debugging petitParser code is really hard. Thanks. Anne

2 2

Moebio framework
by Offray Vladimir Luna Cárdenas 13 Jan '16

13 Jan '16

Hi, I just want to share some recently released framework for data visualization and interaction that could serve as inspiration: http://moebiolabs.github.io/moebio_framework/ I'm thinking, which of the visualizations that are shown in the reel could *not* be done with Roassal and what is needed for that. Just for reference, a friend and I found a visualization that was not on Roassal a couple of months ago (see [1]) and it was a pleasure to create something that provides some support for visualizations that look alike (see [2][3][4]). [1] http://www.theguardian.com/world/interactive/2012/may/08/gay-rights-united-… [2] https://offray.withknown.com/2016/matrix-sunburst-visualization-example-for… [3] https://offray.withknown.com/2016/matrix-sunburst-visualization-example-for… [4] https://offray.withknown.com/2016/matrix-sunburst-visualization-example-for… Of course the best way to know if Roassal supports something like Moebio Framework is to approach some problem which produce a similar output. Cheers, Offray

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev January 2016