Hi,
I just wanted to say: thank you. In particular, I would like to thank the newcomers in our community.
For those that are a bit overwhelmed with the speed of things, here is an incomplete summary of valuable contributions from newcomers:
- Juraj is almost done porting Mondrian visualizations to Roassal
- Daniel is working on the Graph-ET project which will migrate EyeSee onto Roassal
- Mathieu built excellent layouts
- Chris started to join Yuriy and work on PetitJava unexpectedly and enhanced the AST
- Andrei is working on exciting Glamour and GToolkit features
- Vincent just joined us
Cheers,
Doru
--
www.tudorgirba.com
"Things happen when they happen,
not when you talk about them happening."
Hi
We speak with Tudor about mixing layout, and here is something
I try.
====================================
| view rawView |
rawView
:= ROView new.
view := ROMondrianViewBuilder view:
rawView.
"-------------"
"-------------"
view shape rectangle
borderColor: (Color white).
view nodes: ROObject withAllSubclasses
forEach: [ :each |
view nodes: each withAllSubclasses .
view
edgesFrom: #superclass.
view layout: (ROTreeLayout new horizontalGap:
4) .
].
view layout:( RORectanglePackingLayout new ratioWidth: 100
height: 100 ).
"-------------"
"-------------"
"Below is the
initiation of the menu and opening the visualization"
ROEaselMorphic new
populateMenuOn: view.
view open
=======================================
So, it seems it can be done
with not too long a script.
Regards
Math
Hi Doru,
I have made new package called Moose-Tests-CycleTable. Please, can you add
it to the configuration of Moose? It is commited in Moose/DSM/main
Thank you a lot,
Jura
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 941 by v.blonde...(a)gmail.com: Can't export moose model to MSE
file from pharo 2.0
http://code.google.com/p/moose-technology/issues/detail?id=941
When calling export to MSE from Moose Panel, exporting to a file doesn't
work.
--
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!
First, should I move methods #viewAnnouncements, #viewSketch, #viewTree of
GLMBrowser intro Roassal?
Second, how can I use this tool and these methods? Can you give me an
example?
Thank you,
Jura
Hi
I've been modifying ROAbstractCompactTree, and RadialTreeLayout
so that they take nodes size into account. (it's not yet finished for
radialtreelayout)
But I do not have the right to commit on Roassal
package.
Do I put them in RoassalAlgorithm again ? And you move them
after.
Regards
Math
Hi!
I have transformed DSM, DSM Numbered, Dependencies (cycles), Mini Cycle
Table, Number DSM, enriched Cycle Table, Cycle Table, enriched DSM, encaps
DSM into Roassal.
I would appreciate if someone can revise it.
Cheers,
Jura
Hi
I've fixed a big on ROArc, so that it draws well.
And I've
commented and added methods to RORectanglePacking to reduce biggest
nodes, and so on.
try:
Gofer new
smalltalkhubUser:
'MathieuDehouck' project: 'RoassalAlgorithm';
package: 'Roassal-New';
load
| view rawView n b |
rawView := ROView new.
view :=
ROMondrianViewBuilder view: rawView.
"-------------"
"-------------"
b
:= 30.
view shape rectangle
width: [ :cls | cls numberOfVariables *
5 ];
height: #numberOfMethods;
color: (Color r: 0 g: 1 b: 1 ).
view
nodes: TestCase withAllSubclasses.
view nodes do: [ :e | (e width > b
) ifTrue: [ e shapes first color: (Color r: 1 g: 0 b: 1 ) ] ].
view
layout:(( RORectanglePacking new)ratioWidth: 10 height: 10; padding: 4;
logWidthIfMoreThan: b scale: 5).
"-------------"
"-------------"
"Below
is the initiation of the menu and opening the
visualization"
ROEaselMorphic new populateMenuOn: view.
view open.
There are other log... methods, and scale represent the factor to
multiply the logs by. (yes log 10 = 1 and that's pretty small in pixel)
Regards
Mathieu
P.S. The screens have been made with the width and
the height in the same time.
Hi,
The Glamour tests are temporarily red:
https://ci.inria.fr/moose/job/glamour/lastCompletedBuild/testReport/
The reason is that Andrei and I started to work on a couple of new rather
cool features for Glamour. The engine works fine (only the tests require
changes now), and although the changes are quite deep, they are backward
compatible. More details will follow.
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"