Open
Conversation
added 6 commits
September 4, 2015 17:22
This is going to end up being a "force direction" example...but just wanted to get a simple layout example working first.
| return res; | ||
| } | ||
|
|
||
| function o() { |
Contributor
There was a problem hiding this comment.
not a huge fan of the function names o and g here...very non-descript
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This introduces a new component/primitive/concept for e3 that allows for isolated positioning engines. This can be used for Force Direction, Collision Detection, or anything that might determine how items are positioned that does not fall into the idea of a scale. Part of the plan is to also support Asynchronous layout generation too (perhaps your position algorithm would be better served running in a Web Worker or something).
The current example
/force-directionwill eventually become a force direction example (I don't think E3 should support force direction out of the box, but this example would show how you could use a force direction library to get that). But, for now, it demonstrates the concept of how a layout generates some of the position data, based on scales.Only TODOs on this PR, pending feedback, are: