Permalink
Commits on Jul 20, 2011
  1. Merge branch 'release'

    mbostock committed Jul 20, 2011
  2. Fix a bug in histogram.frequency.

    mbostock committed Jul 20, 2011
    The logic was inverted. Oops! But now there are tests. Yay!
  3. Add d3.time.scale.utc.

    mbostock committed Jul 20, 2011
    Also fix a bug in d3.time.hour in regards to daylight savings.
    Also fix a number of tests that weren't testing the desired functionality.
  4. Add d3.time.scale.

    mbostock committed Jul 20, 2011
Commits on Jul 19, 2011
  1. Don't add padding to root node.

    jasondavies committed Jul 19, 2011
    Also, optimise internal scale() function slightly.
  2. Add support for padding to treemap layout.

    jasondavies committed Jul 19, 2011
    The new "padding" property is an array of [top, right, bottom, left], or a
    function that returns such an array for a given node.
  3. Organize tests into modules.

    mbostock committed Jul 19, 2011
Commits on Jul 17, 2011
  1. Merge branch 'release'

    mbostock committed Jul 17, 2011
  2. Update source files.

    mbostock committed Jul 17, 2011
  3. Update generated files.

    mbostock committed Jul 17, 2011
Commits on Jul 16, 2011
  1. Fix typo.

    jasondavies committed Jul 16, 2011
Commits on Jul 15, 2011
  1. Minor optimisation.

    jasondavies committed Jul 15, 2011
Commits on Jul 14, 2011
  1. Prevent RangeError in Safari.

    jasondavies committed Jul 14, 2011
    For very large force layouts, Safari was throwing "RangeError: Maximum call
    stack size exceeded".  I think this is due to Safari having a smaller call stack
    than Chrome and FireFox.  In any case, this fix replaces forEach with a while
    loop, which should be faster in all browsers as well as reducing the call stack
    size needed and thus fixing the Safari issue.
Commits on Jul 12, 2011
  1. Better protection against NaN and negative values.

    jasondavies committed Jul 12, 2011
    Also, a more symmetric prevention of NaN in the scoring function from Mike:
    "rmax is 0 if and only if s is 0, so it is equivalent".
  2. Better fix for zero-area nodes.

    jasondavies committed Jul 12, 2011
    Instead of filtering them out, we fix the root of the issue instead, which is
    that the scoring function "worst" was returning NaN due to calculating 0/0,
    instead of Infinity.
Commits on Jul 10, 2011
  1. Allow multiple zoom behaviors to coexist.

    mbostock committed Jul 10, 2011
    Any event handlers on the window need to manage global state, as they will be
    replaced when another zoom behavior is created.