opencog/atomspace-explorer

Proof-of-concept visualizer for the AtomSpace

atomspace-explorer's Issues

The atomspace-explorer doesnt render due to some issues, and new features

The atomspace-explorer doesnt render due to some issues, and new features are added.

see commits in fork https://github.com/edyirdaw/atomspace-explorer/tree/fixes for fixes

Port to Atomese API

Change request, per discussions with @edyirdaw in pull req #6

Get rid of the RESTful API and port to Atomese. If you don't understand why, let me know, I can explain. If you don't understand how, I can explain that too.

There are three ways to port to Atomese.

• One is to open a connection to the cogserver, and just send whatever scheme you want, and parse the replies. This allows you to do pretty much anything at all. If you open the connection in "quiet" mode, then parsing the results will be easier, as you won't get the extra markup to make it human-readable. This requires you to write a brand-new parser, in js, for Atomese. This would be all-new code, no one has done this before.

• A second option is to do the above, but limit yourself to the StorageNode API. This is almost the same as above, except that it's faster, tailored for good network performance and ... prints no error messages, making it harder to debug. See https://wiki.opencog.org/w/StorageNode half-way down the page.

• Either of the above would be written in js, and, because its generic, should probably be a brand-new js project, so that others can use it (and not just the explorer) I can create a git repo for you, to hold this new code.

• Write a brand-new cogserver plugin to return json. This would replace the RESTful thing. The returned json would need to be designed to fix all the mistakes in the RESTful API. This might be easier to do (??) than the first two options above. The brand-new code would be in C++. I don't really recommend this option, but ... it wouldn't be that bad. The API would be the same StorageNode API, except sending and receiving json instead of s-expressions.

So basically, if you want to write js, pick the first few options; if you want to write C++, pick the last option. I can help with any of these.

AtomSpace Explorer unable to display the following json file.

The visualizer(AtomSpaceExplorer) is unable to display this json file. Attached is screenshot of error message printed by chrome's debugger.

current node version doesn't work but version 10.24.1 does

To make the atomspace-explorer work, I used node version 10.24.1

Security vulnerability in package-lock.json

Sherman, can you take a look at this:

"The handlebars dependency defined in package-lock.json has a known moderate severity security vulnerability in version range < 4.0.0 and should be updated."

If we're stuck with a specific version, then we can live with it I guess, but if not and if nothing breaks, might as well update.

List of symmetric link types is wrong.

See src/app/connect/url-connect/url-connect.component.ts near line 18: the list of Unordered links is wrong; these need to be fetched at runtime, instead of statically compiled.

extend visualization of filtered subgraph

after filtering via double-clicking a node to show just that node and it's containing links, it would be cool to hover over another node (say whiling holding ctrl) to show that node's containing links. then double-clicking that node would extend the visualized sub-graph to include the revealed links and nodes. in the attached messy example, hovering over the node pointed to by the green arrow would reveal the red nodes and links and allow them to be added to the visualized sub-graph.