stucco-archive / ontology-editor Goto Github PK

When a node of interest is selected, move it and its links to the front so they can be read more easily.

Use input files from this repo:

https://github.com/stucco/graph-validation

Right now, any sort of edit restarts the entire graph.

When a node is added, should the entire graph be reset? I'm not familiar with a way to force.tick() on only one node (keeping the others fixed).

When a node is edited (updated), the graph could remain the same (no tick).

When a node is deleted, the graph could also remain the same (no tick).

@jgoodall, thoughts?

I commented it out in the Gruntfile.js. We should update the grunt modules occasionally and hope it gets fixed.

So when reopening the same file, nodes are in same position

https://github.com/stucco/ontology

d3.force fails if you feed it an edge with no corresponding vertex.

This happens in the tool if you remove a vertex but don't remove any corresponding edges.

To fix this, any orphan edges must be filtered. Additionally, the user should be notified of such edges in some way. Here are some possible ways of handling the user side:

• highlighting the lines in the textarea
• displaying a list of _ids that a user can search for (easiest!)

• e.g. when the text in textarea isn't properly formatted json

The user should be notified of orphan edges (edges in the file that have missing nodes) in some way. Here are some possible ways of handling the user side:

highlighting the lines in the textarea
displaying a list of _ids that a user can search for (easiest!)

Two possible solutions:

• Switch to : http://bl.ocks.org/mbostock/1153292
• Merge links and text for drawing: dstAddress, srcAddress

See, depot.js

See, screenful.js

See, mousetrap

Mappings

/ - find
e - focus on editor
f - full screen
u - undo
r - redo

See, dropzone

This might be achieved by pre-defining node and link groups (two s).

To replicate:

1. add new node
2. add link from existing node to new node

See, history.js