Live data from Hacker News

Protovis - a graphical data visualization framework using JavaScript and SVG

vis.stanford.edu

21–23 of 23 posts

Re: Protovis - a graphical data visualization framework using JavaScript and SVG

#21
post #6

See also d3, a newer visualization framework from the same primary author. Similar to protovis but with a greater focus on updating and animation. http://mbostock.github.com/d3/

Thanks! But I can't find which browsers it supports, or which features it supports per browser.

It supports any browser in theory, as it just operates on the DOM. You may want to load Sizzle.js beforehand to give you more powerful CSS selectors for older versions of IE.

In reality you will want to use SVG to create anything impressive, so this means WebKit (Chrome, Safari), Firefox, Opera, IE9. And potentially IE6-8 if the SVGWeb Flash fallback supports all the SVG features you need.

Re: Protovis - a graphical data visualization framework using JavaScript and SVG

#22

I'm looking through the source, specifically the jsDoc comments. Does anybody know what "[v]" means in this context: * @param {function} f function to execute on each value in the array. * @param [v] object to use as the first argument to the first call of As I understand it, the parameter type is specified with curly brackets, like, "{function}" in the line above.

"v" is the variable name, and the square brackets around it mean it's optional. There is no type specified for this parameter, so nothing in curly brackets.

Are these the definitive docs: http://code.google.com/closure/compiler/docs/js-for-compiler...

Because I don't see square brackets for optional in there.

Re: Protovis - a graphical data visualization framework using JavaScript and SVG

#23

Earlier quoted context omitted.

"v" is the variable name, and the square brackets around it mean it's optional. There is no type specified for this parameter, so nothing in curly brackets.

Are these the definitive docs: http://code.google.com/closure/compiler/docs/js-for-compiler... Because I don't see square brackets for optional in there.

It might not be part of the official spec, but it's a convention that we use in my office and I've seen a number of other places as well.

[edit] Here we go. This is the JSDoc we use, and presumably Protovis does too. Take a look at the Optional Parameters section: http://code.google.com/p/jsdoc-toolkit/wiki/TagParam

Post reply on HN