Hi,
The job for Moose 6.0 is randomly stuck (https://ci.inria.fr/moose/job/moose-6.0). It is the second time I had to stop the build.
I installed a plugin (Build timeout) to abort the build automatically after 30 minutes (which certainly a lot...).
However, the root cause should be identified and fixed...
Cheers,
Vincent
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Is it possible/planned to change multiple GTInspector tabs at once?
For example:
​
I would like to click on the next item in the leftmost pane, but keep the
middle and right panes opened, just update the data to reflect the newly
selected item.
I imagine there could be a "pin" button on each tab that would keep it open
or something, but maybe that would not be easy to implement.
Thanks,
Peter
Hi,
I moved Glamour to Rubric, deprecated those presentations that use
PluggableTextMorph and moved almost all usages of presentations that rely
on PluggableTextMorph.
These changes are still only in the Moose branch to see if there are any
ugly bugs.
The changes to the glamour API are the following:
- deprecated #smalltalkCode, #pharoPlayground and #rubricText
- added #pharoScript
If you use #smalltalkCode replace it with either #pharoMethod or
#pharoScript
If you use #rubricTest replace those usages with #text
If you use #pharoPlayground replace those usages with #pharoScript (we
changed this as the glamour playground is not the same at the GTPlayground
and this was causing some confusion)
For this I also renamed GLMPharoPlaygroundPresentation to
GLMPharoScriptPresentation and GLMMorphicPharoPlaygroundRenderer to
GLMMorphicPharoScriptRenderer.
If you are using the latest moose let me know if you run into any problems
or have questions.
Cheers,
Andrei
Hi,
For preparing my teaching course I would have love to have simple class hierarchy visualisations or even better, real UML representations.
Unfortunately, the UML like diagram from the Moose panel is not zoomable. It is by default in light grey saying that it is harder to read. It contains all the attributes and all the methods so it is difficult to put it in a single readable picture. Please make the experiment with the Famix-Core classes.
I was not able to do easily a class hierarchy with the name of the classes. After more than one hour, I gave up.
So it could be good, if we can have:
- a class hierarchy with only the names of the classes in boxes or not
- a class hierarchy with only attributes
- a class hierarchy with only methods
- the existing "UML" representation
- a real metamodel representation. Not as a system complexity representation, but as a real UML representation meaning with inheritance AND associations (those can be deduce from pragmas and now with the new MooseQuery API, we get all the methods to do it).
It should be possible to easily specify which classes we want to represent.
It seems to me the minimum vital to do real analyses.
In my course, I wanted to show I extended FAMIX for SQL purpose. It was so complex (because I don’t want not all FAMIX entity, but just the one from which the SQL classes inherit and without the methods) that once again I gave up.
I don’t have enough time to better look for. But anyway, I find it sad that it is so hard even for people knowing (a bit) Moose of not being able to do that.
Cheers,
Anne
Hi!
Recently I did a refactoring of the actions in GLMRoassal2Presentation. But now the Moose Panel cannot zoom in / out. Any idea?
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am currently preparing a teaching course for next week (sorry, the support will be in French) explaining to the students what is a metamodel and how to create a new one with Moose.
For this purpose, I have to explain how to create properties in Famix.
For example:
<MSEProperty: #name type: #String>
<MSEComment: 'Basic name of the entity, not full reference.’>
What are the accepted primitive types String and what else?
It seems that Integer is not accepted. And what about Date or DateAndTime?
In fact it seems that only String is accepted.
In my case, the svn log metamodel, a Commit has a revision number (Integer) and a date (DateAndTime).
Is there something I am missing?
Thank you in advance for your help.
Anne
Hi!
When browsing examples, I have code highlighting when looking at the source of an example, but in the playground I do not have the highlighting.
Any idea how to fix that?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
[NB: forwarded to the moose mailing list as other may be interested in this]
Hi Thomas,
This is a tricky situation, for which I have found a solution.
Consider the script
-=-=--=-=--=-=--=-=-
b := RTGrapher new.
d := RTData new.
d points: #(3 4 5).
d barShape.
b add: d.
b axisX noLabel; noTick.
b
-=-=--=-=--=-=--=-=-
produces
As always.
You can now send #noAlignmentOffset to the data to remove the offset.
-=-=-=-=-=-=
b := RTGrapher new.
d := RTData new.
d points: #(3 4 5).
d barShape.
d noAlignmentOffset.
b add: d.
b axisX noLabel; noTick.
b
-=-=-=-=-=-=
produces:
It is visually less appealing, however it works well when you combine it with other data sets:
-=-=-=-=-=-=
b := RTGrapher new.
d := RTData new.
d points: #(3 4 3.5).
d barShape.
d noAlignmentOffset.
b add: d.
d := RTData new.
d points: #(3 4 3.5).
d connectColor: Color red.
b add: d.
b
-=-=-=-=-=-=
This is committed in Pharo
Alexandre
> On Oct 15, 2015, at 7:27 AM, Thomas Brodt <thomas.brodt(a)porabo.ch> wrote:
>
> Hi Alexandre, hi Milton
>
> today I upgraded to the new version 2.35 of Roassal for Visualworks. It gets better each time!
>
> Unfortunately we have an issue with the new RTData. As the old RTStackedDataSet is obsolete now, we moved all our charts to RTData.
>
> In some charts where we have bars mixed with lines, the dots of the line graph are no longer aligned with the center of the bars, as it was before with RTStackedDataSet. If I change the RTData for the line graph to RTStackedDataSet, the alignment works again.
>
> Here is an example script:
>
> | b ds |
> b := RTGrapher new.
> ds := RTData new.
> (ds barShape)
> width: 15;
> if: [:v | v < 0] fillColor: Color red;
> if: [:v | v > 0] fillColor: Color green.
> ds points: #(5 -6 10 20 -9).
> b add: ds.
>
> ds := RTStackedDataSet new.
> ds
> points: #(4 -2 11 16 -10);
> connectColor: Color red;
> connect.
> ds dotShape color: Color blue.
> ds lineShape color: Color blue.
> b add: ds.
>
> ds := RTData new.
> ds
> points: #(4 -2 11 16 -10);
> connectColor: Color red;
> connect.
> ds dotShape color: Color red.
> ds lineShape color: Color red.
> b add: ds.
>
>
> (b axisX)
> noLabel;
> noTick.
> b axisY noDecimal.
> b build.
> b view
>
>
> In the example, there are two lines with the same values, one using RTData, and one using RTStackedDataSet. And they have different positions, while I think they should be aligned.
>
> Maybe you can have a look at that?
> Thanks,
>
> Thomas
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Roassal2 adds ClassDescription>>classReferences which references
CompiledMethod>>classReferences but the latter method does not exist.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
