This issue may not be complete, but is a placeholder to address the issues with the client side topology code
The TopologyMapComponent (or VTopologyMapComponent) is a Vaadin custom client Widget/Component.
The problem with that component is, that due to the mix of technologies: Custom Component implemented in Vaadin on top of GWT deployed via OSGI it is not possible to debug the client side generated java script code.
The old mechnamisms for GWT debugging do not work anymore. The new "super debug mode" enables Java debugging via Chrome. However that somehow does not work with OSGi or some other problem. I was not able to get it to work.
In addition I think using Vaadin in the Topology Map scenario does not make any sense.
Before addressing this issue, it is crucial to have a proof of concept developed, showing that the "new" client application is not only a replacement, but should at least cover the following issues:
- Increased performance (the current performance issues in the topology map are not necessarily produced by vaadin. SVG is getting very slow when there are a lot of SVG elements.)
- Customizable (in terms of new context menu entries, new menu entries, etc.)
- Have a defined feature set (e.g. the current topology ui features, or less)