This repository contains code examples that demonstrate how to build diagram editors with the Graphical Language Server Platform (GLSP). The examples are focused on the integration of GLSP editors with the cloud-based Eclipse Theia IDE using the GLSP Theia integration and the Java based GLSP Server Framework.
Each example is self-contained and provides both, an example diagram client (glsp-client directory) and its corresponding GLSP server (glsp-server directory).
The following libraries/frameworks need to be installed on your system:
The examples are heavily interwoven with Eclipse Theia, so please also check the prerequisites of Theia.
The web-based/client part of the examples has been developed using Visual Studio Code and the server/java part has been developed with the Eclipse IDE. However, it's of course also possible to use any other IDE or text editor.
-
Project Templates: The best starting point for your own diagram editor project. The project templates are available for several combinations of tool platform integrations (Theia, VS Code), source models (JSON, EMF) and servers (Node, Java). Please visit the GLSP documentation for more information.
-
Workflow Example: A consistent example provided by all GLSP components. It implements a simple flow chart diagram editor with different types of nodes and edges. The
Workflow Exampleis the main example used for development and integrates all GLSP features
To work with the source code and debug the examples in VS Code dedicated VS Code Workspace files for each example are provided.
These workspace include both the glsp-client and glsp-server sources and offer dedicated launch configurations for debugging purposes.
To open a example workspace simply start a VS Code instance and use the Open Workspace from File.. entry from the File menu.
Then navigate to a example or project template subdirectory (e.g. workflow) and open the *.vscode-workspace file.
For a smooth development experience we recommend a set of useful VS Code extensions. When a workspace is first opened VS Code will ask you wether you want to install those recommended extensions.
Alternatively, you can also open the Extension View(Ctrl + Shift + X) and type @recommended into the search field to see the list of Workspace Recommendations.
The server component of each example has to be built using Maven, the client component has to be built using yarn. Convenience scripts to build both components at once are provided. To build all examples simply execute the following in the repository root:
yarn buildIn addition, it is also possible to build each example individually:
# Build only the workflow example
yarn build:workflowEach example provides a dedicated Theia web app which can be started from the repository root with yarn start:<example_name>:
# Start workflow example Theia app
yarn start:workflowThis will launch the example in the browser on localhost:3000.
Note that each example will be launched at the same port (
3000). Therefore it's currently not possible to launch multiple example Theia apps simultaneously.
Theia applications run in two separate process the Theia Frontend and the Theia Backend process.
In addition, the GLSP Server runs in a third separated process.
Each process can be debugged individually and the example workspaces provides dedicated debug configurations.
To start debugging open a example workspace and then navigate to the Run and Debug view (Ctrl + Shift + D).
Here you can choose between four different debug configurations:
Launch <example-name> Theia Backend (Embedded GLSP Server):
This config can be used to launch the example Theia Backend node process in Debug Mode. Breakpoints in the backend source files of the theia integration package (<example-name>-theia) will be picked up. The backend process includes the source files insrc/nodeandsrc/common. This launch config will start the GLSP server as embedded process which means you don't have to start the server process manually beforehand. However, this also means you won't be able to debug the GLSP Server source code.Launch <example-name> Theia Backend (External GLSP Server)
This config can be used when both the Theia Backend and the GLSP Server process should be debugged. It will launch the Theia Backend node process in Debug mode but will not start an embedded GLSP server process. It expects that the GLSP Server process is already running and has been started externally (e.g. through another VS Code launch config or in the Eclipse IDE).Launch <example-name> Theia Frontend
This config can be used to launch the example Theia Frontend process in Debug Mode and directly debug the sources in VS Code. Breakpoints in the frontend source files of theglsp-clientpackages will be picked up. A browser window pointing to localhost:3000 will be opened automatically.Launch <example-name> GLSP Server
This config can be used to launch the example GLSP server Java process in Debug Mode. Breakpoint the Java source files of theglsp-serverdirectory will be picked up. In order to use this config, the Theia backed has to be launched inExternalserver mode. This can either be done with the corresponding launch config or, if you are not interested in debugging the Theia backend, it can also be launched in normal mode by executingyarn start:externalin theglsp-clientdirectory.
Naturally the Theia frontend process can also be debugged with the built-in Debugging Tools of the browser.
Simply go to localhost:3000 and open the Debugging Tools of your browser.
For instance for Google Chrome the Debugging Tools can be open with F12 or Ctrl+ Shift + I.
Note Parts of the server source may be generated from a graph
.ecoremodel. Adapting this model and regenerating the source code can only be done in the Eclipse IDE because VS Code has currently no Ecore support.
All example GLSP servers are maven projects which can be imported directly into the Eclipse IDE.
In contrast to the Java support in VS Code, Eclipse also offers Ecore tooling which is required to manipulate or extend the graph Ecore models (e.g. workflow-graph.ecore.
We recommend to use the Eclipse Modeling Tools package as it already provides most needed plugins out of the box.
Only the M2E plugin has to be installed on top to enable maven support in Eclipse.
Use the file menu to import a glsp-server maven project into the Workspace ( File -> Import... -> Maven -> Existing Maven Projects).
The projects also contain a launch configuration (<ExampleName>ServerLauncher.launch) to enable debugging via the Run menu.
The general GLSP Client code is separated from the Theia specific glue code and located in a dedicated package with -glsp prefix (e.g. workflow-glsp).
This package can be easily reused when the package should be integrated with any other platform.
In addition to the Theia integration, GLSP provides the following glue code frameworks:
For a reference implementation of a example specific glue code package please checkout the project templates.
For more information, please visit the Eclipse GLSP Umbrella repository and the Eclipse GLSP Website. If you have questions, please raise them in the discussions and have a look at our communication and support options.