| Age | Commit message (Collapse) | Author |
|---|
|
|
|
i.e. start/end on node. It raises a scala error in neo4j (and isn't nice).
|
|
|
|
|
|
|
|
|
|
attr_diffs
|
|
|
|
|
|
|
|
""right""
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
map now, plus cached lists
|
|
of need to add nodes before links
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
clone+input-to-diff to db and back flow working
|
|
|
|
|
|
for nodes/links not helping. thinking of graph trees
|
|
|
|
Multiple fixes / changes. _bugs introduced_
Changes:
graph has two change functions (i.e. the internal API):
- commit_and_tx_diff_topo
This currently transmits, later will optimistically apply first
- commit_diff__topo
This only applies. Used on the ajax success path for commit_and_tx_diff__topo
and when changes are only local.
It signals on the diffBus
- diffBus - a Bacon.Bus that all UI listens to
- selection UI
- node/link dialogs
- main view (rz_core/update_view__graph)
Small changes:
whitespace
rename filer->filter
Completely broken:
- text entry. should use commit_diff__topo
Problems introduced:
selection doesn't work correctly.
editing not verified yet
|
|
|
|
|
|
|
|
|
|
|
|
Broken because of changed server return struct, now uses link_rm
dictionary (i.e. topo diff).
|
|
Broken during recent overzealous precondition addition
|
|
Doesn't fix node color, that is fixed in next commit
|
|
|
|
|
|
pretty large commit, but it mainly boils to
- reusing the same format clone returns to the client for topo_diff
bad bad code introduced mainly in client side, but server wasn't spared:
- graph/commit_topo__diff massages the links too much - this should not
be there at all, it should be in the correct format to begin with.
server code duplication between clone & topo_diff post processing,
should be factored out
on the good side: single transaction whenever user presses enter, and
the correct place to send back any accumulated diffs (other user
changes).
|
|
|
