NabLab from Eclipse to VSCode thanks to LSP & Sirius Web
summary
Migration moves the Eclipse NabLab RCP into a VSCode extension using Xtext-LSP for language services and Sirius Web for diagrams, reusing the same Xtext grammar and the original .odesign via a Sirius Web compatibility layer. The VSCode build bundles a Spring-backed Sirius Web app, the LSP server, and extensions (~90 MB, ~170 jars). Editor features (completion, coloring, hover, error checks), LSP-driven LaTeX image updates, and code generation commands reproduce RCP behavior; diagrams render but require manual refresh. Migration succeeds with nontrivial adaptation and some Sirius limitations.
AI-written summary · about
chapters (14)
- 0:00NabLab migration intro
- 1:31What is NabLab
- 3:39Demo: NabLab Eclipse RCP
- 8:27Why migrate to VS Code
- 9:10Reusing Xtext grammar challenge
- 10:34Implementing Xtext Language Server
- 11:40Reusing editor tooling
- 13:34Sirius Web diagram migration
- 16:46Math formulas in VS Code
- 18:15Code generation in VS Code
- 20:05Demo: NabLab VS Code
- 21:53Packaging VS Code extension
- 23:00Migration success
- 24:04Q&A
related talks
40mDiagram Editors Boosted: Collaborative, Testable and Accessible diagrams with Eclipse GLSP
32mRefactoring via the Language Server Protocol
32mModeling tools go up to the cloud…
44mIntegrating IDEs with Dotty, The Experimental Scala Compiler
21mAconite: Towards Generating Sirius-Based Graphical Editors from Annotated Metamodels
32mWeb-based Diagram Editors with GLSP
06mZero to One How to Integrate a Graphical Editor in a Cloud IDE
34mBuilding Web-based Modeling Tools based on Eclipse Theia