Hi,
I’ve just downloaded roassal2 image from https://ci.inria.fr/moose/job/roassal2/ <https://ci.inria.fr/moose/job/roassal2/>. Problem is next.
On the CI server Roassal2 is loaded into Pharo3 image. But if you open it, there are some problems, as GT inspector is not present there. I could just make it to load into pharo 4 image, or make a matrix job. But I want to rise attention, because this is a sign that roassal conf. loads broken things…
Uko
Hi!
I played a bit this morning. This is the whole Pharo:
A detail of this picture:
There are over 100 000 methods and over 65 000 edges.
Each circle is a method. Color of the method indicates its class. Edges are self-call between methods (e.g., a method "foo ^ self bar” will creates a link between #foo and #bar.
The very short script to produce it and a large version of the pictures are available on: https://www.facebook.com/ObjectProfile/posts/742756179144315
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am executing disharmony codecity example with the properties #isGodClass,
#isBrainClass and #isDataClass. However, the properties return Nil and in
the documentation we have: return nil if the property does not exist. I have
some questions:
1- Where these properties are calculated? I have not found!
2- Where can I find the list badsmells implemented in codecity?
3- I would like implement new properties for disharmony codecity, Where to
start?
My test code is this:
Thanks!
--
View this message in context: http://forum.world.st/Disharmony-codecity-example-The-properties-return-Nil…
Sent from the Moose mailing list archive at Nabble.com.
Hi,
Despite of my advances studying Glamorous Toolkit and making some
advances on "apps" and interfaces, I really don't understand well the
concept of ports and auto-update of values. So I started with a small
excercise from the transcript example as proposed in the GT blog[1]. Its
working as expected, so try to extend the example with a code that shows
my incomplete understanding at [2]. My idea was to create a two panels
browser showing an array. Left panel show a list, and right one was a
text with the selected value of the list. When the values at the right
were updated the list at the left was updated also. Because this was not
working I create a Transcript trying to show if changes on the right
where captured. I have seen the three inter-dependant panes example,
but still I don't get it right. So my questions are:
[1] http://ws.stfx.eu/L277ESMZYIF3
[2] http://ws.stfx.eu/1FOA0OWJ8PWA
a) How can I send the changes in values from the right panel to the one
of the left?
Thanks,
Offray
Hello
RTZoomableView should enable zooming with mouse wheel. It works fine on
Linux, not tested on Mac, but doesn't work for me on Windows (mouse wheel
does nothing). For example, this one:
RTRoassalExample new exampleScrollZoom
Jan
--
View this message in context: http://forum.world.st/Roassal2-RTZoomableView-not-working-on-Windows-tp4786…
Sent from the Moose mailing list archive at Nabble.com.
Dear All,
Over the last few weeks, we have worked on a new Mondrian builder.
Look for the class RTMondrian.
The new Mondrian is faster than the previous Mondrian (in Roassal2) and supposedly contains less bug.
In this builder, the syntax slightly changed. However, the migration is fairly trivial.
Before you had to write:
-=-=-=-=-=-=-=-=-=-=-=-=
b := RTMondrianViewBuilder new.
b nodes: (1 to: 5).
b edgesFrom:: [:v | v + 1].
b treeLayout.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=
Now, you will write:
-=-=-=-=-=-=-=-=-=-=-=-=
b := RTMondrian new.
b nodes: (1 to: 5).
b edges connectFrom: [:v | v + 1].
b layout tree.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=
As you can see, edges and layout are defined slightly differently. There are good reason for this. I foresee the fact that should be able to build some more elaborated and expressive line and layout. For example, we should be able to say we want edges that are taken into account by the layout or not. Or providing control points, or conditional instruction. For the layout, same things, we may want to partition (e.g., elements with edges using a particular layout, and isolated elements in a different locations). Behind the scene, we will have edge and layout builder. Maybe in the future we will have node builder as well… No idea for now :-)
Also, the default shape builder has also changed. Let’s see if you guys can live without a border color :-D
Anyway, I recommend to try out this new Mondrian builder and report for bugs and wanted features.
Also, we will soon deprecate the RTGraphBuilder, since this new Mondrian builder will do much more than what RTGraphBuilder offers. RTGraphBuilder was a very nice experiment, and we learned a lot from it. Now, it is time to capitalize and push Roassal further!
We also have other cool stuff coming. Have you noticed the HTML exporter? :-D
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
A new builder, part of Charter is now in!
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
b := RTDoubleGrapherBuilder new.
b extent: 300 @ 200.
ds := RTStackedDataSet new.
ds points: #(4 3 2 2).
ds barShape width: 40.
b add: ds.
ds := RTStackedDataSet new.
ds points: (10 to: 13).
ds dotShape color: Color blue.
ds connectColor: Color red.
b addRight: ds.
b axisXNoLabel; axisY.
b axisConfiguration color: Color red.
b axisYRight.
b build.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1097 by nicolaih...(a)gmail.com: Not all shapes support
borderColor/borderWidth
https://code.google.com/p/moose-technology/issues/detail?id=1097
Some shapes are using the default stroke and/or the default stroke width,
even if the user sets a borderColor/borderWidth
|v ver circle box poly es |
v := RTView new.
ver := (1 to:5)collect:[:i | Point r:100 degrees:(360/5*i)].
circle := RTEllipse new size: 200; color: Color red;
borderWidth:5;borderColor: Color green.
box := RTBox new size: 200; color: Color red; borderWidth:5;borderColor:
Color green.
poly := RTPolygon new size: 200; vertices:ver; color: Color red;
borderWidth:5;borderColor: Color green.
es := circle elementOn:'hello'.
v add: es.
es := box elementOn:'hello'.
v add: es.
es := poly elementOn:'hello'.
v add: es.
v @ RTDraggableView .
RTGridLayout on: v elements.
v
"all shapes should use the provided borderWidth (5) and borderColor (Green)"
moose build 3147
* Type-Defect
* Component-Roassal2
Attachments:
shapes.png 11.5 KB
--
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
Hi,
I put my java source code directory in the root folder of the infamix. At
execute the command to generate MSE file, the infamix throws the
NullPointerException while processing a class.
The MSE file is generated, but I dont know if this can to cause problems in
the model.
What is the cause this problem?
--
View this message in context: http://forum.world.st/inFamix-throws-NullPointerException-error-at-generate…
Sent from the Moose mailing list archive at Nabble.com.
Hi Alex,
In Eyesee, we have the concept of composite diagrams i.e. you can have
multiple charts in the same diagram with individual y axes (see attached
screenshot). This is a handy concept because not only you could have two
charts on the same diagram but each chart has its own axis. For comparing
disparate values, this is convenient because one does not need to think
about normalizing Y values of charts to the same scale. One example could
be showing trends of software metrics over time.
I saw that you ported more code from Charter to Grapher so I am having a
look at the examples. Is it possible to have composite chart diagrams with
Grapher? Do you plan to add this feature?
Here is a exemplary script that illustrates the need for composite diagrams:
| grapher minDate ds random dates grapherBlock|
dates := (Array with: Date today with: Date yesterday with: Date tomorrow)
collect: #asDateAndTime.
minDate := dates min.
random := Random seed: 10.
grapher := RTGrapherBuilder new
extent: 300 @ 200;
yourself.
grapherBlock := [:index |
ds := RTDataSet new.
ds interaction popup.
ds dotShape ellipse color: (Color red alpha: 0.5); size: 10.
ds points: dates sorted;
x: [ :aDate | aDate asUnixTime - minDate asUnixTime ];
connectColor: (Color random alpha: 0.5);
y: [ :d | (random nextInt: 100) * index].
grapher add: ds].
100 to: 103 do: grapherBlock.
1 to: 3 do: grapherBlock.
grapher axisConfiguration noDecimals.
grapher axisY.
grapher axisConfiguration
labelRotation: -30;
title: '';
numberOfLabels: dates size - 1;
labelConvertion: [ :v | (DateAndTime fromUnixTime: v + minDate asUnixTime)
asDate ] .
grapher axisX; build.
grapher view open
regards,
Usman
[image: Inline image 2]
[image: Inline image 3]
[image: Inline image 1]