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

doesn't support records? #41

Open
ellisonch opened this issue Sep 25, 2023 · 1 comment
Open

doesn't support records? #41

ellisonch opened this issue Sep 25, 2023 · 1 comment

Comments

@ellisonch
Copy link

ellisonch commented Sep 25, 2023

As far as I can tell, this doesn't support records? Is that correct?

I could only manage half a workaround; by using a custom "record" shape, and a manually encoded node label (e.g., <f0> a|<f1> b|<f2> c)) I could handle the nodes, but I can't figure out any way to get it to write edges as "node":f0 -> "node":f1 or node:f0 -> node:f1.

As far as the api goes, edge .From and .To just need to accept optional ports, and nodes need to accept a list of port names and labels (that can be nested in complicated ways, to be fair; they can be grouped in order to switch between horizontal fields and vertical fields).

@rvinowise
Copy link

you don't really need Record-nodes, but the HTML-layout in nodes will do all the work (and more). HTML-nodes can have many HTML-children, with "Port" attributes, so that edges will point from port to port precisely.
this is the specification: https://graphviz.org/doc/info/shapes.html
i tried to implement something like that here, but for the old version, now it's changed alot:
https://github.com/rvinowise/DotNetGraph

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

2 participants