Eclipse Community Forums: TMF (Xtext)

Home » Modeling » TMF (Xtext) » dot-path upside down(my 4GL has an optional reference field{.entity}, how can I adopt Code Completion?)

dot-path upside down [message #1091295]

Wed, 21 August 2013 05:56

Eclipse User

my 4GL has an optional reference field{.entity} (field=attribute, entity=class)
So in my code I may type MyField1.MyEntity2.

How can I inform the Content Assistant that I need all fields for Entity "MyEntity2"?

Using the normal way, I would just enter the class and the dot and this will lead me to the attributes of this class. Unfortunately, this is an upside down situation?

Any ideas how I can solve this in an XTEXT grammar?

TIA, Uli

Re: dot-path upside down [message #1091313 is a reply to message #1091295]

Wed, 21 August 2013 06:28

Eclipse User

Hi,

sorry i did not get the post, can you share grammar and sample model?

Re: dot-path upside down [message #1091367 is a reply to message #1091313]

Wed, 21 August 2013 08:02

Eclipse User

Hi Christian,
sorry I do not have a grammar / example so far because I'm a bit lost.

************* Just a sketch:

Model:
entities+=Entity*

Entity:
"entity" name=ID fields+=Field*

Field:
"field" name=ID

FieldRef:
'use" name=ID usedField=???

************* The sample:

entity A
field F1
field F2
field F3

entity B
field F1
field F2
field F4
field F5

use ATEST1 F1.B
use ATEST2 F1.A
use ATEST3 F3

*************
If the notation was "normal" like A.F? the Content Assist would not have a problem to deliver F1,F2,F3. But in my 4GL, it is turned around and the entity is an optional part of the qualification.

Hope this gives you an impression what is needed.

TIA, Uli

Re: dot-path upside down [message #1091369 is a reply to message #1091367]

Wed, 21 August 2013 08:05

Eclipse User

Hi,

if i understand your problem:

if a Attribute is only in one field then its name is

Simplename else it is Simplename.EntityName?

Re: dot-path upside down [message #1091412 is a reply to message #1091369]

Wed, 21 August 2013 09:17

Eclipse User

even harder, the entity qualification can be left out in the code even if it is ambiguous now.

Then the entity is calculated at runtime from the "context". If you say "F2" and your application is working with entity "B", it uses F2.B

A vey messed up logic, but I have to base my work on this 1985 laws.

The question is how to convince the Contents assistant to show only attributes of class "B".
Is there some construction where i can
type "*.B",
hit CTRL-Space and get a selection of F1.B, F2.B, F4.B, F5.B
which replaces the "*.B" in my text?

use *.B
- activate Content Assistant and select F2.B and get in my text
use F2.B

Re: dot-path upside down [message #1091453 is a reply to message #1091412]

Wed, 21 August 2013 10:25

Eclipse User

Hi,

i guess you have to repackage delegateGetScope(ctx, ref) in your scopeprovider according to your rules.
(create new IObjectDescriptions) and put them into org.eclipse.xtext.scoping.impl.SimpleScope.SimpleScope(IScope, Iterable<IEObjectDescription>)
dont know if this will work smooth.

~Christian

Re: dot-path upside down [message #1091520 is a reply to message #1091453]

Wed, 21 August 2013 12:12

Eclipse User

Hi Christian,

sounds a bit complicate, but I have time enough to collect experiences.
Thanks for giving me a direction where I can have a look.

Uli

Previous Topic:	Couldnt resolve reference to JvmMember
Next Topic:	Arbitrary Qualifiers

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 12:54:00 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter