> Importers for Java, C++, Python and Smalltalk.
How to run the Python and C++ importer? Which tools are doing this
anyway? The only thing I now is that Martin once write some python
scripts, but I do not remember where they are and how to run them.
Java import refers to iPlasma, currently, I guess.
AA
Hi,
I added two components to moose.unibe.ch for reusing the mail
addresses of the mailing lists.
So, now you can use the followings:
+/reusable/moosecontact+ will produce moose(a)iam.unibe.ch
+/reusable/moosedev+ will produce moose-dev(a)iam.unibe.ch
The howto page is here:
http://moose.unibe.ch/varia/howtoedit/mails
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Beauty is where we see it."
I am trying to create custom visulizations with Mondrian using the scripts
described in "Mondrian: An Agile Information Visualization Framework", but I
am not able to execute this script...
*view := ViewRenderer new.
view nodes: model classes using: RectangleShape withBorder.
view open.*
I have tried "model allClasses" as well, but it says there is no model
class.
Hi,
currently opposites are described as
opposite and opposite+derived. This can be one->one, one->many,
many->one and many->many. We
can easily generate code which handles all those different cases.
Secondly, when we are writing out instances of fm3-described classes; we
know when attributes
have an opposite. There the derived is quite unimportant; since it is
just a hint to the writer "which" of
the 2 opposites it should write and which it should derive. However,
since you can
generate code which takes all different cases into account, writing it
out (and reading it in) either way is
possible. The opposite can be filled in from either of the available
relationships. So which opposite you
file out could be chosen randomly. Coming to my point: do attributes
which have an opposite need a
derived statement? Isn't it more logical that only real algorithmic
"attributes" are derived? When choosing
automatically you will only have to take care that if an opposite is its
own opposite (the opposite of the
attribute "opposite" in fm3.Property is like this; that's probably the
only case :)), that it always gets written.
#(((
#This fact would again strengthen my case that the opposite of an
opposite should not necessarily be
#declared as an opposite in the MSE file. Nor should the type be in
either of them. If we find (prop (id: 2)
#(opposite (idref: 1))), then we should automatically do (objectAtId:
1).setOpposite(objectAtId: 2),
#which sets the owner of (objectAtId: 2) as it's type, sets the type of
the (objectAtId: 2) as the owner of
#(objectAtId: 1); and then sets (objectAtId: 2) as the opposite of
(objectAtId: 1)
#
#---->> if you use an opposite-declaration for an attribute; you have 1
statement instead of 5 for which 4 are
#redundant ----> less redundancy => better performance
#)))
any ideas / comments? Does this seem right / clean?
cheers,
Toon
Dear list,
Is there no way to describes an interface in FAMIX?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Dear list,
I wanted to graphically render a model using Mondrian. However It
seems that Meye06a is a bit out of sync with the current
implementation (feel free to say that I am wrong :-).
When I open the easel, in the pane where I am supposed to script the
variable 'model' does not seems to be known.
I tried to cut and paste the following script (extracted from the
paper) but it is not accepted by the easel:
-=-=-=-=-=-=-=-=-=-=-=-=
view := ViewRenderer new.
view nodes: model classes
using: (Rectangle withBorder height: #NOM; width: #NOA).
view edges: model inheritances
using: (Line from: #superclass to: #subclass).
view layout: TreeLayout new.
view open.
-=-=-=-=-=-=-=-=-=-=-=-=
How can I draw the UML diagram for a given model?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
