withjam / ml-lodlive Goto Github PK

When writing a wrapper for ml-lodlive, the same as with ml-lodlive-ng, I find that sometimes the node moves when clicking on the relation bubble instead of opening the new node.

The problem can sometimes be seen here, but I found the issue to be far worse one my own machine.

I've found a solution/workaround, as discussed here.
The changes can be found on this PR:

If lodlive.options.connection['http:'].useForInverseSameAs is false, findInverseSameAs() just terminates, without invoking the callback

This will help eliminate lodlive.xqy

please? :)

When loading a node it appears to try to load an image that doesn't exist - perhaps an ajax loader - until the content appears

I was playing with an implementation of zoom buttons on the lodlive legend included in ml-lodlive-ng, but I notice that once you have transform scaled the lodlive-graph-context div (which works reasonably well), new relations, and nodes when expanding, are drawn in the wrong place. Looks like a counter-measure needs to be taken to compensate for this.

Maybe better if lodlive would come with an object that provides zoom functions itself..

I am running with triples for linking only, and don't really have nice labels that go with them. LodLive is showing noName for the start node, which is very non-informative. I'd prefer if it showed <iri> instead.

Strangely enough, on following relations the iri is shown, but without the angular brackets. That is inconsistent with the start node.

I'm using ml-lodlive over a very large dataset. Some of the entities have multiple (100s) relationships between them.
For example:

• Sam is Bananas
• Sam went Bananas
• Sam ate Bananas
• Sam dislikes Bananas

On my large dataset the label on the line between the two node circles can look crazy since it is rendering every single relationship.

I've forked the repo here with a candidate fix. It provides a new UI.maxRelationshipsToRender flag which when exceeded renders ' and N more' on the label.

For example, on the line between Sam and Bananas it would render "is, went and 2 more".

Let me know if you want me to raise a PR.

Can we access to a demo of the project ? and also what's the differences with original lodlive?

Thanks.

I'd like to make the legend respond to what data is actually loaded. For instance suppress relations from the legend table, that are not shown. In future I might like to be able to click a relation in the legend, and make that expand all such relations in the lodlive chart. Or maybe I'd like that to cause filtering to be applied, so that all not-selected/clicked relations are hidden from the lodlive (new sparql with extra filter for less data?)

Makes injecting css from bower dependencies possible..

The profile.js is quite confusing and overly complex. Try to simplify it for easier customization.

CSS scale transforms mostly work to provide a zoom capability, but the lines are drawn assuming an 80px node ...

I had to override the /v1/graphs/sparql endpoint to by-pass a bug, but the query param name is hard-coded in ml-lodlive. And REST extensions require adding rs: prefix to params..

If enabling remove/close, you should not be able to remove a rootNode when it is last node

Had a strange issue that made lodlive stop working. Another script overwrote the global jquery variable so that none of the plugins were available to lodlive anymore. Angular.element().lodlive worked the whole time - most likely because angular keeps its own pointer to jquery. Lodlive may need to do the same to prevent this type of thing from happening with other external scripts.

The ability to remove an expanded node from canvas and have link icon be toggled.

When clicking nodes to drag them, they jump away with an offset that seems to equal the offset of the ml-lodlive-ng container. Would be nice if 0.3.1 could be patched for this..

LodLive.init() currently appends, but it should first clear the graph. See grtjn/ml-lodlive-ng#9

Currently two-finger scrolling in Mac is easy, but navigating is otherwise difficult. Provide support for clicking and dragging on the background area to allow the user to scroll around the graph.

I can't get this to work as I am getting an error with the semmod:results-payload function:

XDMP-TOOFEWARGS: (err:XPST0017) semmod:results-payload($headers, $params, $result) -- Too few args, expected 4 but got 3 . See the MarkLogic server error log for further detail.

After checking the results-payload function signature, I can verify that it is expecting 4 arguments, the 4th argument being a 'callback'. I am using ML8 and EA4 ML9.

Any suggestions how I could fix this issue?

There seems to be something odd with the file. It looks like RDF originally, but contains embedded sem:triple XML. Do you have an original copy?

As workaround, just ingest as XML, instead as RDF. The triple index will pickup the sem:triple XML directly..

I think bootstrap, and font-awesome have plenty alts. Makes this easier to handle as bower dependency..

I think the only dependency is ui.draggable. Should be easy enough to write drag/drop directly into the codebase instead.