| Re: [mdt-ocl.dev] Import statement and obsolete examples plugins |
Hi Sebastain
Xtext's imports are just a convenient default. There is no need to use them.Indeed. The out-of-the-box Xtext behaviour is amazingly good. The OCL standard library editor even resolved template parameters without any customisation. I got it going in just a couple of hours with realistic semantic relevance; but it was my fourth editor leveraging some of the earlier models.
For OCL the various namespace distinctions need a custom ScopeProviders that provides eClass dependent semantics with eReference dependent filtering. Here there are a variety of useful solutions already available, but unfortunately no documentation on their relative merits. I'm reluctant to stray too far into customisation since improving one facility may break another e.g. Content-Assist is very dependent on the give-me-all-the-names API, whereas Linking could be much more efficient if it just seeks out the one target, rather than gets all the names and then selects one.
Ed