| Age | Commit message (Collapse) | Author |
|---|
|
Number.isNaN is slated to be added in ES6, support in safari/chrome is
non standard, and we don't have to.
|
|
switching. fix #613
|
|
|
|
|
|
positions, else we store positions for the old layout
|
|
|
|
loading
|
|
<enter> breaks (need to reload to see the new node - so it is missing an attribute?
|
|
attribute diff
implement correctly layout updates (reading
layout_<layout-name>_{x,y,fixed}) for attribute diffs.
|
|
|
|
reach minimum
|
|
|
|
Record position when dragging.
Record fixed status. this is still not clear - what fixed means exactly.
|
|
|
|
d3.layout.start to initialize link lengths (linkStrength)
|
|
|
|
cypher friendly
|
|
|
|
This reverts commit ec899fb5dbbe39f45f5dcc47ea39df3a38f2229f.
|
|
|
|
|
|
|
|
|
|
|
|
attributes used are currently a bit lame, since we don't support
nested attributes. So the attribute stored is:
layouts.<layout_name>.{x,y}
where layout_name is one of: force, user, ring.
Note that force layout still takes time initially, because alpha is
always set to 1 initially. This should probably be changed when a layout
is loaded.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
on zen mode entry:
- start layout
- automatic centering mode: every tick adjust the scale and translation
to fit the visible nodes
if user drags or wheels out
cancel automatic centering mode
(layout keeps updating regardless)
implementation details: additional state 'zen_mode__auto_center' and
additional handlers for wheel and mousedown. Better to have a single
flow in the future:
{mouse wheel event, mouse down event) -> update zen_mode__auto_center (or have implicit
state via bacon) -> d3 zoom behavior
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
