The point is to enable fast and intuitive management of potentially large graph structures
Concepts I've come across are:
- Tree
- TreeMap
- Venn diagram
- Hyperbolic tree
Which one would you prefer or other ideas?
views:
241answers:
3
+1
A:
Best practical UI solution I have come across for large graphs is Mark Shepherd's spring graph. It scales quite well too.
Simon
2009-03-03 09:31:50
Excellent solution - not sure how it lends itself to editing though.
Goran
2009-03-03 12:10:21
What sort of editing? If you have a full CRUD cycle you'll have to write the code yourself. If you mean editing properties of the objects behind the nodes, ditto. If you mean rearranging the nodes and stroing the presentation then that can be done too - probably by extending your domain model.
Simon
2009-03-03 17:05:04
A:
skyrails is an interesting concept; editing would be done by its command line rather than direct manipulation. The implementation currently handles 10^4 nodes, which isn't a large graph by the normal measure (large graphs now-a-days means you can't fit them easily into 32 bit memory), but the concept exploits innate human 3D navigation skills, so should scale to as large as we can cope with.
Pete Kirkham
2009-03-03 10:03:59
+1
A:
You might want to take a look at GUESS which has some nice rapid prototyping features like an integrated domain specific language for graph manipulation/generation and includes a variety of graph layouts. Which means you can easily hack a demo and check if you like the interface.
thestoneage
2009-06-15 16:30:47