Replies: 1 comment 11 replies
-
Nice idea, we'll definitely consider it when we'll be working on #24 |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm creating a graph (force graph to be exact) showing the relationship between different types of entities that I'm pulling out of a graph database.
Each entity type has a different shape. Nodes within one entity type are sized and coloured differently according to certain properties (read: more "interesting" nodes are bigger and more colourful).
I want to format links differently to distinguish between different types of graph edge (ownedBy, affiliatedWith, resolvesTo etc).
As I'm doing this I'm thinking: I need a key to show the user what the different link styles actually mean.
It would be great if there was a
<VisKey ... />
object that used all the same nodeFill etc functions to generate a key-based visualisation of each different node and link type/style.OR, failing that, some way to render a single representation of a node or link rather than an entire graph...
ATM I'm thinking of creating a key that has a collection of
<VisGraph.../>
objects with hammed in data to show the different node styles.Beta Was this translation helpful? Give feedback.
All reactions