Hi,
I tried to look in the the failing build problem, but I could not solve it.
Somehow the Moose-Tests-Core.xml is incomplete on the build server.
I tried to reproduce the problem locally, but I did not manage with this
code:
MooseTestCommandLineHandler activateWith: (CommandLineArguments
withArguments: {'--junit-xml-output'})
This should be the correspondent of:
./pharo $JOB_NAME.image moosetest --junit-xml-output
Could anyone else try as well?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi folks,
I am Pablo Estefó an ObjectProfile engineer and I will continue the excellent work of Daniel Aviv on Graph-ET (on Roassal2).
I’ve just added the “oblique” labels feature(for Roassal2’s GraphET version only). And the result is something like this:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETRotatedLabelDecorator new diagonal numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
It produces:
If we change the rotated label as diagonal inverted:
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETRotatedLabelDecorator new diagonalInverted numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETVerticalLabelDecorator new numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Vertical labels
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
| diagram |
diagram := GETDiagramBuilder new.
diagram horizontalBarDiagram
models: #(0.2 0.5 2 0.3 0.51 1);
color: [ :x | x <= 0.5 ifTrue: [ Color blue alpha: 0.2 ] ifFalse: [Color blue alpha: 0.5]];
valueAxisLine;
baseAxisLine;
addValueDecorator: (GETRegularTickDecorator new numberOfTicks: 5);
addValueDecorator: (GETVerticalLabelDecorator new inverted numberOfLabels: 5).
diagram open
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
I am thinking a succinct way to specify it.
Well, as you can see the axis configuration will get more complex the more options we can provide.
So our next question to drive our development is:
How can we get the richest input in order to interpret it and return the best plot with the minimum configuration input.
I would like to know your opinions to develop a better Graph-ET :-)
Cheers,
Pablo
Hi everybody,
I have created a large FAMIX 3.0 file using InFamix form the wildfly (a.k.a. JBOSS) aplication server.
This file is about 142 MB large with 7 853 171 lines.
Importing that MSE file into Moose 4.9 (with pharo) on Windows and MacOS with 8GB RAM fails due to out of memory.
Is there an easy possibility to increase the the memory of the VM? I have only found some older postings talking about recompiling the VM.
Thank you very much
Thomas
Is it possible to provide objects instead of labels for the widgets in
Merlin? I am particularly thinking about MultiCheckboxesPart so that it is
provided with some objects and it shows their labels. Later, I would like
to get the user selection object instead of a label.
Currently, I only know how to provide labels and once user chooses (e.g. a
checkbox, i only get the selected label) and then I have to keep a
dictionary to determine the corresponding selector. Ideally, we should
provide an object along with a selector to get the labels/other properties
to be displayed.
May be something to take up at the upcoming sprint.
regards,
Usman
Hi!
The Moose image offers much more than offering moose. For example, I have a postdoc working on Astronomy images and she is using the moose image not because of moose, but because of what is shipped with it.
Does something who is not interested in analyzing software may find the moose image useful? The answer is absolutely yes.
What about changing the name of the Moose image into something closer to what it really offer?
Maybe Pharo4Modelling ? PharoModellingEdition?
I think this discussion is important.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
In March we will start our lecture about Pharo and Moose. We will give to each student one or two small projects to work on during the semester. We went through the site http://topics.pharo.org to have some ideas.
Is there anything you would like to see that is not on the topics website?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
