| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
still have new/edited node visible at 0,0 briefly while edited
The fix is by using d3 enter/update/exit and not killing all the nodes
every time we run update.
|
|
|
|
|
|
|
|
|
|
|
|
- load_node_by_id_attr()
- response_wrap()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
testing
|
|
|
|
|
|
|
|
|
|
- DBO_load_node_set_by_attribute
- DBO_load_node_set_by_id_attribute (convenience op)
|
|
|
|
|
|
|
|
|
|
|
|
input_to_DB_property_map property mapping argument
|
|
|
|
according to my yet unwritten coding conventions:
1. no single line blocks
2. no empty lines without a good reason
|
|
verbose logging
|
|
Previously:
prefix #a does #b => ((a, b), [(a, b, "does (prefix)")])
now:
=> ((a, b), [(a, b, "prefix #a does #b")])
|
|
|
|
|
|
|
|
|
|
deleted
|
|
|
|
|
|
|
|
|
|
|
|
Auto suggest doesn't work for nodes loaded from local storage
Fixes #60
|
|
Works around a problem where you load rhizi with a small window size and then
enlarge it, since we don't dynamically change the svg size (and it is
fixed instead of filling a parent div or such) we lose access to a lot
of the screen (i.e. can't drag nodes there, can't see anything there,
etc).
|