Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MooseCore Milestone-4.6
New issue 708 by tudor.gi...@gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
Currently, the MSEComment: is used to define comments of a property.
SomeEntity>>someProperty <MSEProperty: ...> <MSEComment: 'comment'>
This is used by the MetaBrowser but not by Fame.
At the very least, we should add a means to add MSEComment: to the class side for the overall class.
Comment #1 on issue 708 by stephane...@gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
I would like to know how can I also get if an attributes was defined in a fame package or not. but this is not that important.
Comment #2 on issue 708 by stephane...@gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
How do you query the comment or any tags associated to another one?
Comment #3 on issue 708 by tudor.gi...@gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
We use the Pragma protocol. For example if you already know a method that has the MSEProperty:... annotation you can query the comment like:
Pragma inMethod: FAMIXType>>#attributes named: #MSEComment:.
==> <MSEComment: 'List of attributes declared by this type.'>
Updates: Labels: -Milestone-4.6 Milestone-4.7
Comment #4 on issue 708 by tudor.gi...@gmail.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
(No comment was entered for this change.)
Updates: Labels: -Milestone-4.7
Comment #5 on issue 708 by tu...@tudorgirba.com: Fame should accept comments both for properties and for meta descriptions http://code.google.com/p/moose-technology/issues/detail?id=708
Not for 4.7