npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

d3-force-surface

v1.0.1

Published

A multi-surface elastic collision force type for the d3-force simulation engine.

Downloads

210

Readme

d3.forceSurface

NPM package Build Size NPM Downloads

A multi-surface elastic collision force type for the d3-force simulation engine.

It can be used, for example to keep nodes within boundaries or in a game of Pong.

See also d3.forceBounce.

Quick start

import d3ForceSurface from 'd3-force-surface';

or using a script tag

<script src="//unpkg.com/d3-force-surface/dist/d3-force-surface.min.js"></script>

then

d3.forceSimulation()
    .nodes(<myNodes>)
    .force('surface', d3.forceSurface()
        .surfaces(<mySurfaces>)
    );

API reference

| Method | Description | Default | | ------------------ | -------------------------------------------------------------------------------------------------------------------------- | ------------- | | surfaces([array]) | Getter/setter for the list of surface lines | [] | | elasticity([number]) | Getter/setter for every collision's coefficient of restitution, aka elasticity. A value of 1 represents a purely elastic collision with no energy loss, while a 0 will fully eliminate the bounce in the collision direction. Values >1 can be used to introduce acceleration at each collision. Values <0 are not recommended. | 1 | | radius([num or fn]) | Getter/setter for the node object radius accessor function (fn(node)) or a constant (num) for all nodes. | 1 | | from([fn]) | Getter/setter for the surface object starting point accessor function fn(surface). It should return a two coordinate object: {x,y} | surface.from | | to([fn]) | Getter/setter for the surface object ending point accessor function fn(surface). It should return a two coordinate object: {x,y} | surface.to | | oneWay([bool or fn]) | Getter/setter for the surface object "one-way" flag accessor function (fn(surface)) or a constant for all surfaces. This flag indicates whether collisions of nodes against the surface should occur in both directions of movement or only in one (when the node is moving in a N>S orientation according to the W>E line axis), effectively ignoring collisions in the other direction. | false | | onImpact([fn]) | Callback function triggered at every collision, with the signature onImpact(node, surface) ||