Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Marked failing tests in PetitRegex as expected failures
by Stephan Eggermont 10 Nov '14

10 Nov '14

The Henry tests are acceptance tests that have been failing for a long time. The structure of RxParser is different from that of PPRegexParser. Stephan Name: PetitRegex-StephanEggermont.30 Author: StephanEggermont Time: 10 November 2014, 12:21:14.634158 pm UUID: 30da11c2-f338-454a-b9f6-4677f21bc791 Ancestors: PetitRegex-JanKurs.29 Marked Henry 45, 48, 87, 115, 199, 120 as expected failures.

1 0

[Survey] Reasoning about objects
by Andrei Chis 10 Nov '14

10 Nov '14

Hi all, In order to improve object inspectors we are doing a survey. We want to know whether several features are important to you or not when trying to understand objects. This is a very short survey and should't take you more than 10 minutes to complete. Please take this time to participate. Here is the link to the survey: http://goo.gl/forms/xKPxqLxJJv Cheers, Andrei

1 0

Roassal2: Camera scale callback?
by Jan B. 07 Nov '14

07 Nov '14

Hello In our Roassal 2 based app, we would like to have current zoom displayed. We need to change the value when camera scale changes. Maybe I could make events for all possible sources of zooming, but it seems pretty error-prone and I did not find a way to do it for RTZoomableView source. Therefore, I think we need something like "TRCameraScaleCallback", or any idea how to do it other way. Thank you Jan Blizničenko -- View this message in context: http://forum.world.st/Roassal2-Camera-scale-callback-tp4788816.html Sent from the Moose mailing list archive at Nabble.com.

2 2

[GLM] How to preserve a view
by Roberto Minelli 07 Nov '14

07 Nov '14

Hi, Sorry if you receive multiple copies of this email, I sent the previous with another email address. I am developing a browser with Glamour inside the GT inspector that looks like this: When I click on a slice of the pie (i.e., the red slice), I get the visualization on the right pane with highlights on red components, as shown in the figure. Then I can zoom and pane the right view, etc. When a click on another slice on the left view, the right view gets regenerated, thus zoom and pan levels are restored to the default values. Since, for each pie the right view looks the same but has to have different highlights, I was wondering if there is a way to keep the right view “fixed”, i.e., not re-creating every click, and just change the highlighting. Thanks a lot for your help, Roberto

2 2

How to make a UML diagram of a package developed in Pharo3?
by phil＠highoctane.be 06 Nov '14

06 Nov '14

Hello, I've got an image I develop in and would like to be able to generate diagrams for a number of classes and relationships to explain how things are working to other people. How can I do that with Moose? (Or GT I have loaded in 3.0) I have seen a couple diagrams floating around, so it is definitely possible to do. But I also saw that all of that was done in a Moose image and not in a normal Pharo image. TIA Phil

5 15

Does Charter handle normal bar graphs currently?
by Chris Cunningham 06 Nov '14

06 Nov '14

I am currently using EyeSee for doing some charting/graphing, and am running into some of its limitations. I'd like to use the newest/bestest, but am stumped how to use it right now. Attached is roughly the graph I want:[image: Inline image 1] except I'd like the bars to be located correctly for the time (as well as the labels). Or, even better, be able to state that I want the days labelled, and either hour tick marks, or optional tick marks. And, of course, be able to specifically call out the color of the bars. Data to build this chart: x := { Dictionary new at: 'COLOR' put: Color gray; at: 'TIME' put: (DateAndTime fromString: '2014-10-30 12:11:28.0'); at: 'SECONDS' put: 4; yourself. Dictionary new at: 'COLOR' put: Color gray; at: 'TIME' put: (DateAndTime fromString: '2014-10-31 12:11:28.0'); at: 'SECONDS' put: 5; yourself. Dictionary new at: 'COLOR' put: Color red; at: 'TIME' put: (DateAndTime fromString: '2014-10-31 12:41:28.0'); at: 'SECONDS' put: 15; yourself. Dictionary new at: 'COLOR' put: Color green; at: 'TIME' put: (DateAndTime fromString: '2014-11-01 12:11:28.0'); at: 'SECONDS' put: 7; yourself. Dictionary new at: 'COLOR' put: Color gray; at: 'TIME' put: (DateAndTime fromString: '2014-11-02 12:11:28.0'); at: 'SECONDS' put: 1; yourself. Dictionary new at: 'COLOR' put: Color gray; at: 'TIME' put: (DateAndTime fromString: '2014-11-03 12:11:28.0'); at: 'SECONDS' put: 4; yourself. }. -cbc

2 8

XML tests failing
by Tudor Girba 06 Nov '14

06 Nov '14

Hi, The Moose job is failing due to two XML parser tests. Can anyone look at this problem: https://ci.inria.fr/moose/job/moose-5.0/3077/testReport/ Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

1 0

Issue 1094 in moose-technology: List presentations should be fast on large collections
by moose-technology＠googlecode.com 03 Nov '14

03 Nov '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1094 by chisvasi...(a)gmail.com: List presentations should be fast on large collections https://code.google.com/p/moose-technology/issues/detail?id=1094 Opening a large collection using a list presentation is very slow. The following example shows the problem. Also when inspect just (1 to: 2000000) collect:#asString creating the Items tab takes time. composite := GLMCompositePresentation new. composite list showOnly: 50. composite openOn: ((1 to: 2000000) collect:#asString) Most of the time seems to be spend in GLMTreeMorphModel>>#roots that given that GLMTreeMorphModel>>#amountToFilterBy always returns nil. -- 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

1 0

TRMultiCompositeShape>>announcer
by Tudor Girba 03 Nov '14

03 Nov '14

Hi, I think we have a problem with announcer from TRMultiCompositeShape. It is implemented as if it should not be called, but TRCanvas>>shapeWithAction: eventClass forPositionInPixels: position calls it. So, we have a problem. I observed the problem when creating edges with RTMondrianViewBuilder. For example: view := RTMondrianViewBuilder new. view shape label text: #asString. view nodes: (1 to: 100). view shape orthoHorizontalLine color: Color veryLightGray. view edgesFrom: [:x | x // 10]. view horizontalTreeLayout layered. view And then click on an edge. Doru -- www.tudorgirba.com "Every thing has its own flow"

2 3

Issue 1092 in moose-technology: Roassal2 examples browser is not working
by moose-technology＠googlecode.com 03 Nov '14

03 Nov '14

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Milestone-5.0 Component-Roassal Component-GlamorousToolkit New issue 1092 by tu...(a)tudorgirba.com: Roassal2 examples browser is not working https://code.google.com/p/moose-technology/issues/detail?id=1092 Just that. It seems that the recent example refactorings broke the browser. -- 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

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev