Smalltalk › Pharo › Pharo Smalltalk Users

Moose

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

7 messages Options

abdelghani ALIDRA

Moose

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

abergel

Re: Moose

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 <[hidden email]> 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

Tudor Girba-2

Re: Moose

In reply to this post by abdelghani ALIDRA

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 <[hidden email]> 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"

abdelghani ALIDRA

Re: Moose

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 <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>; Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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"

Tudor Girba-2

Re: 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 <[hidden email]> 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 <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>; Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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"

abdelghani ALIDRA

Re: Moose

Ok. Thanks a lot.

Abdelghani

De : Tudor Girba <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>
Cc : Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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 <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>; Any question about pharo is welcome <[hidden email]>
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 <[hidden email]> 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"

abdelghani ALIDRA

Re: Moose

In reply to this post by abdelghani ALIDRA

Actually I am not using a specifc tool to generate feature models. For the moment, I am using XML Files to express features because tools like SPLOT use such format so it would be easy to export it into Moose.

It would be nice to have the Frascati feature model file, just to test some new metrics and visualisations and better understand the code :)

Abdelghani

De : Alexandre Bergel <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>
Envoyé le : Mercredi 24 juin 2015 17h03
Objet : Re: [Pharo-users] Moose

Hi!

No, we do not have a particular description of the text file. This was made in a very ad-hoc way, and very close to Familiar. Since I guess you are using your own platform to express features and variability, I guess this text description is not that useful for you.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On Jun 24, 2015, at 8:13 AM, abdelghani ALIDRA <[hidden email]> wrote:

Thanks for the document.
Since Familiar code is open, I may want to reuse some parts of it.
I noticed there is a FMTexImportCommand class in the Familiar package. This is to load a feature model from a text description or file I gess.

What is the structure of such a file? Maybe you have some examples also?

Regards.
Abdelghani

De : Alexandre Bergel <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>
Envoyé le : Mardi 23 juin 2015 15h39
Objet : Re: [Pharo-users] Moose

What I try to do is to use Moose to model, raison and do visualizations on feature models (a variability model used to model variability in software product lines)

In the feature model there is a concept called crosstree constraints relying two features (fonctionnalities)
example: aFeature requires aNotherFeature.
The relation goes from aFeature to aNotherFeature.

Okay. Interesting topic.
We did a bit of work on this, you may want to have a look at it:
https://dl.dropboxusercontent.com/u/31543901/MyPapers/Urli15-FeatureComplexity.pdf

Cheers,

Alexandre

Regards

De : Alexandre Bergel <[hidden email]>
À : abdelghani ALIDRA <[hidden email]>; Any question about pharo is welcome <[hidden email]>
Envoyé le : Lundi 22 juin 2015 19h41
Objet : Re: [Pharo-users] Moose

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 <[hidden email]> 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