gephi-plugins
gephi-plugins copied to clipboard
Neo4j Gephi 0.9 version support
I tried to install the plug-ins with 0.9.1 on my mac without success. It's keep needing older APIs. It seems that with 0.9 Gephi changed the way plugins are done. Is there a plan to upgrade the Neo4j plugins?
any updates on this? i'd like ti use the neo4j plugin as well with the latest 0.9 version.
I was able to install the two dependencies from here: https://github.com/mbastian/nbms-repository
After that Neo4j plugins could install
However - when I click File --> Install Neo4j Database, these are 2 options and the response I get: Full import --- > Select DB ---> Error window, no message Traversal import ---> Select DB ---> Nothing happens
See: https://github.com/gephi/gephi-plugins/issues/53
Hi Zachary, Sorry, even if you install that, the Neo4j plugin for Gephi 0.8.2 cannot work in 0.9+
The plugin needs a complete rewrite, it's planned, but our resources are very limited.
Thanks! I'll go with 0.8.2 for now.
would be awesome if this could be updated to work with 0.9* ! just tried to downloading and installing the older 0.8.2 version and doesn't even open anymore on my mac :(
There is no plan to adapt the Neo4j plugin, but you can easily connect Neo4j data to Gephi with APOC via GraphML export or even streaming plugin: https://neo4j-contrib.github.io/neo4j-apoc-procedures/
Yeah we might have to do the GraphML export / import. The streaming plugin only works reliably with very little data so effectively makes it unusable.
On Wed, Feb 27, 2019, 8:07 PM Eduardo Ramos [email protected] wrote:
There is no plan to adapt the Neo4j plugin, but you can easily connect Neo4j data to Gephi with APOC via GraphML export or even streaming plugin: https://neo4j-contrib.github.io/neo4j-apoc-procedures/
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gephi/gephi-plugins/issues/107#issuecomment-467782227, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQ_QGltUlddMpZCgsjvpY4SprEuzFY3ks5vRkrEgaJpZM4IU0mC .
Closing as we have a duplicate issue to cover this request, see #263.