Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

by Alexandre Bergel

Hi! When tracing the execution in GT-debugger the text selection does not always reflect the real position of the program counter. Consider the following screenshot: I have simply pressed the step-into button, nothing more. The selection is not meaningful. Am I the only one to have noticed this? It would be great to have it fixed… Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Roassal3d elements & edges

by Natalia Tymchuk

Hello, Does Roassal3d elements know which edges are connected to them? Best regards, Natalia

9 years, 8 months

Roassal3D and Woden process handling

by Yuriy Tymchuk

Hi guys, I’m not experienced in OpenGL, but I’ve noticed that both Roassal3D and Woden occupy a high level process and are not yielding Processor to anyone else. For example code highlight, spotter, and other lower priority processes are not working as soon as you open a 3D visualization. On the other hand this doesn’t happen while using CodeCity (and it also uses OpenGL). Is it very complicated to make Roassal3D and Woden to respect other processes? Uko

9 years, 8 months

Improvement of Grapher

by Alexandre Bergel

Hi! We did a number of improvements of Grapher for Thomas. I am sharing them since some of you may find it relevant. ************************************** *** Tip: need to shift the Y-axis *** b := RTGrapher new. ds := RTStackedDataSet new. ds barShape color: Color red. ds points: #(5 1 20 8). b add: ds. b axisX noLabel; noTick. b axisY noDecimal. b build. The Y-Axis can be shifted vertically using labelConversion: and a minor translation of the value, as in: b := RTGrapher new. ds := RTStackedDataSet new. ds barShape color: Color red. ds points: #(5 1 20 8). ds y: [ :v | v - 10 ]. b add: ds. b axisX noLabel; noTick. b axisY noDecimal. b axisY labelConversion: [ :v | v + 10 ]. b build. ************************************** *** Improvement 1: Centered labels for bar charts *** -=-=-=-=-=-=-=-=-=-=-=-= b := RTGrapher new. ds := RTStackedDataSet new. ds barShape color: Color red. ds points: #(5 1 20 8). ds y: [ :v | v - 10 ]. ds barChartWithBarCenteredTitle: [ :value | '##', value asString ]. b add: ds. b axisX noLabel; noTick. b axisY noDecimal. b axisY labelConversion: [ :v | v + 10 ]. b build. -=-=-=-=-=-=-=-=-=-=-=-= ************************************** *** Improvement 2: Average for X values *** b := RTGrapher new. ds := RTDataSet new. ds dotShape color: Color red. ds points: #(5 1 20 8). b add: ds. b addDecorator: (RTHorizontalAverageDecorator new withLabel; labelConvertion: [ :aValue | 'average = ', aValue asFloat asString ]). b build. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

Bug in GLMTreeMorphNodeModel?

by Jan Kurš

Hi, From time to time I see a bug in GLMTreeMorphNodeModel>>pathIn: It happens like this: 1) PPSmalltalkGrammar new inspect. 2) Click to the tree view and do some clicking here and there, expanding and collapsing nodes. 3) After some time, pharo freezes in a enldess recursion call. You can see it in the attached screenshot. This behaviour is there for quite a time (at least half a year, as far as I remeber). Cheers, Jan PS: Where shall I report bugs like this? GoogleCode or FogBugz?

9 years, 8 months

Small workshop/hackathon today and tomorrow about Pharo and Agile Visualization.

by Offray Vladimir Luna Cárdenas

Hi all, Today and tomorrow, a small group of persons will be doing a workshop/hackathon about Pharo and Agile Visualization at our local hackerspace. Details on the event are on: http://hackbo.co/hackboweb/eventos/evento/375 I will be sharing teaching materials, first impressions and questions with you about the experience, while is happening and after that. Thanks, Offray

9 years, 8 months

SVG example added

by Alexandre Bergel

Hi! We have exposed the SVG examples in the Roassal example browser. Some of you may be interested in this Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 8 months

[Request]: Review Updated Pharo 4.0 Welcome Text

by Sean P. DeNigris

Since there are a bunch of GT-related items for which I added one-liners and links... https://github.com/pharo-project/pharo-workingRoadmaps/blob/master/Pharo40W… Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Request-Review-Updated-Pharo-4-0-Welcome-Text-tp48237… Sent from the Moose mailing list archive at Nabble.com.

9 years, 8 months

Update GTInspection Blog Post?

by Sean P. DeNigris

Can http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed be updated to remove the "load in Pharo 3.0" instructions? I'd like to link the post to the Pharo 4.0 Welcome window, but it would be more powerful if it started with "The goal of the Glamorous Toolkit project is...". Thanks. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Update-GTInspection-Blog-Post-tp4823731.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 8 months

Roassal TRCompositeShape regression

by Peter Uhnák

Hi Alex, unfortunately changes in TRCompositeShape created a regression, because now TRRemoveCallbacks are executed multiple times. the commit is Trachel-AlexandreBergel.266 Interestingly there is TRCompositeShapeTest>>testCallback01 which works, but it doesn't use RTElement. Here's a test case: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |v e executed| v := RTView new. e := RTElement new. e + (RTBox new) + (RTEllipse new). executed := 0. e trachelShape addCallback: (TRRemoveCallback new block: [ :shape | executed := executed + 1 ]). v add: e. TestAsserter new assert: executed equals: 0. e remove. TestAsserter new assert: executed equals: 1. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Now since you have discussed with Jan that the new behavior makes sense in some circumstances, it would be better to have both behaviors. So I would propose to make a distinction for RemoveCallback - to not triggered them from TRCompositeShape, because it is not reentrant. Thus when executed on composite shape, only non-removing callbacks would be executed. Additionally it seems very random that CompositeShape uses it's first subshape for callbacks; what is so special about the first one? Why can't composite shape hold it's own callbacks, or have an explicit way to specify which one to use (first, second, none, ..)? Since Composite Shape is recurring problematic theme, perhaps there should be some wider discussion to collect all the use cases? What do you think? Peter

9 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev