Jannik rang the alarm bell. We are slower than in January ( 1600 nodes
=> 28 ms, 300 edges => 35919 ms), but we have a slightly better test
coverage.
I will dig into it.
Report produced on 2010-04-06T09:37:41+00:00
Benchmark ManyNode (simple rendering of nodes) :
100 nodes => 4 ms
200 nodes => 8 ms
300 nodes => 10 ms
400 nodes => 14 ms
500 nodes => 17 ms
600 nodes => 22 ms
700 nodes => 25 ms
800 nodes => 27 ms
900 nodes => 31 ms
1000 nodes => 35 ms
1600 nodes => 55 ms
Benchmark ManyEdges (simple rendering of edges) :
10 edges => 2 ms
20 edges => 10 ms
30 edges => 24 ms
40 edges => 45 ms
50 edges => 99 ms
60 edges => 142 ms
70 edges => 205 ms
80 edges => 402 ms
90 edges => 552 ms
100 edges => 744 ms
200 edges => 12463 ms
300 edges => 134138 ms
60.6 % of methods are covered
Progress from last time: +5.82 %
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
When importing smalltalk code in Moose, the method 'belongsTo' for a class
always refers to the namespace 'Smalltalk', and never to its package.
Is it something wanted ?
Hi,
I added a new feature in Glamour: the ability to add a status bar that
displays a simple label for some object. At the moment it only works
by default with Mondrian views, but it could have further usages.
To use it all you have to do is to send withStatusbar instead of new
to your browser. This will create a fix size pane at the bottom called
#'_statusbar'. By default, there is a transmission from the #status
port of each regular pane to this one, and so every time you populate
a port called #status in your pane, a text representation will appear
in the status bar.
You can find a simple example for Mondrian here:
GLMBasicExamples new mondrianPainting openOn: 100
I also added a small extension, MOViewRenderer>>openWithStatusbar,
that lets you spawn any Mondrian view with a status bar below.
There will be some more developments in this area, but the basic idea
is implemented.
Cheers,
Doru
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of
problem understanding."
Hi All,
Just to give some news about Mondrian. Together with colleagues from
Bern, Lille and Santiago, I have been working on this visualization
engine for quite some times. Although it contains some important bugs
(e.g., popupView) it is fairly stable and usable. The current version
is 2.0-beta.7.
Mondrian is slowly maturing. A short summary of the discussion I had
with Doru and Stéphane today.
Some of the features I would like to see in for Version 3.0 are:
- scalable spring layout (also known as force based layout): this
is a very simple and nice layout that produces amazing results
- add layers: embedding a rendering or a part of it in a layer.
Layers could then be iteratively activated and desactivared. The idea
is to enable the construction of scripts in a very iterative and
incremental way.
- having a small core embeddable in your application
- making Mondrian load graphiz scripts
- having a better help system (à la ProfStef)
- dedicated chapter for Pharo By Example Volume 2
- exporting as PDF
- anti-aliasing
This probably will not happen today or tomorrow, but I just feel
necessary to share this roadmap with you. Some other features are
wanted. Using Rome is one. Open GL is another. There are plenty of
rooms for a very cool visualization engine.
Probably during the holiday period I will consolidate the current
version by fixing remaining bugs and produce 2.0.
Bug tracker: http://code.google.com/p/moose-technology/
Web page: http://www.moosetechnology.org/tools/mondrian
Let's render our dream!
Cheers,
Alexandre
NB: sorry for this cross mailing list post.
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
I don't remember if I already told you:
I've started to build an OverviewPyramid visualization. I saved it in
the package Moose-
MondrianPaintings-OverviewPyramid. You can test it by right-clicking
on a moose model (from the
moose panel).
I've based the metrics computation on the book 'Object-oriented
metrics in practice'.
Hi,
As the subject suggests I'm trying to install Moose on the latest
image of Pharo
available on the website.
Even though I follow the instruction and I do first:
DEVImageWorkspaces openExternalProjectWorkspace
then, on the new window, I do:
Gofer new
squeaksource: 'Moose';
package: 'ConfigurationOfMoose';
load.
(Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault.
After some time, after installing some components,
the procedure is blocked trying to compile something
(maybe something related to: MOFeatureCollection>>hausdorffDistance).
You can see a screenshot of the exact point here:
http://www.inf.usi.ch/phd/bacchelli/Screenshot.png
I am trying to use Pharo on a 32-bit Debian Linux
(testing with kernel 2.6.32-3-686), on a HP Mini 5102 netbook.
Could you please give me some suggestions on
how to solve this blocking problem?
Thank you in advance,
Alberto
Hi All,
I have a swing.mse that loads in Moose. Anyone is interested in this?
It was easy to produce by the way, but since we talked once about
getting a public repository for case study...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
You can try:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
view shape diamond height: 30; width: 15; fillColor: Color lightBlue.
view nodes: (1 to: 10).
view shape triangle height: 30; width: 15; fillColor: Color lightGreen.
view nodes: (1 to: 10)
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Some of you were a bit bored of having rectangle and ellipse :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I gived a first try and start to build the wizard and the
DistributionMap itSelf.
I put all my classes in the package Moose-MondrianScripts (is it a good idea?).
So, by dowloading the last version of this package, you will be able
to test it by right-clicking on a
FAMIXClassGroup in a MooseFinder
(For the moment, I have only added a menu item to FAMIXClassGroup, but
this visualization could be applied
on any kind of element)
I fill-in the default inputs of the wizard with a working example, so
that you can see how to use it.
Just tell me if it looks like to what you were expecting, what would
you change?, what would you had?, any
suggestions?
The visualization itself is not yet well-implemented. I'm going to do
that now :)
