That's pretty cool; judging by the 'crappy demo' it has potential but would need some important features to be useful, such as: labels, improvements regarding the visual appearance & clarity, and node selection to isolate connections.
I'd still love to see a graphviz equivalent for JS that does layout for digraphs. This looks cool if you need undirected graphs, but doesn't seem to have any digraph support.
The tree layout supports some fairly complicated tree structures, including ones that alternate or have different configurations for leaves: http://www.gojs.net/latest/samples/tLayout.html
Disclosure: I'm a developer of this library and it is not free.
On the technical side: D3 is built on svg, looks like this is built on canvas. There are a few implications to both of those as far as compatibility and performance, but shouldn't make a difference in most cases.
In general, D3 looks to be a more general purpose graphing tool (also maps, multiple charting types, and graphs), while this is more single purpose.
upvote, because this is the correct answer to the question "how does this work differently from d3," as opposed to the question, "what are the advantages/disadvantages of using this over d3."
a quick f12-for-firebug reveals that sigma indeed uses the canvas element. i haven't actually used the library, but it appears ( https://github.com/jacomyal/sigma.js/blob/master/package.jso... ) to in fact be built directly on canvas, which is impressive in some sense but probably does duplicate a lot of work that could be avoided by using a generic-canvas-drawing-but-not-specifically-graph-drawing library.
d3 stands for "data-driven-documents" and is actually not specific to graphs. at the core, it's about (as the expanded name suggests) connecting html documents to javascript data structures. of course, lots of libraries -- angular, etc. -- may be described in such general terms, so more specifically, d3 is useful when you have both a lot of data (or a lot of structure to your data) and a lot of html elements to layout according to that data.
it just so happens that <svg> is now actually a tag in html ( : / ? i mean that, the advances in the browsers themselves, was news to me, when i looked at d3 for the first time), so yeah, d3 is most commonly used when the elements you want to lay out are a bunch of svg tags.
anyway, i really like d3 (and probably would like three.js, for that matter, if i took the time to toy around with it) b/c i think it does one fairly general thing, does it well, and has practical applications.
to add up on the other replies: sigma.js is plug-and-play, very easy to draw a force-directed graph with nice built-in features. d3.js requires more work to get to the same result.
Advantage of d3.js is that it is easier to customize the display you want.
other difference: sigma.js implements "force atlas 2 " algorithm - like the one found in Gephi, which may be more suitable for some graphs (when you want to highlight community structures)
Sigma is significantly faster than D3 for drawing large graphs; however, it's only able to draw graphs. D3 is a multipurpose library for many different kinds of visualizations.
Actually, as with d3, you can develop your own network visualization layouts.
The main difference is that sigma only deals with graphs drawing, so it deals without effort with drag and drop (mouse or touch), scaling the graph to the screen, smooth zooming (with mousewheel or pinch)...
It depends on where your data's coming from, but I tend to avoid doing layout in JS, and instead pre-lay-out the data using Gephi or graphviz (possibly in a cron job if the data changes), loading the hardcoded initial layout in JS and using sigma.js only for display/interaction. In the non-cron case, also lets me tweak the layout a bit through trial and error or trying out different algorithms, to get something I like. Obviously doesn't work for every possible usage, though.
Hello all,
I'm a student at MIT working on a project building a general-case platform to create and explore graphs called WikiNets http://wikinets.co.uk/ with the goal of enabling half-formed ideas separated across different people's heads to come together (e.g. making a custom platform for http://hackathonprojects.tk/). Anyone want to work on this with us? I would love to find others who think on this same wavelength and I lament that (ironically) there's not yet a way online for people to find others with synergistic ideas! Feel free to poke me at jcole@mit.edu
Incidentally, we're currently using D3, but welcome suggestions as well!
I've used both Sigma.js and Arbor.js (http://arborjs.org/) extensively. I liked Arbor a bit better for smaller graphs, because of its flexible API and separated drawing and math components. Unfortunately Arbor seems abandoned by the author last updates were two years ago), so i guess Sigma might be a better choice right now.
Want to get started with PHP and GEXF to create dynamic input files for sigma.js? http://stackoverflow.com/a/14719375 If there is enough interest, I will create a GEXF lib for PHP.
We tested this with some Super Bowl social data we collected as part of a project.
First: looks really good, very easy to integrate.
Next: Am I missing it, or is there no way to visually represent the edge strength? Everything appears to be a 1px connection no matter how strong the edge.
I know it's pretty simple to run the examples yourself, but it would be nice if they were hosted on sigmajs.org. Great work, though. Pretty sure I'm going to try this today or tomorrow.
I keep this in mind. We need to find an easy way to export examples formatted with the good template etc... before putting anything public, to ensure it's not too hard to update the production server when we release sigma.js.
https://github.com/frewsxcv/graphosaurus
And a really crappy demo (give it a few seconds to load):
http://vps.rwell.org/index-eve.html