Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert Cytoscape.js JSON style file to Cytoscape XML style file #1

Open
jlaw9 opened this issue Jun 7, 2017 · 5 comments
Open

Convert Cytoscape.js JSON style file to Cytoscape XML style file #1

jlaw9 opened this issue Jun 7, 2017 · 5 comments

Comments

@jlaw9
Copy link
Contributor

jlaw9 commented Jun 7, 2017

According to the Cytoscape documentation for Style File Formats, Cytoscape can export XML style files and Cytoscape.js compatible JSON style files, but only imports XML style files.

I suspect a good place to start for syncing graphs between Cytoscape and GraphSpace would be to create a script (in Java) which converts the JSON style file to an XML style file. That would enable a user to manually download a graph and style from GraphSpace, convert it to XML and then import the graph and style files to Cytoscape.

That same Java code could then be used to convert the styles internally for the app.

@tmmurali
Copy link
Member

tmmurali commented Jun 7, 2017

@adbharadwaj @rishabhsethi Should we consider this functionality in CyGraphSpace?

@tmmurali
Copy link
Member

tmmurali commented Jun 7, 2017

Sorry. I see that Jeff opened this bug in CyGraphSpace!

@adbharadwaj
Copy link
Contributor

adbharadwaj commented Jun 8, 2017 via email

@rishabhsethi
Copy link
Collaborator

Cytoscape should have an API to add style to the graph manually. So we should be able to parse the JSON file and add the style parameters. I'll try to implement this and get back.

@tmmurali
Copy link
Member

tmmurali commented Jun 8, 2017

@rishabhsethi Thanks for offering to implement this functionality. You do not need to work on this issue right away. I suggest you add it to your timeline sometime later in the summer. Getting the core functionality implemented first is more important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants