-
Notifications
You must be signed in to change notification settings - Fork 22
RFE: Export full graph at readable scale #260
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
Comments
@jeff-phillips-18 Do you know how difficult this would be to implement? Could we do something like export to PDF? |
@dlabaj I have not looked into this nor do I have any experience with HTML to PDF. If you can convert HTML elements that are off screen to PDF then you could determine the bounds of the graph, create a div that is large enough to show the entire graph and then convert that. The slack thread mentioned is no longer available. |
@jshaughn Do you have information on what you tried? Looks like the the slack thread is no longer available. Is this something you still need? |
@dlabaj I don't recall the details, but in short I failed to find a way to capture the off-screen elements. We'd still like a way to capture a large topology, in readable scale, in a static format. I think in the Slack thread some other folks were also looking for a solution. If there were a way, I'd still be a little concerned of the size, as when anything is unbounded it tends to make bad things happen... |
The Kiali project had an RFE submitted for graph export at a readable scale. This means the user wants to be able to export a full layout at a scale that allows for labels to be readable, etc. In short, like a screenshot if the screen were big enough to render the entire topology at that scale. I don't know if this is feasible; my experience is only to be able to export the html elements that are currently visible on-screen.
I tried to adapt the solution used by NetObserv in this PFT Slack thread, but was not able to get it to work past what was on-screen (although it works nicely for that ability).
The text was updated successfully, but these errors were encountered: