background preloader

Graph Computation, Layout, Algorithms for JavaScript

Graph Computation, Layout, Algorithms for JavaScript

arbor.js Raphaël—JavaScript Library Demos - JavaScript InfoVis Toolkit JavaScript InfoVis Toolkit Create Interactive Data Visualizations for the Web Home ● Download ● Builder ● Donate Area, Bar and Pie Charts Sunburst Icicle ForceDirected TreeMap SpaceTree RGraph HyperTree Advanced/Other copyright © 2013 SenchaLabs - Author: Nicolas Garcia Belmonte Springy - A force directed graph layout algorithm in JavaScript. D3.js - Data-Driven Documents TechCrunch

blog Hey friends! I gave in and finally integrated <canvas> support into JSViz, and just in time for the Safari 3 Beta (which I'm really digging so far)! Note: To render with canvas, you'll need Firefox 1.5, Safari 2.0, or Opera 9. JSViz gracefully degrades to alternative rendering platforms (SVG, HTML) when support is not present. Continue reading "Viva la Canvas" » I get lot's of e-mails from JSViz users that want to know how to integrate tooltips into their graphs. Yeah, that's super easy and everyone is always asking. So I had a moment and here it is: Continue reading "Everybody wants tooltips" » In the process of integrating vector graphics into JSViz, we developed svg2vml, a library that provides a common interface for scripting vector graphics in browsers that support either SVG or VML. The library lives in the Google Code project hosting site at Howdy friends, I've just uploaded another patch to 0.3.3. Improved SVG Rendering Performance

Cyan | Software Defined Metro Networks Processing.js Demos below! As a sort-of reverse birthday present I’ve decided to release one of my largest projects, in recent memory. This is the project that I’ve been alluding to for quite some time now: I’ve ported the Processing visualization language to JavaScript, using the Canvas element. I’ve been working on this project, off-and-on now, for the past 7 months – it’s been a fun, and quite rewarding, challenge. The full scope of the project can be broken down into two portions: The Processing Language The first portion of the project was writing a parser to dynamically convert code written in the Processing language, to JavaScript. It works “fairly well” (in that it’s able to handle anything that the web site throws at it) but I’m sure its total scope is limited (until a proper parser is involved). The language includes a number of interesting aspects, many of which are covered in the basic demos. The Processing API The second portion of the project is the full 2d Processing API.