Dear Moose community,
In the past two years, I have been working on 3D visualization of
software. During this time I developed a tool called CodeCity, built
on top of Moose.
In CodeCity, software systems are represented as cities. Some of you
may have seen a demo of CodeCity during ESUG 2007 or at the Moose Dojo.
However, not many of you have played with it yet. Let's change that!
You can download CodeCity at:
http://www.inf.unisi.ch/phd/wettel/codecity.html
I would appreciate your feedback and use it to make the next release
of CodeCity better.
Cheers,
Ricky
Hi,
We are pleased to announce that a new edition of FAMOOSr (Workshop on
FAMIX and Moose in Reengineering) is going to be organized together
with TOOLS 2008.
The workshop will be a 1 day event and will take place at the end of
June or beginning of July. The exact day will be announced later.
The deadline for submissions of either experience reports (4 pages) or
position papers (2 pages) is: May 5.
More information can be found at:
http://moose.unibe.ch/events/famoosr2008
Cheers,
Doru, Orla and Michele
stef,
My question means that : how can i extract the informations from mse
file? Is it possible to use this format like a moose model in
implementation? Is it possible to do something like: anMseFile allClasses?
thanks,
Azadeh
Hi,
I would to use ArrowShape for some edges but I did not succeed yet :-(
I specified the edges shape like that:
...
using: (ArrowShape goofy)
but that did not work, how we can visualizing edges as arrow and how
we can specifying the direction of the arrow (ex: #atEnd #atStart).
thanks,
hani
Hi,
In some visualization I need the CircleLayout. But the pb in the
actual implementation of this layout that some nodes could appear over
(or very very near of) some other nodes; while some other nodes
appear with a very high distance from the rest (see the attached
picture). This way visualizations does not scale well and we have the
pb of overheads.
In the attached picture I specified the layout as following: view
circleLayout scaleBy: 50.
If I increase the number of scale the view will be very very large and
if I decrease it we will have a lot of overheads.
Could we do something for ameliorating this layout?
do you know an another layout that work well for cases that we could
have ad-hoc edges between a large number of nodes? (I tested the
ForceBasedLayout and unfortunately it does not work well for such a
case as in the attached picture)
best wishes,
hani
Hi
I have two question, thanks to help me.
1)
I know that the MSE format allows to specify models for import and
export with Moose. My question is that how I can import the MSE format
as a model in the code not in Moose tool. I need to import different
versions of Moose as an input model in my system that is based on Moose
and my model is a MooseModel. I import my Moose model as the bundles
like this:
^ Model5 addEntity: (SCG.Moose.PundleImporter new model: model5;
addBundleNamed: 'Moose';run).
2)
Is there any possibility to understand, in existed Moose architecture,
what are the classes or packages in the different components. For
example, what are the classes in Meta Description or in Meta Model?
Do you know any work on Moose Architecture that explain the notion of
entities in the components?
Thanks,
Azadeh
Helo,
I would use Mondrian.DistributionMap that you have recently
implemented, but the pb that I had is:
-each distributed entity has at less two properties (let us imagine:
'first property'->'fill color darkness' and 'second property'->'border
color darkness').
-in some models may be we will have more than two properties to map:
we can have 4, 5, etc. of properties but in the same time any given
entity could not be attached to more than two properties (in other
words we need to mapping different properties to different colors).
-could we have the possibility to use different shapes for the
distributed entities (some entities are boxes while some others are
ovals).
Now could you, please, tell me how to improve the actual
implementation of distribution map? may be we should implement a new
distribution map, what you think about the time cost?
any help is appreciated, i should going on very fast :-)
best wishes,
hani
hello,
two bugs:
Collection>#union: and Collection>#collectUnion:
the first pb is where the receiver is a set,
and the second one is that (#(1 2 3) union: #(1 2 3 4))-->#(1 2 3
4), but (#(#(1 2) #(2 3) #(3 4)) collectUnion: [:each])-->#(1 2 2 3
3 4).
I have added some new asserts inside CollectionTest>>#testCollectUnion
(actually there is two red tests in this class) and published a new
version of CodeFooDevelopment.
best wishes,
hani
