Diagram Editors with GLSP: Why flexibility is key
summary
Eclipse GLSP claims a loosely coupled, client–server diagram framework that reached a 1.0 release with 26 contributors, adds a node-based server alongside Java, and stabilizes server APIs so model management (EMF, JSON, REST) can be swapped without touching the frontend. Rendering uses Sprotty/SVG and client editing tools send operations to a server; demos show a Java server replaced by a TypeScript one and a VS Code web instance running fully client-side, validating edits and layouting successfully.
AI-written summary · about
chapters (8)
- 0:00Introduction to GLSP
- 1:36Architecture and design
- 5:47Developing editors
- 10:48New features in 1.0
- 13:49Flexibility and integration
- 20:48Server and model flexibility
- 24:22Deployment options
- 28:39Conclusion and Q&A
related talks
32mWeb-based Diagram Editors with GLSP
29mDiagram Editors in Theia with Eclipse GLSP
40mDiagram Editors Boosted: Collaborative, Testable and Accessible diagrams with Eclipse GLSP
39mTowards a Graphical Language Server Protocol for Diagrams?
32mModeling tools go up to the cloud…
34mBuilding Web-based Modeling Tools based on Eclipse Theia
06mZero to One How to Integrate a Graphical Editor in a Cloud IDE
34mLucky in the Cloud With Diagrams