In Velocity, you can just use ${attribute.documentation} (and
entity.documentation, model.documentation, etc). Entity Modeler
exposes these as top level properties that just happen to be stored in
userInfo.
ms
On Nov 15, 2007, at 5:18 PM, Kieran Kelleher wrote:
> Works fine for me :-)
>
> Note you are missing the $ at the end ....... this is eogen template
> syntax <$...........$>
>
> And it might be case sensitive, so use same spelling as appears in
> the Entity Plist ....... open with plist editor for easier path
> determination of available data.
>
> On Nov 15, 2007, at 3:39 PM, Pierce T. Wetter III wrote:
>
>>
>> On Nov 15, 2007, at 9:19 AM, Kieran Kelleher wrote:
>>
>>> Just FYI,
>>>
>>> If you examine the plist structure to see how Entity Modeler docs
>>> are added to the entities and attributes, you can easily have the
>>> docs added as javadoc to the autogenerated superclass files by
>>> adding template variables like this:
>>>
>>> /**
>>> <$Attribute.userInfo._EntityModeler.documentation$>
>>> */
>>>
>>> Thanks for the docs integration in the GUI Mike ...... I used to
>>> add my own userInfo for docs before, but this is much cleaner and
>>> it is a standard that teams can use to document their models.
>>
>> This is a cool tip, though the EOGenerator that is built into
>> WOLips doesn't quite work with the tip unfortunately. If I put in:
>>
>> /**
>> ${attribute.userInfo._EntityModeler.documentation}
>> */
>>
>> I get an error, because the parser is expecting a ., not a ._.
>>
>> Though I think:
>>
>> #if (${attribute.userInfo._EntityModeler.documentation})
>> /**
>> ${attribute.userInfo._EntityModeler.documentation}
>> */
>> #end
>>
>> Would be better...
>>
>
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 17:34:03 EST