innoq/viskosity

ViSKOSity - visual SKOS browser

ViSKOSity - visual SKOS browser

https://github.com/innoq/viskosity

Getting Started

• make dependencies downloads third-party libraries
• open index.html

Dependencies

• jQuery (MIT)
• D3 (BSD)

Architecture

[TODO]

Tests and Code Coverage

The test suite is located at test/index.html. It can be run either in the browser or headlessly via make test (using PhantomJS).

Blanket.js is being used for code coverage. This requires the test suite to be accessed via HTTP, e.g. using SimpleHTTPServer or servedir:

$ python -m SimpleHTTPServer &
$ sensible-browser http://localhost:8000/test/index.html?coverage=true

License

Copyright 2012-2013 innoQ Deutschland GmbH

Licensed under the Apache License, Version 2.0

viskosity's Issues

ignore/discard duplicate edges

cf. f7d5fbea#L0R68

UI controls for pan & zoom

note that this currently relies on the user knowing about (or experimenting
with) scrolling/(double-)clicking and dragging to invoke zoom and pan,
respectively - perhaps later we'll add some Google Maps- style controls

4cfc992

highlight "exhausted" nodes

nodes within the visualization can be created either through a direct request (usually when clicking or initializing that particular node) or indirectly through relations to such an explicitly requested node

facts on the latter are usually quite rudimentary, but can be expanded through an explicit request - whereas there are usually no further facts to retrieve for the former

it would be useful if both types of nodes were distinguished visually

visualize edge direction

directed edges should be visualized as such

cf. http://bl.ocks.org/1153292

invalid node placeholders

when encountering an edge pointing to a hitherto unknown node, the graph store fills in the gap with a Node

however, this leads to "node.shape is not a function"-style errors because the visualizer expects a RenderNode

I suppose what's needed there is some sort of DefaultRenderNode, though that would circumvent the presenter layer - unless we make the store presenter-aware, which seems rather undesirable as well

Add link to running instance to README

Being able to quickly find a running demo would be very nice. Maybe link to it from the README?

suppress initial "jumpiness"

when new nodes are created, there's often a lot of movement all over the place - this should be reduced to avoid confusing users

fisheye magnification

cf. http://bost.ocks.org/mike/fisheye/

aborted attempt in 62e3408

document architecture

cf. #9

pan & zoom

pretty much expected functionality these days - would also obviate bounding box restrictions