Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.10.0 #756

Merged
merged 40 commits into from
Aug 10, 2012
Merged

2.10.0 #756

merged 40 commits into from
Aug 10, 2012

Conversation

mbostock
Copy link
Member

@mbostock mbostock commented Aug 9, 2012

New features:

mbostock and others added 30 commits June 27, 2012 20:20
The previous method of subtracting slightly from the radius introduces
distortion where smaller circles are disproportionately reduced. For example,
subtracting 1px from the radius scales a circle of radius 5px by 0.64x, while a
circle of radius 50px is only reduced by 0.96x.

By incorporating padding into the layout algorithm, the leaf circles’ area is
still proportional to the associated value. Due to the scale-independent nature
of the layout, the specified padding value is only approximate.
This makes the previous d3.csv code a bit more generic via a d3_dsv (delimiter-
separated values) module generator. Fixes #501. (Thanks, @vlandham!)
Sometimes you want additional padding between the outer bands and the range
extent. Now you can.
You can now specify a function as the interpolate property of a line or area,
allowing you to define custom interpolation behavior.
…are respected (that is the local maxima of the curve only occurs at the local maxima of the data)
The previous implementation didn't handle polylinear domains correctly.
Previously, only the angle was being interpolated. Unfortunately, it
looks like the origin information is lost when converted to a matrix.
For example, "rotate(0 100 100)" is the identity matrix [1 0 0 1 0 0].
Interpolating the matrix decomposition seems better than dropping the
origin altogether.
Although the unicode minus is typographically correct, using the standard hyphen
is more conventional (and is compatible with standard parsing).
Rather than adopting CSS’s elaborate rules for detecting when the start and end
transform are the same type as using piecewise (i.e., string-based)
interpolation, we always use the consolidated transform transition. If you want
to use string-based interpolation, simply specify d3.interpolateString as the
interpolator. Fixes #746.
@hlship
Copy link

hlship commented May 15, 2013

I'm trying to track down if multi-value map support was ever released? It would appear it is, but I don't see support for it inside 3.1.6. Was it backed out at some point?

@mbostock
Copy link
Member Author

Yes, it landed in 2.10; see the multi-value map demo. The thing you’re looking for that never landed in master is the function-that-returns-a-map variant; I felt it introduced too many overloaded method variations and wasn’t worth the extra complexity.

@ianjorgensen
Copy link

The way i use to get around that limitation is:

.attr('attr', function(d) {
    var style = {fill:'blue', r:5};

    for(var attr in style) {
        $(this).attr(attr, style[attr]);    
    }
    return;
});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

8 participants