21 Oct
2008
21 Oct
'08
11:05 a.m.
On 21 oct. 08, at 09:15, Stéphane Ducasse wrote:
but if I want to follow a naigation via a menu will I
have to follow
container and not belongsTo?
Not sure if I understand the problem, but isn't this the case where we
use the Fame descriptions to navigate between elements?
In other words, should the mouse finder rely on Famix or Fame for
navigation and display of properties?
Stef
On Oct 20, 2008, at 11:08 PM, Tudor Girba wrote:
--
Simon
None. belongsTo will just be Smalltalk
implementation and nothing
else.
Cheers,
Doru
On Oct 20, 2008, at 11:03 PM, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Yes I know
my question was more what is the impact to add
belongsTo
^ self container
on the navigation and metadescription?
Stef
On Oct 20, 2008, at 9:53 PM, Tudor Girba wrote:
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Be rather willing to give than demanding to get."
Hi Stef,
We kept belongsTo just for backward compatibility and for the
trademark :).
belongsTo is now derived from other instance variables that are
specific for each entity. For Types belongsTo = container. For
Methods, belongsTo = parentClass.
Cheers,
Doru
On Oct 20, 2008, at 9:39 PM, Stéphane Ducasse wrote:
> Sometimes I have no idea what to do
> and I'm stuck
>
> belongsTo
> <MSEProperty: #belongsTo type: #FAMIXContainerEntity> <derived>
> ^self shoudBeImplemented
>
> what does it means?
> Why there is no instance variable somehow related to belongsTo in
> FamixNamedEntity?
>
> Yes I feel a bit alone some times.....
>
> Stef
--
www.tudorgirba.com
www.tudorgirba.com/blog
"One cannot do more than one can do."