Hello,
In which cases should we describe a property with a pragma ? I guess that property-pragmas will be used to set the list of attributes to the FM3MetaDescription of the class. But by looking quikly to the famix implementation, it seems that some properties are described and other not.
For example, in FAMIXPackage, the method 'classes' is not described. Therefore it does not appear in the FAMIXPackageMetaDescription listOfAttributes. I don't know the reason?
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
One reason for describing a property with a pragma is to make tools
aware of this pragma. In the example you said, it is more relevant for the user to deal with groups instead of collection. MooseAbstractGroup>>allClasses contains the pragma #navigation:. Alexandre On 18 Mar 2010, at 05:42, Cyrille Delaunay wrote: > Hello, > In which cases should we describe a property with a pragma ? > I guess that property-pragmas will be used to set the list of > attributes to the FM3MetaDescription of the class. > But by looking quikly to the famix implementation, it seems that > some properties are described and other not. > For example, in FAMIXPackage, the method 'classes' is not described. > Therefore it does not appear in the FAMIXPackageMetaDescription > listOfAttributes. > I don't know the reason? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Ok. But pragmas I talk about are pragmas like:
<MSEProperty: #methods type: #FAMIXMethod opposite: #parentType> <multivalued> <derived> that will be used to build the metaDescriptions of the famix classes.
In my example, I wonder why the method 'classes' is not described with such a pragma
2010/3/18 Alexandre Bergel <[hidden email]> One reason for describing a property with a pragma is to make tools aware of this pragma. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Maybe because FAMIXPackage is not properly fame described?
Alexandre On 18 Mar 2010, at 08:06, Cyrille Delaunay wrote: > Ok. But pragmas I talk about are pragmas like: > <MSEProperty: #methods type: #FAMIXMethod opposite: #parentType> > <multivalued> <derived> > that will be used to build the metaDescriptions of the famix classes. > In my example, I wonder why the method 'classes' is not described > with such a pragma > > 2010/3/18 Alexandre Bergel <[hidden email]> > One reason for describing a property with a pragma is to make tools > aware of this pragma. > In the example you said, it is more relevant for the user to deal > with groups instead of collection. MooseAbstractGroup>>allClasses > contains the pragma #navigation:. > > Alexandre > > > > On 18 Mar 2010, at 05:42, Cyrille Delaunay wrote: > > Hello, > In which cases should we describe a property with a pragma ? > I guess that property-pragmas will be used to set the list of > attributes to the FM3MetaDescription of the class. > But by looking quikly to the famix implementation, it seems that > some properties are described and other not. > For example, in FAMIXPackage, the method 'classes' is not described. > Therefore it does not appear in the FAMIXPackageMetaDescription > listOfAttributes. > I don't know the reason? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by cdelaunay
One reason is that #classes is a query on another attribute of FamixPackage, not a stand-alone attribute. As such, it is not necessary to describe it for MSE. (and as noted by Alex, we prefer to use groups for navigation in the model). Now it's possible to describe this attribute. I will just mark it as derived in this case. On 18 mars 2010, at 10:42, Cyrille Delaunay wrote: > Hello, > In which cases should we describe a property with a pragma ? > I guess that property-pragmas will be used to set the list of attributes to the FM3MetaDescription of the class. > But by looking quikly to the famix implementation, it seems that some properties are described and other not. > For example, in FAMIXPackage, the method 'classes' is not described. Therefore it does not appear in the FAMIXPackageMetaDescription listOfAttributes. > I don't know the reason? > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- Simon _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |