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

Use d3 following its own philosophy #441

Open
shamansir opened this issue Feb 18, 2017 · 2 comments
Open

Use d3 following its own philosophy #441

shamansir opened this issue Feb 18, 2017 · 2 comments

Comments

@shamansir
Copy link
Owner

shamansir commented Feb 18, 2017

Since I've chosen d3-selection to serve as (being honest now) jQuery alternative, it is used in a wrong way now, in case of RPD. There are mostly no arrays of data etc., and no parent/children hierarchies of selections, in a d3 way of thinking. (See docs-patch example with Planets as a proper implementation of it).

When I've changed from d3_tiny to actual new version of d3, I discovered those issues immediately, for example d3/d3-selection#106 (comment).

@shamansir shamansir added this to the v4.x.x milestone Feb 18, 2017
@shamansir
Copy link
Owner Author

Could be hard since in our case the data for children is not ready when we create a parent (root has no patches at start, patch has no nodes at start, nodes have no inlets/outlets and start & s.o)

@shamansir
Copy link
Owner Author

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

No branches or pull requests

1 participant