You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The headings name the type of vertex, and the rows describe an edge in one direction. There are problems with this format.
This format is highly specific to Excel. There's no way to also support CSV.
It's difficult to draw unnamed edges.
There's no way to create orphaned vertices.
The format is not extensible. (such as defining colours for vertices, etc.)
Given that relviz is still alpha or beta quality and just about literally no one knows it exists yet, we can do better. We can switch to the following format, and abandon the current one.
The edge data can be optional, and if edge data is not supplied we can say that the edge ID is equal to the edge label. We can allow for any number of optional additional columns for the node and edge rows to specify properties of them. In addition, we can later support settings for the graph itself:
Graph,Renderer
,Force-directed
We will support these groupings of CSV data in any given order. We will apply fuzzy-matching to headings so alternative spellings will work, potentially later including foreign languages.
The text was updated successfully, but these errors were encountered:
This issue will remain open until most of these ideas are realised, and can be used as a reference later for a vision of what this tool should do.
I slapped together relviz with the following format, expressed in CSV:
Sheet 1 (Name labels the edge)
The headings name the type of vertex, and the rows describe an edge in one direction. There are problems with this format.
Given that relviz is still alpha or beta quality and just about literally no one knows it exists yet, we can do better. We can switch to the following format, and abandon the current one.
We can accept the following extension later for defining Edge information.
The edge data can be optional, and if edge data is not supplied we can say that the edge ID is equal to the edge label. We can allow for any number of optional additional columns for the node and edge rows to specify properties of them. In addition, we can later support settings for the graph itself:
We will support these groupings of CSV data in any given order. We will apply fuzzy-matching to headings so alternative spellings will work, potentially later including foreign languages.
The text was updated successfully, but these errors were encountered: