|Re: Sirius Tree Description [message #1804217 is a reply to message #1804209]
||Wed, 20 March 2019 15:30
|| Steve Monnier
Registered: May 2011
Concerning your first question, as you said the order is defined by the order of the mappings. If you want different type of elements to be displayed, you will need to have only one mapping where the Domain Class will be a common superclass (the Domain Class can be an abstract class) and a semantic candidate expression that return the element in this order. This may implies change in your metamodel to have this level of abstraction. For exemple, let's say that we have a family metamodel. If your metamodel has 3 class Family, Man and Woman where Family has 2 references men and women, then in your odesign you are stuck with 2 mappings, one for Man and one for Woman and they will be displayed separatly. Instead you update the metamodel with 4 class Family, FamilyMember, Man and Woman where Man and Woman inherits FamilyMember and Family only has 1 reference familyMembers. In your odesign under Family, you don't have 2 mappings but only one on FamilyMember and the members will be presented in the order of creation instead of one kind after the other.
I am not sure to understand your second question. The order of the elements displayed by a mapping is determined by the semantic candidate expression. The order displayed should be the same has the order serialized in the aird file.
Steve Monnier - Obeo
Need training or professional services for Sirius?
Powered by FUDForum
. Page generated in 0.02020 seconds