Moose-dev February 2016

moose-dev@list.inf.unibe.ch

27 participants
31 discussions

Anyone can explain this PParser behaviour?
by Nicolas Anquetil 27 Feb '16

27 Feb '16

--- testWhatTheHeck self parse: 'true' rule: #condition. self parse: 'true)' rule: #condition. self parse: 'true' rule: #expression. self parse: 'true)' rule: #expression. --- First 3 tests pass, last one fails But the grammar says: --- condition ^ expression --- Can anyone propose an explanation? [Notes: Yes I checked that I am testing the right grammar Yes the 'true)' test is strange, but this is precisely what I am trying to debug (why does it pass for #condition ?) ] nicolas -- Nicolas Anquetil RMod team -- Inria Lille

6 21

Variable bindings in a playground?
by Alexandre Bergel 26 Feb '16

26 Feb '16

Hi! Some times ago non-declared variables where painted in blue. Apparently, they are now in red. Can this behavior be restored? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 3

Comment Extractor
by Brice GOVIN 26 Feb '16

26 Feb '16

Hi, I’d like to know if there is some kind of comment extractor for a source code () in Moose. I was trying to get a quick understanding of methods from an old code (not smalltalk) and I couldn’t get rid of the source code itself… I need a way to get the comment associated to a method. I could do it by myself but if there is already a way to do it I prefer to use it (or at least adapt it to my case). Thanks, -------------- Brice Govin PhD student in RMoD research team at INRIA Lille Software Engineer at THALES AIR SYSTEMS Rungis ENSTA-Bretagne ENSI2014 22 Avenue du General Leclerc 92340 BOURG-LA-REINE

2 3

Verveine download link
by abdelghani ALIDRA 26 Feb '16

26 Feb '16

Hi all, I would like to download Verveine J but I could not find the download link. Has any one a working one? Thanks in advance, Sheers Abdelghani

2 1

198 different authors have contributed in Roassal
by Alexandre Bergel 26 Feb '16

26 Feb '16

Big thanks to all of them! ((({'Roassal2' . 'Trachel' . 'Roassal2Spec' . 'Roassal2GT' } collect: [ :n | RPackageOrganizer default packageNamed: n ]) flatCollect: #classes) flatCollect: #authors) asSet size => 198 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 1

How to display an histogram given a bag
by stepharo 25 Feb '16

25 Feb '16

Hi I have a bag b := Bag new. b add: 1 withOccurrences: 5. b add: 3 withOccurrences: 4. b add: 6. b and I would like to display it as an histogram with roassal. Stef

8 11

PetitParser and huge files
by Blondeau Vincent 25 Feb '16

25 Feb '16

Hi, I would like to parse a log file with PetitParser. I wrote the parser and it works with a test file of 5,3 Mo. But the real case is 73,6 Mo... The main problem is that PetitParser calls asPetitStream, which calls contents on the file. At this point, the primitive 72 #elementsForwardIdentityTo: fails for #'insufficient object memory'. However, my image is new so it should not raise an error because I have at least 500 Mo of free space. Is there an way to parse the file as a stream to avoid the call to contents? Maybe by using PPStream? Thanks in advance, 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."

4 4

short spotter demos
by Tudor Girba 25 Feb '16

25 Feb '16

Hi, The recent debates around Spotter, showed that some of its features are not well understood. In an effort to document it more thoroughly I created a couple of (very short) videos. They have no sound. Please take a look and let us know what you think. Spotting a class with GTSpotter https://www.youtube.com/watch?v=_wIh4fekcD8 Scoping a search to a specific category in GTSpotter https://www.youtube.com/watch?v=9-fY4mN6Isc Using category shortcuts in GTSpotter https://www.youtube.com/watch?v=USNZ7_6gLDA Using preview in GTSpotter https://www.youtube.com/watch?v=FSm5xylmTqM Using the dive-in action in GTSpotter https://www.youtube.com/watch?v=C7mJBX3Oblw Loading a public playground with GTSpotter https://www.youtube.com/watch?v=xeDDLLdA1v8 Navigating through files with GTSpotter https://www.youtube.com/watch?v=dHQqXcS0vDI Refining a search through the dive-in-category action with GTSpotter https://www.youtube.com/watch?v=IclLett0d6c Opening a cached playground page with GTSpotter https://www.youtube.com/watch?v=V_yndTSsj8c Cheers, Doru -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

4 10

Moose Chef help
by Alexandre Bergel 24 Feb '16

24 Feb '16

Hi! Just to let yo know: I have just committed a new version of the package Moose-Help with a help for Moose Chef. It is very preliminary, but I will make it grow over the time. Help is welcome :-) Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

Theme aware-ish TRMorph
by Peter Uhnák 24 Feb '16

24 Feb '16

Hi, since I wanted to use DarkTheme I played around with TRMorph (since seeing giant white rectangle in dark theme is not very nice). What I have done is moved the background color setting to `surface clear:` (instead of the original aCanvas fillRectangle). And then if theme background luminance is dark (>0.5), I invert all the colors in the visualization. For dark theme the background is black, and not the theme background - at least to me it seems that black is much clearer. Is this something that could be incorporated? And the modified code: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "protocol: drawing" TRMorph>>drawOn: aCanvas "aCanvas is a FormCanvas" self checkSession. "aCanvas fillRectangle: bounds color: trachelCanvas color." trachelCanvas playAnimations. "The drawing has to be done when a change in the shapes occured or when there is an animation." surface drawDuring: [:cs | surface clear: trachelCanvas color. "We display the elements that are subject to the camera" cs pathTransform translateBy: (self extent / 2) asFloatPoint; scaleBy: trachelCanvas camera scale asFloat; translateBy: trachelCanvas camera position negated asFloatPoint. trachelCanvas shapes do: [ :trachelShape | trachelShape drawOn: cs. ]. "We display the elements that are _NOT_ subject to the camera" cs pathTransform loadIdentity scaleBy: 1.001. trachelCanvas fixedShapes do: [ :trachelShape | trachelShape drawOn: cs. ]. ]. self theme backgroundColor luminance < 0.5 ifTrue: [ surface drawDuring: [ :cs | cs paintMode restoreAfter: [ cs setPaint: Color white. cs paintMode difference. cs drawShape: (0 @ 0 extent: surface extent) ] ] ]. "aCanvas translucentImage: surface asForm at: self bounds origin." "asForm creates a new Form, which is likely to be expensive. This can be cached" aCanvas image: surface asForm at: self bounds origin sourceRect: (0 @ 0 extent: surface extent) rule: 34. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

4 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev February 2016