Le 6 nov. 2017 à 18:24, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> a écrit :

Le 06/11/2017 à 18:02, Tudor Girba a écrit :
Hi,

The point of Traits is exactly to not require inheritance.

Why is it not good solution to add TEntityMetaLevelDependency to all classes that require it regardless of the place in inheritance?


My problem is that: I know that a children selector will return a
FAMIXSourcedEntity and I need to send some messages to
FAMIXSourcedEntity that are in the Trait. But FAMIXSourcedEntity cannot
use the Trait if we do not accept that the associations will also get
the Trait.

If we introduce this FAMIXNonAssociationEntity then we will move
#comments and #containerFiles to this entity? Also FAMIXFile>>entities
should point to FAMIXNonAssociationEntity?

Yes.


But once again… Why an association car understand
#atScope:/#children/#parents (which are queries) and not #queryAllIncoming?

I don’t remember why. Perhaps it is a design error. 
I would have to make some test to have be sure. But no time to do it in the next two weeks at least or even more. Sorry.
If you want, try to remove TMetaLevelDependencies in the traits used by TAssociationMetaLevelDependency.

Anne



Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"We are all great at making mistakes."








_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev



-- 
Cyril Ferlicot
https://ferlicot.fr

http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev