Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Jean-Christophe Bach

Hello Pharoers, We propose a Pharo sprint / Moose dojo this Friday, 10th July, starting at 10:00am. (Local Time Lille). It will be at the Inria Lille, Building B, third floor (RMoD offices). Remotely, you can join us on the official IRC channel #pharo on irc.freenode.net server. During the sprint, we will try to synchronize local and remote Pharo sprinters. As the building is not open to the public, please contact us before if you plan to come. JC

10 years

curved lines

by Tudor Girba

Hi, I would like to draw a simple curved line. The idea would be to offer a simple way to deal with edges that come from or to other place. Roassal2 seems to not support this right now (at least not anymore). Do I miss something? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years

Failing tests in Moose5.1

by Blondeau Vincent

Hi, It would be nice if the moose5.1 (https://ci.inria.fr/moose/job/moose-5.1/) image has no failing tests. 2 tests are failing : >>><javascript:showStackTrace('test-GT.Tests.Spotter.GTSpotterProcessorsForExamplesTest.testEachProcessor','GT.Tests.Spotter/GTSpotterProcessorsForExamplesTest/testEachProcessor//summary')> GT.Tests.Spotter.GTSpotterProcessorsForExamplesTest.testEachProcessor<https://ci.inria.fr/moose/job/moose-5.1/lastCompletedBuild/testReport/GT.Te…> 1 mn 43 s 44<https://ci.inria.fr/moose/> >>><javascript:showStackTrace('test-GT.Tests.Inspector.GTInspectorExamplesTest.testAllExamples','GT.Tests.Inspector/GTInspectorExamplesTest/testAllExamples//summary')> GT.Tests.Inspector.GTInspectorExamplesTest.testAllExamples<https://ci.inria.fr/moose/job/moose-5.1/lastCompletedBuild/testReport/GT.Te…> 10 mn 45<https://ci.inria.fr/moose/> The second has a duration of 10mins which is very long. Does it mandatory do run it and does it possible to split it ? A way to solve them is to change in RTGrapherExample>>exampleSeismDepthAndMag and exampleSeisms, http://earthquake.usgs.gov/earthquakes/feed/v0.1/summary/2.5_month.csv by http://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/2.5_month.csv But as it is in Roassal repo I cannot commit it... and one will have to change the configuration of Moose5.1... By the way, does the GT* tests can be done in a GT job, e.g.: https://ci.inria.fr/moose/job/gtoolkit5 or https://ci.inria.fr/moose/job/gtoolkit/? 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

PetitParser : an OrderedCollcetion transformed to a PPDelegateParser

by abdelghani ALIDRA

Hi everyone, I have defined #PPMyLanguageGenerator inheriting from PPMyLanguageParser inheriting from PPCompositeParser In the class PPMyLanguageGenerator I have an instance variable named: model I initialize with : model := OrderedCollection new to collect reconized elements of my language I also define PPSplotModelGenerator>>aMethd anElement := someCode. model add: anElement When I try to test my method from a PPCompositeParserTest sub subclass I have the error message on the ligne above : MessageNotUnderstood: PPDelegateParser >>add: But model is not supposed to be a PPDelegateParser!!!! Any idea about this matter and how can I acc my variable from my methods? Regards. Abdelghani

10 years

Error when Importing ST code?

by Alexandre Bergel

Hi! I have an error when trying to filter some packages in the wizard, after having pressed ST->. Any idea? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years

visualizing package dependencies

by Peter Uhnák

Hi, after a year of using Moose I actually wanted to use it for what it was made for... and I kind of don't know how... so basically I have packages (let's call them B1 B2 and D1 D2 D3) and I would like to visualize all dependencies between classes in those packages. More specifically I'm interested in all calls from D* packages to B*... After looking through TheMooseBook I've found things like MooseModel and MoViewRenderer, which the first I assume is related to non-smalltalk code and second is outdated version of RTMondrian. RTMondrian however doesn't have documentation yet and I am kind of lost. How do I define that I am interested only in calls between those packages (that's without calls inside a package)? Ideally if it can also display the name of the methods. I could probably build it procedurally going in cycles class by class, method by method but I was hoping there's better way. Any pointers appreciated, Peter

10 years

GT Inspector: Set Presenter Width

by Sean P. DeNigris

Why the restriction that columns be equal? Several times I've wished that I could set the width of each column. IMHO it would be a very useful feature to at least default to equal with the ability to drag, if not ideally some smart width calculation based on the width of the information displayed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/GT-Inspector-Set-Presenter-Width-tp4834858.html Sent from the Moose mailing list archive at Nabble.com.

10 years

Frequency distribution and histograms

by Pierre CHANSON

Hola todos, These days I am working on compete with R. I am taking the datasets and examples from http://cran.r-project.org/doc/contrib/Zhao_R_and_data_mining.pdf and make it with Roassal even better ! Or almost... ;) First chapter first pages, the histograms... In Roassal they were not working so well. So lately I restructured the RTDistribution package. This, by default make a classical frequency distribution, with an optimized number of classes. The method #strategyBlock: allows to change the strategy for the distribution. I also worked on the RTHistogramSet and method #histogram of SequenceableCollection to improve a bit the looking. There is still here some work to do but at least the histogram works well and looks fine. We worked with Alejandro on the algorithm of frequency distribution to make it efficient compared to the classic one (Only one iteration on datas during the algo itself). Here are some examples, don't hesitate to try a bit and give me feedbacks if any bugs, so I can move on the next graphs ;) #(5 3 8 6 5 4 2 9 1 2) histogram. #(1 2 3) histogram. #(555 1 1 2) histogram. ((1 to: 1000) collect: [:i | i atRandom ]) histogram. Also, I found this page and thought it was really nice animations !! http://bost.ocks.org/mike/algorithms/ cheers, Pierre

10 years

Glamour: opening paths in tree with filters

by Usman Bhatti

Hi, I am having trouble with opening a specific path in tree presentation (using MorphTreeMorph) when filtering nodes. What I am trying to achieve is that if a node is searched in a tree at level 4, all the parent nodes are opened to show the node searched (hence the user the does not need to open the nodes manually). In Glamour, when combined with filtering, expanding up to the root of the search node works when the parent node is already expanded, otherwise the nodes are not expanded. At the end of the mail, there are two snippets to reproduce the behavior. MorphTreeMorph>>addMorphsTo: from: withExpandedItems: atLevel: is the method responsible for this behavior in Glamour and it seems that nodes are only expanded (to show their children) if they were expanded beforehand. Is there a way to do otherwise in MorphTreeMorph (open paths with non-expanded nodes)? tx. Usman Code snippets in Glamour (Pharo 4.0): | tabulator | tabulator := GLMTabulator new column: [ :c | c row: #one ]; yourself. tabulator transmit to: #one; andShow: [:a | a tree title: 'Show filter paths'; rootsExpanded; children: [:item :x : level | (item < 5 and: [ level < 6 ]) ifTrue: [ {item + 1}] ifFalse:[#() ]]; filterOn: [:text :each | text = each asString]]. tabulator openOn: (1 to: 1) "searching for 3 does not open the path to 3 ?!?!?!" | tabulator | tabulator := GLMTabulator new column: [ :c | c row: #one ]; yourself. tabulator transmit to: #one; andShow: [:a | a tree title: 'Show filter paths'; rootsExpanded; children: [:item :x : level | (item < 3 and: [ level < 5 ]) "to stop adding infinite children" ifTrue: [ level = 4 "plug a node 5 deep down and see if we can find the path" ifTrue: [(1 to: 5)] ifFalse: [ (1 to: item * 2) ] ] ifFalse:[#() ]]; filterOn: [:text :each | text = each asString]]. tabulator openOn: (1 to: 2) "searching for 5 correctly opens the path up to 5"

10 years

GTInspector "too smart" for debugging :-(

by Nicolas Anquetil

In Moose, I have some problems with my sourceAnchors. Because of these problems (bugs), sourceText does not work for these entities Unfortunatelly, when I try to inspect these faulty entities in GTInspector (for debugging) it does not work because the first thing it tries to do is compute all panes, including the one for sourceText which is buggy :-( Possible solutions: - GTInspector's panes would gracefully fail and allow the inspector to be displayed nevertheless - Compute a pane when it is visible and only at that moment (but anyway, failing gracefully would be nice. It is always better to be graceful) nicolas

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