Hi,
In VW7.5 and the last version of Moose, I do not know why these two methods:
"ViewRenderer>>sortNodes:" and "Group>>sort:"
do not work well.
In action, I think that they do not do any modification on the group/collection! Why?
Thus, actually, for sorting a group, I was obligated to do:
(aGroup asOrderedCollection sort: aBlock) [collection asOrderedCollection].
bests,
Hani
Hani ABDEEN
Student Phd thesis (Remodularization of Architectural Elements in OO Softwares)
Laboratory LISTIC - Them LSE
Annecy - University de Savoie
Hi,
On the moose.unibe.ch server we have around 300 GB at our disposal
for storing case studies. At the moment, the only way to upload these
casestudies is via ftp. Please contact me if you want to upload one.
To keep track of what is available, there is a new wiki page:
http://smallwiki.unibe.ch/moose/casestudies/
Obviously, the wiki page can be used for linking other case studies
that are stored on other servers. If you add them to the wiki page, I
can take care of storing them in the common repository.
Right now, there are 81 versions of ArgoUML and 61 versions of JEdit
(courtesy of Radu Marinescu).
Cheers,
Doru
--
www.iam.unibe.ch/~girbawww.iam.unibe.ch/~girba/blog/
"No matter how many recipes we'll know, we'll still value a chef."
Hi,
when displaying an ellipse shape, however its radius, the shape arc will not be complete :-(
for example, the attached image includes the result of this:
view shape: (Mondrian.EllipseShape radius: [:r| 20]).
view node: #circle.
do we have a solution for that?
can I change the border color of an ellipse shape, independently of its fill color?
bests,
Hani
Hani ABDEEN
Student Phd thesis (Remodularization of Architectural Elements in OO Softwares)
Laboratory LISTIC - Them LSE
Annecy - University de Savoie
Hi,
If you choose to use 7.4, you should manually load 'CodeFoo for VW74'
before you load Moose. It contains some backward compatibility methods.
However, we no longer support 7.4. Perhaps a better solution would be
to use the X11 version of 7.5. Alternatively you can also use the
Windows VM via Parallels. It seems to work quite well.
Cheers,
Doru
On Jul 4, 2007, at 12:17 PM, Mathieu Suen wrote:
> Yes is with the 7.5 VM
> So I switch back to 7.4
> Mth
>
>
>
> On Jul 4, 2007, at 11:48 AM, Tudor Girba wrote:
>
>> Hi Math,
>>
>> I believe you are using the native Mac VM for VW 7.5.
>>
>> I noticed this problem too when we moved to 7.5. It seems to be
>> related to a bug in the VM. The code works as it should on all
>> version of 7.4.1, and it works on 7.5 on Windows and on Mac X11.
>>
>> In any case, I found the native Mac VM unusable, and I switched
>> back to X11.
>>
>> Cheers,
>> Doru
>>
>> On Jul 4, 2007, at 11:33 AM, Mathieu Suen wrote:
>>
>>> Hi
>>>
>>> Look at this example
>>>
>>> | view |
>>> view := ViewRenderer new.
>>> view borderedRectangleShape.
>>> view nodes: (0 to: 5).
>>> view edgesFrom: [:each | each // 3].
>>> view treeLayout.
>>> view open
>>>
>>> The edge between the node 4 and 1 do not appear.
>>> If you move it the node 4 the edge is there.
>>>
>>> Thanks
>>>
>>> Mth
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.iam.unibe.ch/~girba
>> www.iam.unibe.ch/~girba/blog/
>>
>> "Every thing should have the right to be different."
>>
>>
>
--
www.iam.unibe.ch/~girbawww.iam.unibe.ch/~girba/blog/
"Value is always contextual."
Hi
Look at this example
| view |
view := ViewRenderer new.
view borderedRectangleShape.
view nodes: (0 to: 5).
view edgesFrom: [:each | each // 3].
view treeLayout.
view open
The edge between the node 4 and 1 do not appear.
If you move it the node 4 the edge is there.
Thanks
Mth
Hello!
Today, I tried to load Moose in a virgin image of VW7.5 and I had a little
problem :(
Indeed, after loading the package Moose, I clicked on the Icon Moose and
it leads into a bug!
The bug comes from MooseModel>>name: that calls the method deprecated: The
class SCG.Deprecation is not defined in the system.
Did I do something wrong?
sara
Hi Sara,
Please load the 'Moose Config' package. This will load several other
bundles including Mondrian.
For more information on how to setup a Moose image from scratch
please check:
http://smallwiki.unibe.ch/moose/setupamooseimagefromscratch/
Cheers,
Doru
On Jul 3, 2007, at 12:02 PM, sellossa(a)ensieta.fr wrote:
> Hi Doru,
>
> thank you very much for your help.
> I think that the visualization that shows the pointers between
> entities
> should be very interesting to study and generate :)
>
> you said that this visualisation is avalaible in:
> MooseModel>>viewAllEntititesOn: in the MondrianPaintings bundle.
>
> I've loaded the last version of Moose (the 3.2.40 version) but I can't
> find it in the MondrianPaintings bundle!
>
> did I do something wrong?
>
> thank you
>
> sara
>
> Hi Sara,
>
> I understood that you would want a visualization that would work for
> any meta-model, but what I did not understand is: What would the goal
> of the visualization be?
>
> What you probably want is some visualization that would just
> interpret the EMOF description in some way.
>
> One generic visualization I can think of is to see what kind of
> instances are there loaded and how many of each are there. But, this
> would basically be not much more than the list we show in the browser.
>
> Another possibility would be to have all objects in the model, or at
> least a collection of them, and then show all the pointers between
> them.
>
> I quickly put together this visualization and I attached an example
> of the LAN model: each node is an entity colored according to its
> type, and each edge represents a pointer to another entity. The nodes
> are arranged according to a force based layout (which is very slow).
>
> As you can see, the problem here is that even with a small model, you
> can get complex pictures. The visualization is available in
> MooseModel>>viewAllEntititesOn: in the MondrianPaintings bundle.
>
> Many times the meta-model of the case study and and the meta-model of
> the visualization are not the same. For example, in a FAMIX meta-
> model, InheritanceDefinition is a first class, just like Class, but
> in a class hierarchy visualization, classes are represented as nodes
> and inheritances as edges. In this case, the naive generic
> visualization I described above would probably map inheritances on
> nodes as well.
>
> I mentioned Mondrian, because the idea behind it is to provide a kind
> of an infrastructure with which you can quickly script your
> visualization to show what you want from the model. With Mondrian you
> besically specify a meta-model transformation.
>
> Cheers,
> Doru
>
>
>
--
www.iam.unibe.ch/~girbawww.iam.unibe.ch/~girba/blog/
"Every thing should have the right to be different."
Hi,
Using Mondrian easel I would giving the nodes of a given context the possibility to have different shapes (e.g., Rectangle, oval, ... "if we have other shapes??").
In other words, I need something like this:
context.....
......
view shape:[:node|
node condition1
ifTrue:[shape1]
ifFalse:[node condition2
ifTrue:[shape2]
ifFalse: [shape3]]].
........
view nodes: aGroup.
I have done that but I did not get what I search. How I can do that?
bests,
Hani
Hani ABDEEN
Student Phd thesis (Remodularization of Architectural Elements in OO Softwares)
Laboratory LISTIC - Them LSE
Annecy - University de Savoie
hello
I created my own metamodel to import my own elements in Moose.
Actually, I want to analyse chickens and eggs with Moose. So,I wrote
classes Chicken and Egg which both extend MooseElement. Then, I extended
MooseModel in my package and I implemented allChickens and allEggs methods
in the class MooseModel. Finally, I imported in Moose my instances of
Chicken and Egg and I could see them into Moose, so I was very happy :)
Infortunatly, when I decided to unload my model(and consequently the
methods allChickens and allEggs in MooseModel), Moose didn't work anymore!
To solve it, I ran System>> reinitializeDefaultSystem. Nervertheless, it
may be painful and tiresome to reinitialize the system whenever a
metamodel is removed.
Is there an other solution to fix this problem? Or is there possible to
reinitialize it automatically at Moose launch.
Thank you for your help
Sara
