Eclipse Community Forums: TMF (Xtext) » Xtext via Equinox without a UI component

Home » Modeling » TMF (Xtext) » Xtext via Equinox without a UI component(Initialising an Xtext Project in an OSGi Environment WITHOUT a UI component)

Show: Today's Messages :: Show Polls :: Message Navigator

Xtext via Equinox without a UI component [message #1752988]

Tue, 31 January 2017 17:15

Felix Kampfer

Messages: 3
Registered: January 2017

Junior Member

Hi,

how would I go about using Xtext via Eclipse-Equinox without an editor/workspace component? I'm not sure if my question even makes sense, but I'd like to instantiate an Xtext project using an extension point that doesn't make UI contributions. I'm aware that it's also possible to have a standalone setup.

Section 8.2 of the tutorial demonstrates how to extend "org.eclipse.ui.editors", but that's not what I'm after.

My ultimate goal is creating a plugin with an API to parse a string, serialize models, and provide a content assist function for a web-based editor for my language.
Architecture restrictions require me to use Xtext 2.5, which unfortunately doesn't generate a web editor plugin from the get-go.

Any help is very much appreciated.

Report message to a moderator

Re: Xtext via Equinox without a UI component [message #1753142 is a reply to message #1752988]

Thu, 02 February 2017 08:07

Karsten Thoms

Messages: 762
Registered: July 2009
Location: Dortmund, Germany

Senior Member

Please note that "standalone" mode means always without any Equinox runtime, while the "UI" part is meant to be running within Equinox. Xtext has also UI dependencies in its default "UI" part and is not designed to run in a non-UI Equinox environment by default.
What you have to do is to provide a UI-less "UI Module". Problem here is that parts of the shared UI is also UI dependent.
Quite some work to get things sorted, but we have that also in a "headless" Equinox application.
Please do not use the StandaloneSetup!

Report message to a moderator