This doesn't appear to be supported even in IE9, which means the server
must set the correct content type to get the correct mime type
behaviour. I think this is only important to trigger XML parsing but
I'm not sure.
The treemap layout can now be set to "sticky" mode, which preserves the row
arrangements from an earlier layout. This is particularly handy for animating
treemaps, as it avoids the temporary occlusion as nodes swap positions. Thanks
to @philogb and the New York Times for the inspiration!
Release 1.7.0. Adds partition & hierarchy layouts, step-{before,after}
interpolation for line & area, sorting for treemaps, and a few bug fixes for
time format. Oh, and a bunch of tests!
First, we were using the wrong space-filling format for %d and equivalent.
Second, we weren't parsing numbers with optional leading spaces correctly.
Yay tests!
This was breaking setTimeout and setInterval in Node, since I've already
unplugged env-js' event loop. With that out of the way, we can write tests for
transitions!
The Selectors API guarantees that results are returned in document order, but
Sizzle does not, by default. So now we sort the results when using Sizzle. Yay
tests!
This fixes a bug with the usage of `require` in env-js, such that env-js now
uses proper relative paths rather than unshifting "." onto `require.paths`. The
behavior of `require` is documented here:
<http://nodejs.org/docs/v0.4.2/api/modules.html#all_Together...>
With this change in place, it's now possible to use env-js simply by require'ing
it from a script, rather than having env-js host and eval.
Also, this commit changes the initialization of env-js, such that the initial
document is immediately available when the env-js module is loaded. And, the
event loop is disabled so that env-js shuts down cleanly. This probably breaks
some parts of env-js, but it makes it much easier to use so I'm going to play
with it a bit.
The method existed previously, but it only makes sense in conjunction with the
newly-added `entries` operator; map keys are inherently unsorted. Originally I
envisioned that key-sorting could be done externally using `d3.entries`, but
that's tedious for hierarchical structures.
Still a work in progress. Need to decide on the appropriate API for representing
tree structures; not sure I want to go the heavyweight pv.dom route. May also
need rounding to exact pixel values.
Use the Floyd-Warshall algorithm to compute the shortest path between nodes, and
use that graph theoretic distance as the distance constraint for the Gauss-
Seidel relaxation. In addition, have the constraint alpha decay over time, as in
Simulated Annealing.
This allows scale interpolation in HSL space. For example:
var fill = d3.scale.linear()
.interpolate(d3.interpolateHsl)
.domain([0, 100])
.range([d3.hsl(180, .5, 1), d3.hsl(180, .5, 0)]);
You could approximate this in previous versions using d3.interpolateString, but
the new interpolation method is slightly faster and also provides backwards-
compatibility for browsers that only understand RGB.