Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Aug 24, 2011
  1. Merge branch 'release'

  2. Fix a bug in selector functions.

    They weren't being invoked with the correct syntax (being passed the data and
    index, with the current node as the context). This commit also removes the
    d3_array wrapper, which does not appear to be necessary; I've forgotten why it
    was there in the first place.
  3. @jasondavies
Commits on Aug 23, 2011
  1. Merge branch 'release'

  2. Merge branch 'drag' of into release

    This also fixes a few bugs in the new implementation, restoring support for the
    offset between the mouse and the dragged element by reporting a delta rather
    than an absolute offset. Also, this fixes an infinite loop when an element is
    removed from the DOM.
  3. Promote the axis component to the svg module.

    I'm including the axis component in the core build because it should be useful
    in many different visualization types, similar to the other svg components. The
    chart module contains a hodgepodge of more obscure visualization types, and
    there's no reason to pull those in for more common visualizations. Perhaps most
    importantly, the axis component isn't a chart type!
  4. Tick subdivision.

  5. @xaviershay
  6. @xaviershay
  7. Add a clip path.

  8. Fix a bug in path z-index.

    The test wasn't catching it because it wasn't updating the domain.
  9. Allow custom ticks and tickFormat.

    Rather than specifying the ticks directly, you specify the arguments that will
    be passed to the scale's ticks function. I suppose there are some obscure cases
    where you might want more direct control over the generation of ticks, but this
    makes the common case easy, and we could add a tickFunction property in the
    future if we wanted to allow arbitrary control. Alternatively, you could write
    a new scale type that supports the desired tick behavior (e.g., time scale).
Commits on Aug 22, 2011
  1. Axis transitions!

  2. Tweak example parameters.

  3. Merge branch 'release'

  4. @jasondavies

    Prevent click events on drag in zoom behaviour.

    jasondavies authored
    You have to hold the mouse quite still though (see the zoom-pan
    example).  Perhaps we should have a small allowance for jittery mice?
    Fixes #243.
  5. Weight nodes according to number of links.

    The previous implementation was very unstable if a large number of nodes were
    connected to a single node (a single node connecting many). The problem was that
    the single node in the center would be moved many times for each connected node,
    never converging to a stable solution. The fix is to weight each node according
    to the number of links; in effect, the Gauss-Seidel relaxation then becomes the
    average of the connected links, rather than relaxing each link individually.
  6. @jasondavies

    "psuedo" -> "pseudo".

    jasondavies authored
  7. If fixed is set externally, make it sticky.

    Previously, if you set a node to be `fixed`, it was forgotten on mouseover. Now
    the preference is sticky. This changes the fixed attribute from a boolean to a
    two-bit integer, but truthiness remains for backwards compatibility.
  8. @jasondavies

    Add d3.behavior.drag.

    jasondavies authored
    Extracted from d3.layout.force.  Fires "dragstart", "drag" and "dragend"
    events, with a "position" property.  Note: this introduces a dependency
    on d3.behavior to d3.layout.force if used (in addition to the existing
    dependency on d3.geom).
    Fixes #249.
  9. Add missing semicolons.

  10. Expose selection and transition prototypes.

    This means that you can now extend D3's selections and transitions with custom
    functionality! Also, you can use now instanceof to see whether something is an
    instanceof d3.selection or d3.transition.
  11. Add test for time scale.copy.

  12. Expose transition id.

Something went wrong with that request. Please try again.