As I mentioned briefly before I moved on to a force-directed rendering
algorithm for our application.
I've forked JIT at v1.1.3 and published my changes on github :) [1]
You can find a small demo of it working at [2].
Hit the 'URI' button to make it do something interesting.
Sorry about the lack of documentation, I don't have time to learn the
markup format and am a bit rushed in development at the moment.
Enjoy,
Marcus
1] http://github.com/mcobden/jit/tree/master
2] http://www.rkbexplorer.com/~mc1204/dotAC-ui-backup/
I just saw your blog post on this; looks good :)
Incase anyone's interested; the interface I was developing this for is
viewable here: http://www.rkbexplorer.com/~mc1204/ui/
It's a mock-up of a Semantic Web 'Co-reference' management system. The
idea is that something (in the demo: people) may be represented by a
number of different identifiers (in the demo: URIs) and you need some
way of maintaining collections of these links.
Also you need to be able to tell where incorrect links have been made,
and the interface at the bottom is to allow you to explore this.
Re: papers
I didn't really read any this time round; I kind of did it from memory.
The previous iteration was an SVG based graph rendering which you can
find here:
http://gradf.marcuscobden.co.uk/graphDemo.xhtml
It's fun to play with but it's a lot nicer (visually) to finish the
computation and then have a smooth animation rather than doing the
layout in real-time. That's one of the things which I liked about jit :)
Also SVG DOM manipulation is way too slow for the real-time animation :P
The paper I read when implementing my old engine was this one:
http://www.lirmm.fr/~artignan/bib/QUIG-EADE-00-1.pdf
It has a good method for how to optimize the node-node forces.
Marcus