Miro Spönemann

They are for computing anchor points of edges on the border of source / target nodes, specifically for the Manhattan router which uses orthogonal bend points. The anchor computation depends...

The model elements have an optional `anchorKind` property: https://github.com/eclipse/sprotty/blob/master/packages/sprotty/src/lib/model.ts You could create your own subclasses of SNode.

Thanks! Let's keep this open so we can find the content when we revisit the documentation. It would be great to have a dedicated website for Sprotty that hosts the...

I moved this to [eclipse/sprotty](https://github.com/eclipse/sprotty) because it's a frontend issue. We could introduce a special layout (or layout option) to support elements outside of their container's bounds. This does not...

The easiest way to see the demos is to start a Gitpod workspace: https://gitpod.io/#https://github.com/eclipse/sprotty Then open the exposed port 8080 in a new browser tab.

Adding a layers would be a very powerful concept, but also introduce a huge amount of complexity. Generally I'd be fine with encapsulating low-level operations like reordering elements to control...

Thanks for the feedback! This is certainly valuable, and we should consider it when preparing the final API before we publish v1.0.0. @planger @tortmayr @ndoschek WDYT about the codicon css...

Usually I would use the default polyline router when the layout is computed automatically, to avoid side-effects of the post-processing applied by other routers. ELK has an option for changing...

[LanguageServer](https://github.com/eclipse/lsp4j/blob/master/org.eclipse.lsp4j/src/main/java/org/eclipse/lsp4j/services/LanguageServer.java) is an interface. How could LSP4J provide this functionality? Add an abstract class that implements that interface, to be used as superclass for your implementation?

I tend to regard such default method implementations as out of scope for LSP4J, but we can keep this open to see whether there is more interest about that.