Hi all,
I wanted to try Hapao to see the quality of the tests we have in LRP but I cannot get it to work. I looked at the instructions on http://objectprofile.com/Hapao.html
- the one-click is a Pharo 1.2 version, that’s much much too old to be able to load LRP
- In the latest moose 6.0 executing ConfigurationOfSpy loadDevelopment produces an error
- in the latest LRP (based on Pharo 5 pre-spur) I can load Hapao but it throws up a lot of warnings during the load. Furthermore nothing works like in the ‘how to use’ part on the page.
What is the status of Hapao? How can I use it to have a look at my tests?
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
Hello guys,
thanks for the support so far. I've been working on your suggestions.
Some of them concerned that the example in the first demo video was too
"magic". :-P
So I made another video showing how the developer can manually configure
the tool.
Take a look: https://youtu.be/3xc3j3PjIYQ
( first demo here: https://youtu.be/gW3l4O-WEGs )
Also, I kindly remind you that I'm interested in usage data:
- if you systematically modified code in the past, show me.
- if you created a custom transformation with the tool, show me; or
- if you had problems using the tool, show me too! :-)
Feel free to provide any feedback.
Cheers,
--
Gustavo Santos
http://gustavojss.github.io/
Hi!
The Pharo 5.0 (and therefore Moose) cannot be open with the last VM available on pharo.org.
I think that if the image can only be run on Spur, Spur should be available.
So, where to get Spur?
Here: ?
https://ci.inria.fr/pharo/view/5.0-VM-Spur/job/PharoVM-spur32/375/Architect…
I have tried Roassal on Spur, and text cannot be displayed properly.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am improving the Dashboard of Synectique and I see that GLMDashboard
use extents in order to build a browser.
I was thinking of removing this and use layout instead. Using layout we
would have more freedom and we would not have any problem with the
resizing of the window that can let grey area for now.
This will not be backward compatible so I prefer ask to the mailing list
if someone is against this change. Should we keep this change inside the
synectique tools or push it to Moose ?
--
Cyril Ferlicot
http://www.synectique.eu
165 Avenue Bretagne
Lille 59000 France
Hi everyone,
Is there a pdf version of the moose book? for I have students in Algeria for whom it is not always easy to access the online version.
Thanks in advance.
Abdelghani
Hi,
I created another little poll about the importance of architecture.
If you have a Twitter account, feel free to participate:
https://twitter.com/girba/status/675330047608299521
Cheers,
Doru
--
www.tudorgirba.com
"Things happen when they happen,
not when you talk about them happening."
Hi,
I put together a very simple poll on code reading. I kindly ask you to participate. It should take you 30 seconds to answer it:
https://twitter.com/girba/status/674339247046991872
Cheers,
Tudor
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
Hi!
I have found a nasty situation that may occurs when using composite shapes.
Consider the following script:
[ b := RTMondrian new.
b shape box size: 30; color: Color red trans; withText.
b nodes: (1 to: 20).
b edges connectFrom: [ :v | v // 3 ].
b build.
RTForceBasedLayout new
"doNotUseProgressBar;"
on: b view elements.
b view] timeToRun
=> 0:00:00:10.386
[ b := RTMondrian new.
b shape box size: 30; color: Color red trans; withText.
b nodes: (1 to: 20).
b edges connectFrom: [ :v | v // 3 ].
b build.
RTOptimizedForceBasedLayout new
"doNotUseProgressBar;"
on: b view elements.
b view] timeToRun
0:00:00:00.387
Yes, on this example, the class RTOptimizedForceBasedLayout is 33 faster than the traditional layout.
The problem is that translating a composite shape is much slower than translating a non-composite shape. I have created mock elements and mock edges. That is a good news :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
Some time ago I asked about how to make some kind of matrix sunburst,
like the one on [1]. Thanks to the help of the community, specially
Milton we're almost there. Look at this:
[1]
http://www.theguardian.com/world/interactive/2012/may/08/gay-rights-united-…
Now I would like to locate better the labels for each country, ideally
at the center of each arc. The important part of message which is making
this is here:
=================
PublishedMedInfo>>addLineSeparatorsTo: aView withData: data
separatedBy: aDistance centerSized: aSize
| e1 e2 ang cos sin radio label countries |
label := RTLabel new
height: 16.
countries := self medDataMatrix at: 1.
1 to: data children size do: [ :i |
e1 := (RTBox new size: 1) element.
ang := ((i - 0) * 360 / data children size) degreesToRadians.
cos := ang cos.
sin := ang sin.
radio := aSize.
e1 translateTo: (radio * cos)@(radio * sin).
e2 := (RTBox new size: 1) element.
radio := self arcWidth * 30 + aSize.
e2 translateTo: (radio * cos )@ (radio * sin).
label text: (countries at: (countries size + 1 - i)).
aView
add: e1;
add: e2;
add: (RTLine new width: aDistance; color: Color white;
edgeFrom: e1 to: e2);
add: (label element translateBy: (((radio - 70) * cos)"-
15" )@ (radio - 70 * sin) "+ 15")
]
=================
as you can see the e1 and e2 edges are the ones that create the
separation between columns in the matrix sunburst and are computed
inside an iterator. I would like to keep a temporal edge that stores the
value of the e2 edge in the previous run and locate the label in the
coordinates between actual e2 and the previous one (lets call it
"edgeTemp"). How can I do this?
Thanks,
Offray
Ps: I have subscribed this new direction because my previous one is
failing tonight. Probably I will unsubscribe the previous and keep this
one for Pharo and Moose mailing lists.
