|
|
|
|
|
|
|
|
Re: content assist [message #759780 is a reply to message #759557] |
Wed, 30 November 2011 01:18 |
Mokhtar Alshubei Messages: 121 Registered: November 2011 Location: Germany |
Senior Member |
|
|
Thanks again for helping but could you answer the following:
you wrote:
Quote:There are several options.
-Use the simple name fragment, i.e. don't use qualified names
-Introduce a QualifiedName-rule (see domain model example or Xbase grammar) and reference via qualified name
-adapt the qualified name of FoodCaeg returning a simple name
-adapt scoping
q1) do you mean like alex likes nuts instead of alex likes coco.nuts? it didnt work unless i make ('likes' likes=[FoodCateg|QName])
q2)what do you mean by "adapt the qualified name of FoodCateg returning a simple name"? can you give me an example?
q3)scoping?!? i have no idea how
q4) is it true what i discovered that one must give a feature with the name 'name = ID' in order the qulified name-rule trick to work?
thanks alot!
Mokhtar
[Updated on: Wed, 30 November 2011 01:21] Report message to a moderator
|
|
|
Re: content assist [message #759800 is a reply to message #759780] |
Wed, 30 November 2011 06:53 |
Alexander Nittka Messages: 1193 Registered: July 2009 |
Senior Member |
|
|
q1) is already answered, [FoodCateg] is equivalent to [FootCateg|ID] and coco.nuts is not an ID.
q2) see the documentation on naming, search for IQualifiedNameProvider and check out the DefaultDeclarativeQualifiedNameProvder
q3) see the documentation, search for scoping, there are hundreds of threads here with scoping questions
q4) see the documentation, the feature name "name" has a special meaning for naming elements
Alex
Need training, onsite consulting or any other kind of help for Xtext?
Go visit http://xtext.itemis.com or send a mail to xtext@itemis.de
|
|
|
Powered by
FUDForum. Page generated in 0.03015 seconds