Click on the names to add the icons to the "Icons" tab
URL to load the topology from
Save to text / load from text
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
How to use
Drag and drop. Connect the blue dots with lines. Doubleclick to add the annotations.
Control-drag the blue dots to clone them. Click on the text links in the "library" to add the icons to the "Icons" tab.
"Save" the JSON into the textbox. "Load" JSON from the textbox. Also you can have the JSON on a server and you can "load" it from an URL, like this
This little hack is standing on the shoulders of giants:
The few kilobytes of glue code to make this working together written by Andrew Yourtchenko a while ago in a few evenings.
I've done this mainly because I wanted to try and see what happens and how it looks like.
There are still quite a few relatively cosmetic bugs, but I consider it working "good enough", so most probably won't fix them. If you find something and fix it, feel free to send me the diff to ayourtch [at] gmail, and I'll put it in.
I deliberately coded it in such a way that after the initial loading everything runs only on the client. In any case, if you prefer to be on the safe side, you can download the tarball and run it locally.
NB: if you view the source, you will see that I hooked the google analytics - merely for the purposes of looking how much use this page gets, and removing it in case it gets too popular, before the kind guys at employees.org get too much load. The version in the tarball obviously does not have this tracker.
NB#2: Obviously, if you try to load the JSON over a remote URL, the method of doing that is inherently insecure, so you will first want to visually inspect the content of the URL in the browser - to ensure that the JSON is indeed the only content there.