|
Re: [Xtext]Cross reference between different files [message #665733 is a reply to message #665716] |
Fri, 15 April 2011 16:27 |
|
Hi,
simple change the globalscopeprovider e.g. by
// scoping and exporting API
fragment = scoping.ImportURIScopingFragment {}
// fragment = exporting.SimpleNamesFragment {}
// scoping and exporting API
//fragment = scoping.ImportNamespacesScopingFragment {}
fragment = exporting.QualifiedNamesFragment {}
fragment = builder.BuilderIntegrationFragment {}
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
|
|
Re: [Xtext]Cross reference between different files [message #1508516 is a reply to message #1508384] |
Fri, 12 December 2014 13:34 |
Puneet Patwari Messages: 64 Registered: November 2014 |
Member |
|
|
Hi christian
Actually I think I have framed my question non-clearly. For example, I have 3 model files(A,B,C) of the same grammar. In the 1st File A I have a cross-reference. Now content assist provides me with all the suitable candidates from the other 2 files also, irrespective of my specific import statement ( importedNamespace way not importURI ) in A which points to File B, only. Firstly, What I want is, to restrict the content assist in File A to show options from itself and File B and not from file C, as it is not required in the context of file A. Secondly, if the user wants to point to a particular attribute in File C without importing it, he can do that using FullyQualifiedNaming convention like we do in JAVA, directly. So, my concern is not with the second point , as it is working properly, but with the first.
Do you think I should be customizing the ContentAssistProvider or the ScopeProvider to restrict exposure? Hope I am able to explain my requirement.
By the way what did you mean by "you want to import simple names as well" ? Sorry I did not get you.
Regards
Puneet
|
|
|
|
Powered by
FUDForum. Page generated in 0.02545 seconds