graphical-lsp
graphical-lsp copied to clipboard
Graphical language server platform for building web-based diagram editors
While resize and move can generally be regrouped in a single "Change Bounds" action, it is sometimes useful to distinguish them, at least in two cases: - Sometimes the bounds...
The resizetool does not consider any potentially bound movement restrictors. As a consequence its possible to overlap elements via Resize even if the `NoCollisionMovementRetrictor` is bound. Also there is one...
Manhattan routing has been improved so that edges don't go through elements anymore. However if 2 elements are too close to each other the edge will be routed through one...
After the client layout cycle only the computed bounds are reported back to the server. The position is only updated in the client model and remains unset at server side....
- Reduce amount of casting/type checks by use of Generics. - Maybe:1-to-1 mapping between action and corresponding handler?
(see also #62) Triggering a layout action from client side should make the diagram editor dirty
A generic point that we should start thinking about is to make it clear (by package name) what is internal and public API meant to be directly used and extended...
For the client code base (TS) we already use a linter (TSlint). Maybe we should do the same for the server code base? (probably checkstyle)
I suspect that this is a concurrency issue. If multiple operation requests are sent from the client to the server within a short period of time, the second one might...