Hi all,
I just want to share a post made on the Open Knowledge Foundation Forum
talking about what we're doing in our local community to celebrate the
Open Data Day:
https://discuss.okfn.org/t/our-poryect-and-hackathon-workshop-for-the-open-…
Pharo, Roassal and Moose will be an integral part of our celebration. As
I said in the link, we're going to try some treemapping techniques. I
know about Quick Silver, but if any has some other advice, is very
welcomed.
Probably I will be making some questions here and in the chat channel
regarding treemapping and some SQLite queries to get the proper info, so
I'll keep you posted on how our pharo powered workshop/hackathon for the
celebration of the Open Data Day advances.
Cheers,
Offray
Already publicized on Facebook and Tweeter. Since there are not many emails these days, here it is:
Script of the day: visualizing dependencies between FAMIX classes and methods. Here is an example with SweetHome3D, a java application
-=-=-=-=-=-=-=-=-=-=-=-=
methods := self flatCollect: #methods.
b := RTMondrian new.
b shape rectangle withTextAbove.
b nodes: self forEach: [ :cls |
b nodes: cls methods.
b layout grid.
].
b shape line
color: (Color red alpha: 0.2); width: 3.
b edges
objects: methods;
connectToAll: [ :m | m queryAllOutgoingInvocations atMethodScope ].
b layout circle .
b
-=-=-=-=-=-=-=-=-=-=-=-=
The script has to be executed on 'all model classes', within the moose panel.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/>
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I have produced:
GT-Inspector-AlexandreBergel.389
That replace:
GTExampleImpostorPragma>>= aImpostorPragma
^ self class = aImpostorPragma class
and: [ self method = aImpostorPragma method ]
by:
GTExampleImpostorPragma>>= aImpostorPragma
^ self class == aImpostorPragma class
and: [ self method == aImpostorPragma method ]
Performing #= between methods is pretty expensive and I see no reason why classes have to be compared with #= and not #==
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
---
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
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
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
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