protovis + transitions
jerome cukier
and had cool things to show?
thanks,
jerome
Daniel
What is the status of animations? Is there a git branch one should
track?
/D
JanWillem Tulp
didn't find it.
I am working on my next submission for a visualizing.org contest on
urban water, and I am currently rebuilding a basic Protovis
visualization I did in D3, the new visualization framework by Mike
Bostock. That one will have some transitions in it (it already has
some actually, but the current ones may become obsolete... ).
From what I've heard from Mike he's gonna put some of the good stuff
from Protovis in D3, rather than the other way around...
Daniel
There must be some sort of limit on how many visionary frameworks
Stanford superstars can produce in a year? ;)
Mike?
ps. Where does one discuss D3?
Mike Bostock
D3 and also provides a brief introduction tailored towards Protovis
users. I should have that available today. It probably makes sense to
create a separate discussion group for d3 (see:
http://groups.google.com/group/d3-js), but I'm equally happy to
continue discussion on D3 in this group, given that they're closely
related.
Mike
> --
> You received this message because you are subscribed to the Google Groups "protovis" group.
> To post to this group, send email to prot...@googlegroups.com.
> To unsubscribe from this group, send email to protovis+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/protovis?hl=en.
>
>
Daniel
I'm getting more and more familiar with Protovis' syntax so I'm glad
to learn D3 is not a distant cousin. (And the performance and
versatility seems to be impressive!)
Thank you for all the good work.
/D
Mike Bostock
of the D3 website:
http://mbostock.github.com/d3/
And here's a direct link to the tutorial; though, I'd recommend
reading the D3 overview and browsing the examples if you are reading
about D3 for the first time:
http://mbostock.github.com/d3/tutorial/protovis.html
Lastly, the TL;DR version:
"""
Where D3 and Protovis differ is the type of visualizations they enable
(the what), and the method of implementation (the how). While Protovis
excels at concise, declarative representations of static scenes, D3
focuses on efficient transformations: scene changes. This makes
animation, interaction, complex and dynamic visualizations much easier
to implement in D3. Also, by adopting the browser’s native
representation (HTML & SVG), D3 better integrates with other web
technologies, such as CSS3 and developer tools. Our hope is that this
makes D3 not only more powerful, but easier to use.
"""
It's been a blast seeing the adoption of Protovis over the last two
years. I owe a big debt of gratitude to our users and contributors;
thank you! I literally can't wait to see the awesome things you do
with D3. :)
Please continue to send feedback, questions and pull requests!
Cheers,
Mike
Oliver Rolle
D3 looks awesome!
The transition is imo very valuable and I missed this feature in protovis badly! It creates a unique (not often seen) usage experience. At the moment I think it would be possible to use this feature alone for a viral product marketing strategy because it looks like magic and attracts peoples perception :-)
The next thing I like is, that a developer access low-level browser functionality directly, which is more flexible for future technological changes in browsers, especially the upcoming 3D-technologies in browsers.
What are your goals with D3 and what are the next milestones of D3?
best regards
Oliver
Jan van Gemert
I'm much impressed by the extra set of features it gives and the speed
improvement over Protovis (eg. pv.brush+link vs d3.scattermatrix).
Despite the extra complexity and the deferred burden of having the
user know the underlying tools (svg, css3) the generalized framework
seems quite powerful, retaining full control over the whole document.
Like a protovis for XML.
I guess you could even use d3 to produce VML, and be IE compliant.
In the multiverse of the web specifications, it seems to give One
framework to rule them all, One selectAll() to find them, One enter()
to bring them all, And in the darkness bind them ;)
I'll start and play with d3, it seems definitely the way forward.
Impressive work!
Jan
(JIT before the visweek deadline? :) )
Pedro Alves
On 03/07/2011 04:06 PM, Jan van Gemert wrote:
> I guess you could even use d3 to produce VML, and be IE compliant.
If you're directly generating svg, how could this be done in an abstract
way? Even with svgweb, I don't see how the same code could be written in
a browser-independent way
Any thoughts?
-pedro
Mike Bostock
The design goals are discussed in more detail on the website, but to
summarize: dynamic scenes with animation & interaction, better
debugging, and full support for web standards (HTML5, CSS3, SVG). My
immediate development objectives mostly involve new feature
enhancements such as layouts and scales, as well as broader test
coverage and documentation. Feel free to use GitHub to file feature
requests or follow along.
> I guess you could even use d3 to produce VML, and be IE compliant.
As Pedro says, while possible, this would be a lot of work; D3 is not
a compatibility layer, so you'd have to code twice for SVG and VML. If
you want to be IE-compliant without doing (more than) twice the work,
I'd use SVG Web. D3 supports Sizzle out of the box, but there are a
few additional tweaks needed to support SVG Web. Chad Burt has a fork
here:
https://github.com/underbluewaters/d3
For simple stuff, you could also use pure HTML and avoid SVG entirely.
You might also consider falling back to a static image, given
performance limitations of older browsers that can't be abstracted
away.
Mike
(cough)