| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
doesn't complain either
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
i.e.
related =
|selected| == 1 N(selected)
else intersection_{s in S}{neighbours(s)}
|
|
selected nodes - nodes the user selected directly, via search or click.
related - nodes that we choose to show the user as a result of the
selection made.
|
|
|
|
|
|
It was buggy and did not deal with overlap.
Renamed to neighbourhood.
|
|
|
|
|
|
|
|
nodes; resolve #393
shift selection still works, but now it's a bit not obvious when you
shift select a link:
- it acts as inverting the source and destination node.
- an alternative could be to special case for both or single or none of
the nodes already selected
- a correct fix would be to track separately the nodes and links
selection states. Right now we only have a nodes selection state
(array of root nodes, the ones the user selected, and array of
selected nodes, the ones we highlight as such).
|
|
|
|
add shim requirement for Bacon to have jquery loaded first, since Bacon
patches in asEventStream (and other APIs).
Undo the Bacon_wrapper non fix:
git grep -l Bacon_wrapper | while read f; do sed -i -e s/Bacon_wrapper/Bacon/g $f; done
|
|
|
|
Fixes #358
Implementation limitations:
- uses hasOwnProperty for search, and further filters on strings. So
technically could be oversearching - i.e. string properties that are
not attributes. We should keep an attribute key on Node and Link
- there is no selected link, just selected nodes. So we select both
source and destination. Opening issue #367 for this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from declaration
|
|
before Bacon
|
|
|
|
|
|
|
|
work)
|
|
used for merge)
|
|
|
|
|
|
|
|
|
|
Should have two functions for node+link class setting, one for
temporary, one for not, instead of passing this constant (since
construction time) value along.
|
|
|
|
|
|
|
|
1. seperate root_nodes/selected_nodes
2. move graph update to rz_core.js
Fixes #213
|
|
|
