- Moose-dev - INF Mailman

Camp Roassal place

by Peter Uhnak

Hi, where will camp Roassal be? Same place as camp smalltalk? Peter

9 years, 11 months

3
3
0 0

DeepTraverser

by Nicolas Anquetil

Anybody can explain the changes that occured over DeepTraverser ? (Ideally how can we switch from old to new traverser?) We have an "old" (1 year) bit of code that use the deepCollect: method However, the changes in DeepTraverser break our code :-( DeepTraverser-StefanReichhart.9 Time: 11 May 2015, 7:02:16.666278 pm nicolas

9 years, 11 months

5
12
0 0

build ?

by Alexandre Bergel

Hi! There are 3 tests that have been failing for long… What should we do? Simply remove them to get the build green? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 11 months

5
5
0 0

Scrollbar in Roassal

by Alexandre Bergel

hi! Just to let you know since some of you are not aware. We have nice scrollbars that adjust automatically when zooming in/out and drag and dropping the view. Try this: b := RTMondrian new. b nodes: RTObject withAllSubclasses. b edges connectFrom: #superclass. b layout tree. b build. b view @ RTDoubleScrollBar. b view -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 11 months

3
5
0 0

[ANN] New version of MooseChef

by Jean-Christophe Bach

Hi, We are pleased to announce a new version of MooseChef. This version has the advantage to be generic and can be easily used for non-object oriented FAMIX metamodel. We used it for example for FAMIXSQL without redefining everything. The existing API is still working and will be removed later when people will be used to this new version. The new version modifies FAMIX entities with pragmas and traits. It can be downloaded using the configurationOf available on this SmalltalkHub project: http://smalltalkhub.com/#!/~AnneEtien/MooseQueryDraft/ The methods to use are (respectively for outgoing): queryLocalIncoming: aFAMIXAssociationClass retrieve incoming association whose source is self and the type of association is aFAMIXAssociationClass queryIncoming: aFAMIXAssociationClass queryLocalIncoming applied on self and on each of its children queryAllLocalIncoming similar to queryLocalIncoming but take into account any kind of association types queryAllIncoming similar to queryIncoming but take into account any kind of association types We are working on atScope: and within: to generalize them and integrate them into the new API. Feel free to give feedbacks, Anne & JC

9 years, 11 months

3
2
0 0

RTDoubleArrowedLine

by Alexandre Bergel

Hi! With Usman we are pair programming today on Moose and Roassal. We have just implemented the following: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | v l e1 e2 eShape | v := RTView new. eShape := RTEllipse new size: 8; color: (Color blue alpha: 0.3). e1 := eShape element. e2 := eShape element. e2 translateBy: 50 @ 30. v add: e1; add: e2. e1 @ RTDraggable. e2 @ RTDraggable. l := (RTDoubleArrowedLine new color: Color red) edgeFrom: e1 to: e2. v add: l. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Yeah, not groundbreaking, but a small and positive step. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 11 months

3
3
0 0

Issue 1123 in moose-technology: Smalltalk importer wizard in Moose panel should be dimensioned to the screen size

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1123 by v.blonde...(a)gmail.com: Smalltalk importer wizard in Moose panel should be dimensioned to the screen size https://code.google.com/p/moose-technology/issues/detail?id=1123 Describe the problem: what do you get? what do you expect? The panel is too height for small screan and we can't click on Finish... How to reproduce the problem: step by step if necessary Open the moose panel, click on ST, choose some packages and try to click on finish! Additional information: platform, context which may impact the problem Screen 15" Please fill in the labels with the following information: * Type-Defect * Component-MoosePanel -- 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

9 years, 11 months

2
2
0 0

Issue 1122 in moose-technology: Grapher - Exception for zero values

by moose-technology＠googlecode.com

Status: New Owner: usman.bh...(a)gmail.com CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal New issue 1122 by usman.bh...(a)gmail.com: Grapher - Exception for zero values https://code.google.com/p/moose-technology/issues/detail?id=1122 Exceptions should be managed in Grapher with all points are zero To reproduce the problem in Moose 5.1: grapher := RTGrapher new extent: 300 @ 200; title: 'testing zero values'; yourself. ds := RTDataSet new. ds dotShape ellipse color: (Color red alpha: 0.5); size: 10. ds points: {0->0. 0->0}; connectColor: (Color red alpha: 0.5); y: #value; x: #key; highlightIf: [:each | true] using: #value. grapher add: ds. grapher axisY decimal: 0; title: 'asdasd'. grapher axisX labelRotation: -30; title: ''; numberOfLabels: 2. grapher build. -- 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

9 years, 11 months

1
1
0 0

Ecore Importer

by Brice GOVIN

Hi everybody, does anyone know if there is an Ecore importer in Pharo? The idea is to import an ecore file (so an XMI) and to create Pharo classes in a given package directly. At least, there could be an Ecore importer that create immediately a MooseModel ? Regards, -------------- Brice Govin PhD student in RMoD research team at INRIA Lille Software Engineer at THALES AIR SYSTEMS Rungis ENSTA-Bretagne ENSI2014 64 chemin des boeufs 91220 PALAISEAU

9 years, 12 months

3
2
0 0

update #stable glamour core Pharo 4.0

by Usman Bhatti

Hi Andrei. I would like to update the stable version of ConfigurationOfGlamourCore for Pharo 4.0 to include the fix for overlapping status bars and to load: Glamour-Morphic-Renderer-usmanbhatti.323 instead of: 'Glamour-Morphic-Renderer-AndreiChis.321'; Is it ok with you? regards.

9 years, 12 months

2
2
0 0

Image crash on Moose 6.0 due to fonts on W7

by Blondeau Vincent

Hi, I was working with the Moose6.0 #105. I closed the image and, at startup, I got a Fatal VM error... It seems that is a problem with font management through external calls (libfreetype-6.dll)... I don't know how to resolve this issue. The stack trace is attached. Cheers, Vincent Ps: I am under W7... ________________________________ 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.

9 years, 12 months

1
0
0 0

status bar in Glamour browsers

by Usman Bhatti

Hi, When adding status bar to Glamour browsers in Pharo 4.0, the contained presentations overlap the top elements of container. Here's a little script to reproduce this problem (see attached screenshot). Status bar does not seem to have changed, surely the layout frames of the container browser or the presentations are not handled correctly. I tried to dig the problem but could not get to its cause. regards. usman | browser | browser := GLMTabulator withStatusbar. browser column: #one. browser transmit to: #one; andShow: [:a | a text display: 'something wrong with my browsers layout'; title: 'Tab'. a text display: 'something wrong with my browsers layout'; title: 'Tab' ]. browser openOn: 1 [image: Inline image 3]

9 years, 12 months

2
2
0 0

GT Paging Through Large Collections

by Sean P. DeNigris

Several times I found myself thinking that it's a PITA that the -> and text field only appear when you vertically scroll to the end of the currently-shown items. Sometimes you know right away that e.g. you have to page about 5 times, and currently you have to keep alternating scroll/page/scroll/page... ----- Cheers, Sean -- View this message in context: http://forum.world.st/GT-Paging-Through-Large-Collections-tp4835968.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 12 months

3
4
0 0

PetitParser ignorable parsers

by Peter Uhnák

Hi, is it possible to add such a parser that would consume input, but wouldn't return anything? Right now I do things like... MyParser>>rule ^ ($[ asParser, anotherRule, $] asParser) ==> [ :nodes | nodes second ] Of course when the rules are more complex, so is the block; however it seems that this is how it's done in the example parsers... So, would it be possible to add some kind of Null/Void/Ignore/Throwaway parser, that would consume the input, but would be omitted from the result? so the above method could be written as MyParser>>rule ^ $[ asNullPaser, anotherRule, $] asNullParser or MyParser>>rule ^ $[ asParser ignore, anotherRule, $[ asParser ignore or something else. Thanks, Peter

9 years, 12 months

3
3
0 0

GT: Difficult to edit long strings

by Sean P. DeNigris

When editing in place, there is apparently no way to scroll to the right, and the "String" presentation seems to allow editing, but the accepted text does not appear to be saved. ----- Cheers, Sean -- View this message in context: http://forum.world.st/GT-Difficult-to-edit-long-strings-tp4836004.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 12 months

3
3
0 0

Pharo sprint & Moose dojo this Friday

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

9 years, 12 months

1
0
0 0

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"

9 years, 12 months

4
15
0 0

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

5
9
0 0

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

2
1
0 0

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

3
5
0 0

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

3
2
0 0

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

3
7
0 0

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

5
10
0 0

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

1
0
0 0

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

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev