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
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."
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:
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."
None. belongsTo will just be Smalltalk implementation and nothing else.
Cheers, Doru
On Oct 20, 2008, at 11:03 PM, Stéphane Ducasse wrote:
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:
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."
-- www.tudorgirba.com www.tudorgirba.com/blog
"Be rather willing to give than demanding to get."
but if I want to follow a naigation via a menu will I have to follow container and not belongsTo?
Stef
On Oct 20, 2008, at 11:08 PM, Tudor Girba wrote:
None. belongsTo will just be Smalltalk implementation and nothing else.
Cheers, Doru
On Oct 20, 2008, at 11:03 PM, Stéphane Ducasse wrote:
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:
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."
-- www.tudorgirba.com www.tudorgirba.com/blog
"Be rather willing to give than demanding to get."
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:
None. belongsTo will just be Smalltalk implementation and nothing else.
Cheers, Doru
On Oct 20, 2008, at 11:03 PM, Stéphane Ducasse wrote:
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:
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."
-- www.tudorgirba.com www.tudorgirba.com/blog
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Cheers, Doru
On Oct 21, 2008, at 11:05 AM, Simon Denier wrote:
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:
None. belongsTo will just be Smalltalk implementation and nothing else.
Cheers, Doru
On Oct 20, 2008, at 11:03 PM, Stéphane Ducasse wrote:
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:
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."
-- www.tudorgirba.com www.tudorgirba.com/blog
"Be rather willing to give than demanding to get."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"There are no old things, there are only old ways of looking at them."
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ?
Hi Stef,
Take a look at: FAMIXNamedEntity>>belongsTo
Doru
On Oct 21, 2008, at 12:31 PM, Stéphane Ducasse wrote:
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ? _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We are all great at making mistakes."
Excellent!
for the lurkers :)
belongsTo <MSEProperty: #belongsTo type: #FAMIXContainerEntity> <derived> ^self shoudBeImplemented
On Oct 21, 2008, at 12:41 PM, Tudor Girba wrote:
Hi Stef,
Take a look at: FAMIXNamedEntity>>belongsTo
Doru
On Oct 21, 2008, at 12:31 PM, Stéphane Ducasse wrote:
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ? _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We are all great at making mistakes."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
do I have to put it also for the setBelongsto do you distinguish setter and getter?
simon I fixed some belongsTo implementors.
On Oct 21, 2008, at 12:41 PM, Tudor Girba wrote:
Hi Stef,
Take a look at: FAMIXNamedEntity>>belongsTo
Doru
On Oct 21, 2008, at 12:31 PM, Stéphane Ducasse wrote:
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ? _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We are all great at making mistakes."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
The convention is that the meta-description is added only to the getter. The rationale is that you always need a getter, but you don't always need a setter.
Cheers, Doru
On Oct 21, 2008, at 2:17 PM, Stéphane Ducasse wrote:
do I have to put it also for the setBelongsto do you distinguish setter and getter?
simon I fixed some belongsTo implementors.
On Oct 21, 2008, at 12:41 PM, Tudor Girba wrote:
Hi Stef,
Take a look at: FAMIXNamedEntity>>belongsTo
Doru
On Oct 21, 2008, at 12:31 PM, Stéphane Ducasse wrote:
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ? _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We are all great at making mistakes."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"To lead is not to demand things, it is to make them happen."
Good we are making progress!
Stef
On Oct 21, 2008, at 2:23 PM, Tudor Girba wrote:
Hi,
The convention is that the meta-description is added only to the getter. The rationale is that you always need a getter, but you don't always need a setter.
Cheers, Doru
On Oct 21, 2008, at 2:17 PM, Stéphane Ducasse wrote:
do I have to put it also for the setBelongsto do you distinguish setter and getter?
simon I fixed some belongsTo implementors.
On Oct 21, 2008, at 12:41 PM, Tudor Girba wrote:
Hi Stef,
Take a look at: FAMIXNamedEntity>>belongsTo
Doru
On Oct 21, 2008, at 12:31 PM, Stéphane Ducasse wrote:
ok
The Moose Finder relies on the Fame descriptions.
It is just that we will have two such descriptions, one for belongsTo and one for container. They can both be followed. So, I would say this is not really an issue.
Then I have to metadescribed belongsTO ?
<MSE: ><derived>
?
can you tell me what is the magic incantation ? _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"We are all great at making mistakes."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"To lead is not to demand things, it is to make them happen."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Simon Denier -
Stéphane Ducasse -
Stéphane Ducasse
-
Stéphane Ducasse -
Tudor Girba