Hi everybody, when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to?if I make MyFamixClass>>from^previousthe same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass)Who can one avoid that? Regards Abdelghani
Hi! I have never used the previous and next. No idea whether this is used or not. What are you trying to achieve? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jun 22, 2015, at 12:06 PM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote:
Hi everybody,
when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to? if I make MyFamixClass>>from ^previous the same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass) Who can one avoid that?
Regards
Abdelghani
Hi, from/to are derived properties and they should describe the association. For example: FAMIXAccess>> from ^ self accessor FAMIXAccess>> to ^ self variable next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code: self doSomething. self doSomethingElse. you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived). Does this make sense? Btw, these questions are better suited for the Moose mailing list: http://www.moosetechnology.org/#twitter Cheers, Doru On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote:
Hi everybody,
when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to? if I make MyFamixClass>>from ^previous the same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass) Who can one avoid that?
Regards
Abdelghani
-- www.tudorgirba.com "Every thing has its own flow"
Thank you Tudor, Yes, it makes sence.Then I suppose that I just return nil if I dont want to display the previous and next information. Regards De : Tudor Girba <tudor@tudorgirba.com> à: abdelghani ALIDRA <alidrandco@yahoo.fr>; Any question about pharo is welcome <pharo-users@lists.pharo.org> Envoyé le : Lundi 22 juin 2015 21h25 Objet : Re: [Pharo-users] Moose Hi, from/to are derived properties and they should describe the association. For example: FAMIXAccess>> from ^ self accessor FAMIXAccess>> to ^ self variable next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code: self doSomething.self doSomethingElse. you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived). Does this make sense? Btw, these questions are better suited for the Moose mailing list:http://www.moosetechnology.org/#twitter Cheers,Doru On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote: Hi everybody, when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to?if I make MyFamixClass>>from^previousthe same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass)Who can one avoid that? Regards Abdelghani -- www.tudorgirba.com "Every thing has its own flow"
You do not have to return anything if you do not have any information. FAMIXAssociation already does that job for you. Doru On Tue, Jun 23, 2015 at 11:42 AM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote:
Thank you Tudor,
Yes, it makes sence. Then I suppose that I just return nil if I dont want to display the previous and next information.
Regards
------------------------------ *De :* Tudor Girba <tudor@tudorgirba.com> *à :* abdelghani ALIDRA <alidrandco@yahoo.fr>; Any question about pharo is welcome <pharo-users@lists.pharo.org> *Envoyé le :* Lundi 22 juin 2015 21h25 *Objet :* Re: [Pharo-users] Moose
Hi,
from/to are derived properties and they should describe the association. For example:
FAMIXAccess>> from ^ self accessor FAMIXAccess>> to ^ self variable
next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code:
self doSomething. self doSomethingElse.
you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived).
Does this make sense?
Btw, these questions are better suited for the Moose mailing list: http://www.moosetechnology.org/#twitter
Cheers, Doru
On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote:
Hi everybody,
when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to? if I make MyFamixClass>>from ^previous the same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass) Who can one avoid that?
Regards
Abdelghani
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
Ok. Thanks a lot. Abdelghani De : Tudor Girba <tudor@tudorgirba.com> à: abdelghani ALIDRA <alidrandco@yahoo.fr> Cc : Any question about pharo is welcome <pharo-users@lists.pharo.org> Envoyé le : Mardi 23 juin 2015 13h51 Objet : Re: [Pharo-users] Moose You do not have to return anything if you do not have any information. FAMIXAssociation already does that job for you. Doru On Tue, Jun 23, 2015 at 11:42 AM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote: Thank you Tudor, Yes, it makes sence.Then I suppose that I just return nil if I dont want to display the previous and next information. Regards De : Tudor Girba <tudor@tudorgirba.com> à: abdelghani ALIDRA <alidrandco@yahoo.fr>; Any question about pharo is welcome <pharo-users@lists.pharo.org> Envoyé le : Lundi 22 juin 2015 21h25 Objet : Re: [Pharo-users] Moose Hi, from/to are derived properties and they should describe the association. For example: FAMIXAccess>> from ^ self accessor FAMIXAccess>> to ^ self variable next/previous denote the position of the association in the code with respect to the other associations. For example, imagine this Pharo code: self doSomething.self doSomethingElse. you will get two FAMIXInvocations, and these can be linked through the previous property (next is derived). Does this make sense? Btw, these questions are better suited for the Moose mailing list:http://www.moosetechnology.org/#twitter Cheers,Doru On Mon, Jun 22, 2015 at 5:06 PM, abdelghani ALIDRA <alidrandco@yahoo.fr> wrote: Hi everybody, when working with the FAMIX meta model, one must implement the previous, next, from and to methods for each class extending FAMIXAssosiation. What is the diffence between previous/from and next/to?if I make MyFamixClass>>from^previousthe same information is displayed twice in the Moose panel (because both methods are annotated with the MSEProperty in the superclass)Who can one avoid that? Regards Abdelghani -- www.tudorgirba.com "Every thing has its own flow" -- www.tudorgirba.com "Every thing has its own flow"
participants (3)
-
abdelghani ALIDRA -
Alexandre Bergel -
Tudor Girba