The animations for expanding nodes seemed very jarring. At first I wasn't even quite sure what was occurring. I didn't look through the docs to see if it was configurable for users - but I'd recommend something a little less abrupt for your landing page. It took some getting used to and imo is a deterrent to really exploring your site.<p>That being said - it seems like a very cool library!
For force-directed graph layouts in javascript, see also Springy: <a href="http://github.com/dhotson/springy" rel="nofollow">http://github.com/dhotson/springy</a><p>Demo: <a href="http://dhotson.github.com/springy/demo.html" rel="nofollow">http://dhotson.github.com/springy/demo.html</a>
Nice, been thinking of starting an HTML 5 graph visualization myself. Though I would put less emphasis on the animation and more on the "clickability" of buttons. This jittering around makes it look broken - instead I would arrange all elements in their final position from the beginning and only use animations when a new node is created.
Are there any common reasons why a startup would be interested in graph visualization? There's clearly uses here for visualizing a social network or RDF graph, but what else?
Very interested on this. How scalable it is? How many nodes can I see?<p>I ask because it uses a Force Directed layout, I guess it will get very slow after a few thousands of nodes.<p>Looks promising though. I'll play with it...
This reminds me of the JavaScript InfoVis Toolkit, which includes similar graph visualizations but also a handful more:
<a href="http://thejit.org/" rel="nofollow">http://thejit.org/</a><p>I've used it in the past to visualize the structure of Google Wave conversations, and intend to use it in the future to visualize related products. (Unless I use this one instead, of course :)<p>I think that a graph interface like this shouldn't be the only way to get at some set of data, but at least for some people, it can be a really new and compelling way to explore it.
What a great site design which incorporates the library itself. It took me a second to realize that the graph <i>was</i> the site navigation, and it kind of caught me off guard. In a good way.
wow, this is really well done! i love the user interface for changing parameters (friction, gravity,etc.) and just overall smoothness<p>seems as if the algorithm grows unstable for very high node repulsion. even with a few nodes you can tell it is getting caught in a local energy minimum, plus the oscillations are jarring. maybe just cap the repulsion strength at 50k?<p>have you thought about adding hover text, upon a mouseover of the vertices?<p>also, maybe instead of spring tension, one could use fixed lengths given by the weights of another text file. giving user generated meaning to the edge lengths.
The library itself is nice, but I feel the need to ask - why the hell does this have a jQuery dependency? jQuery exists primarily to plug the holes/inefficiencies in older browsers, but this thing isn't guaranteed to work in older browsers due to its reliance on web workers in the first place.<p>There's nothing wrong with standard Javascript provided the environment is sane.