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

Consider approaches to improve the diagram generation #15

Open
csarven opened this issue Aug 31, 2017 · 0 comments
Open

Consider approaches to improve the diagram generation #15

csarven opened this issue Aug 31, 2017 · 0 comments

Comments

@csarven
Copy link
Member

csarven commented Aug 31, 2017

Many questions and possible paths here.

When there are many notifications it will take a long time for the client to fetch each (an HTTP request per notification) and to build the SVG diagram. Initial considerations:

  • Should there be a single file containing all notifications? This is still an issue once for the client.
  • Stream fetch and display. Potentially slowing down the rendering if the SVG is updated continuously - Perhaps drop the d3-force simulation. Advantage being that the user can see something right away. Perhaps fetch in batches?
  • Instead of fetching all notifications on load, the UI should make the calls based on user input eg display only the citations, and filtering.
    ..
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant